chore: bump pnpm to 12.6.0 - #682
Merged
Merged
Conversation
Bump packageManager to pnpm@12.6.0 and pin pnpm/action-setup to v6.1.0. The floating v6 tag still points at v6.0.10, which predates pnpm 12 support (pnpm/action-setup#289). The lockfile gains a leading document pinning pnpm itself; the dependency graph is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CLWF7NjBCMtQMXjDBHqwRD
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
packageManagertopnpm@12.6.0(currentlatest) and pinspnpm/action-setuptov6.1.0.pnpm/action-setup@v6.1.0, not@v6. The floatingv6tag still points at v6.0.10 (2026-08-03), which predates pnpm 12 support. Support landed in v6.1.0 (pnpm/action-setup#288), but the major tag was never moved (pnpm/action-setup#289, open). Revert to@v6once that is fixed.pnpm-lock.yamlgains a leading document that pins pnpm itself (packageManagerDependencies:pnpm+@pnpm/exe.*platform binaries). Additions only (+183/-0); the dependency graph is untouched.v12 breaking changes checked
pnpm ships no v11→v12 migration guide (its docs say v12 keeps v11's config model), so this was checked against the v12.0.0 release notes and 12.1–12.6 (no further major changes):
pnpm-workspace.yamlkeys are now a hard error: all keys here are recognized.--frozen-lockfile falseremoved: not used.engineStrictnow fails through optional subtrees: not set.filterLogdeprecated: no pnpmfile.ERR_PNPM_TASK_CYCLEforpnpm -r run/exec: not used (turbo/lerna orchestrate).Repo-specific
action-setup, so no workflow changes. Verified corepack 0.35.0 runs pnpm 12.6.0 (the npm package's launcher downloads the native binary).action-setup@v4example in.github/instructions/github-actions.instructions.md, which would break under pnpm 12 if copied.Test plan
node_modules:pnpm install --frozen-lockfileunder pnpm 12.6.0, then build, lint, test. All green, no pnpm warnings.pnpm/action-setup@v6.1.0🤖 Generated with Claude Code
https://claude.ai/code/session_01CLWF7NjBCMtQMXjDBHqwRD