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:
|
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 performance
Comparing Footnotes
|
There was a problem hiding this comment.
✅ No new issues found.
Approach: sound — moving the pnpm pin and the lockfile format together in one commit is the right sequencing: pnpm 12.21.0 is the tool that writes and reads the v13 document, and the packageManager pin is what makes CI (pnpm/action-setup@v6) and older local pnpm installs switch to it automatically.
Reviewed changes
- pnpm pin —
packageManagermoved from12.16.1to12.21.0; verified against the registry, andengines.node >=18is satisfied by the20/22/24/26CI matrix. - v13 lockfile — the project document is now
lockfileVersion: "13.0": tab indentation, trailing commas, a singlepackagesmap with peer versions as properties, and nosnapshotssection. The boot/env document keeps its9.0shape and lists the new pnpm binaries. - format opt-in —
lockfile: { format: v13 }inpnpm-workspace.yaml, confirmed effective (pnpm config get lockfile.format→v13).
Checks run locally: pnpm install --frozen-lockfile passes, a fresh pnpm install leaves the lockfile byte-identical, the resolved package set is unchanged versus main (377 entries), and pnpm check / pnpm test (377 tests) pass. CI is green, including the pkg-pr-new preview job. Dependabot's pinned lockfile parser (@pnpm/lockfile-file@9.1.3) reads the v13 document and sees all packages, so the daily update job should keep working.
One understanding worth carrying forward: v13 is still upstream-experimental, so a future pnpm release may force another one-time lockfile rewrite. That trade-off is documented in the PR description and is reasonable given the merge-conflict payoff.
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