A merge to main could break the app even though the PR check ran
ci-test separately; deploy previously fired on push regardless of
CI outcome. Trigger deploy via workflow_run on ci-test completion
instead, and skip the build job unless ci-test concluded success,
so a broken main no longer publishes to Pages.
* Use safe concurrency pattern for Pages deploys
Switch to the group: pages, cancel-in-progress: false pattern GitHub
recommends for deploy-pages, so a superseded run is skipped before it
starts rather than killed mid-deploy, which can leave the Pages
deployment stuck in progress.
* Tag each successful Pages deploy
There is currently no record of which commits were actually deployed.
Tag the deployed commit as deploy-YYYY-MM-DD-<sha> right after
deploy-pages succeeds, giving a lightweight, always-unique history of
production deploys without introducing a formal versioning/release
scheme.
* Switch Dependabot checks from daily to weekly
Reduces PR noise by checking for npm and github-actions updates
weekly instead of daily.
Co-Authored-By: Claude Sonnet 5 <[email protected]>
* Add resumé link to experience section
Point visitors to a full resumé for more detail, and add rel support
to Link so external references can opt out of link equity.
---------
Co-authored-by: Claude Sonnet 5 <[email protected]>
Give the check job an explicit name so branch protection rules can
reference a stable, searchable "CI" status check context instead of
the generic job-key-derived name.
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
The pnpm migration left a tracked .yarn/install-state.gz. pnpm doesn't
use the .yarn directory, so remove it.
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
Adds a project-scoped .mcp.json registering the Playwright MCP server
so browser automation tooling is available to anyone using Claude Code
in this repo.
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
* Switch package manager from Yarn to pnpm
Replace Yarn 3 (Berry) with pnpm 11.12.0 (latest stable):
- Pin packageManager to [email protected].0; add pnpm-lock.yaml
- Remove yarn.lock, .yarnrc.yml, and the bundled .yarn/ release
- Update CI (ci-test, deploy) to use pnpm/action-setup + setup-node
pnpm cache, with `pnpm install --frozen-lockfile` and pnpm scripts
- Switch Husky pre-commit hook to `pnpm check`
- Add pnpm-workspace.yaml allowlisting esbuild's build script, which
pnpm 11 otherwise blocks with a hard error on install
- Update CLAUDE.md guidance and drop yarn-specific .gitignore entries
Verified: pnpm install --frozen-lockfile, pnpm check, and pnpm build
all pass locally.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
* CI: read Node version from .tool-versions for pnpm 11 compat
pnpm 11.12.0 requires Node >=22.13, but the workflows pinned
node-version: '20' (20.20.2), failing install. Point setup-node at
.tool-versions (22.14.0) so CI and local dev share one source of truth.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
Document build/check commands, the Svelte 5 + Vite + Tailwind v4
architecture, project conventions, and the GitHub Pages deploy flow
for future Claude Code sessions.
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
djkotowski
