Repository navigation
Conversation
Bump the pinned pnpm to 12.21.0 and enable the experimental `lockfile.format: v13` (pnpm >= 12.19). It writes pnpm-lock.yaml with one entry per package version and one line per value, with trailing commas, so dependency updates touch fewer lines and concurrent PRs hit fewer lockfile merge conflicts. Resolved dependency versions are unchanged; only the pnpm binaries in the env lockfile and the lockfile layout change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VVaw7SDgegkh5P17SW6Ewa
|
No actionable comments were generated in the recent review. Summary
Merge Risk:
|
@standard-server/aws-lambda
@standard-server/core
@standard-server/fastify
@standard-server/fetch
@standard-server/node
@standard-server/peer
@standard-server/shared
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Merging this PR will not alter performance2 warnings
Comparing Footnotes
|
There was a problem hiding this comment.
✅ No new issues found.
Approach: sound — bumping the exact packageManager pin and enabling lockfile.format: v13 in pnpm-workspace.yaml is the whole mechanism; CI and Corepack both read that pin, and the large lockfile diff is the one-time rewrite into the new layout.
Reviewed changes — all three files, verified against the base lockfile rather than by reading the diff alone:
packageManagerbump topnpm@12.21.0— the only pnpm version reference in the repo; every workflow usespnpm/action-setup@v6with noversioninput, so nothing else needs updating.lockfile.format: v13inpnpm-workspace.yaml— honoured by pnpm: taking the base v9 project document and runningpnpm install --lockfile-onlywith this config present reproduces the committed file byte for byte, so the lockfile is canonical (not hand-edited) and the key is not a silent no-op.pnpm-lock.yamlrewrite — the file stays multi-document (env lockfile still v9 YAML for the@pnpm/exe.*binaries incl. the newnetbsd-x64; project document now v13 withprojectsand a singlepackagesmap). Resolved package sets are identical: 550 entries in both, same 11 projects, and the 31 peer-suffixed snapshot keys collapse to plain version keys with no collisions.
Beyond the diff, I confirmed:
pnpm install --frozen-lockfilepasses on 12.21.0 with no lockfile churn.- A fresh checkout (
git archive HEAD) installs cleanly with--frozen-lockfile --ignore-scripts. pnpm runtime set node 24(the CI matrix step) leaves the project document at13.0;sherifis clean;oxfmtexcludes the lockfile, sopnpm formatcan't rewrite the v13 document.- The repo has no Renovate/Dependabot config, so no third-party lockfile parser is exposed to the experimental format.
One editorial nit, no action needed: the PR body mentions a "packageManager / devEngines pin", but the repo only pins via packageManager.
deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏
|
Closing this for now because the v13 lockfile format is still experimental upstream. I'm keeping the branch so it can be reopened later. Blockers I confirmed before closing:
Worth revisiting once v13 is stable and Dependabot supports it. Generated by Claude Code |

Summary
Bump the pinned pnpm from
12.16.1to12.21.0(latest), viapnpm self-update.Enable the v13 lockfile format in
pnpm-workspace.yaml:Why
The v13 format (added in pnpm 12.19) writes
pnpm-lock.yamlwith one entry per package version (no separatepackages/snapshotssections), one value per line, and a trailing comma after every entry. A dependency or peer update then changes only the lines that record its version, so concurrent PRs hit far fewer lockfile merge conflicts.Notes
name@versionsets of the old and new lockfiles: they match, apart from pnpm's own binaries in the env lockfile document.packageManager/devEnginespin makes pnpm switch to 12.21.0 automatically, and CI usespnpm/action-setup@v6, which reads that pin.Testing
pnpm install --frozen-lockfilesucceeds with pnpm 12.21.0pnpm run check(or this repo's equivalent) passesGenerated by Claude Code