chore(deps): update pnpm to v12 - #265
Merged
Merged
Conversation
baseballyama
force-pushed
the
renovate/pnpm-11.x
branch
from
June 15, 2026 01:11
3f026f5 to
9dbebeb
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-11.x
branch
2 times, most recently
from
June 18, 2026 19:53
290f319 to
0252b11
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-11.x
branch
from
June 23, 2026 18:05
0252b11 to
8d77dda
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-11.x
branch
2 times, most recently
from
July 4, 2026 20:50
6287831 to
460f963
Compare
Renovate proposed pnpm 11.10.0 back in July; 11.x has since been superseded by 12.x, so go straight to the current release rather than land the same migration twice. Both majors turn ignored build scripts into an install error, which is what kept this red (`ERR_PNPM_IGNORED_BUILDS: esbuild`). pnpm 12 also replaces `onlyBuiltDependencies` with `allowBuilds`, so the workspace now approves esbuild and node-pty explicitly. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
baseballyama
force-pushed
the
renovate/pnpm-11.x
branch
from
September 20, 2026 16:04
460f963 to
5801c42
Compare
baseballyama
changed the title
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
Moves the repo's pinned package manager from pnpm 10.34.4 to 12.5.1 and approves the two dependency build scripts the new majors require to be listed explicitly.
Motivation
Renovate opened this in July proposing pnpm 11.10.0. It has been red ever since because pnpm 11 promoted "ignored build scripts" from a warning to an install error:
11.x has since been superseded by 12.x. The migration work is identical for both, so this goes straight to the current release rather than landing it twice.
Changes
Nothing user-visible — this is repo tooling only.
packageManager→pnpm@12.5.1.pnpm-workspace.yaml:onlyBuiltDependencies→allowBuilds, which pnpm 12 replaced it with, listingesbuild(links its prebuilt binary) andnode-pty(compiles the dev-preview terminal bridge).pnpm-lock.yamlpicks up pnpm 12'spackageManagerDependenciesblock, which pins the pnpm binary itself alongside the rest of the tree.Testing
Ran the full local gate under pnpm 12.5.1:
2015 tests: 1905 passed, 109 skipped. The one failure is
test/property/schema-valid.property.test.tshitting its 5 s budget under parallel load — it passes in 1.9 s on its own and is green in CI, unrelated to this change.Breaking changes
None. Contributors get the pinned pnpm automatically via
corepack/pnpm/action-setup.Checklist
flagged it above.
represents real work that warrants a maintainer's review, and I am willing to
defend each line in review.
🤖 Generated with Claude Code