chore(deps): migrate to pnpm 11#4
Merged
Merged
Conversation
…yaml; bump packageManager to pnpm 11 - Remove `pnpm.onlyBuiltDependencies` from package.json (removed in pnpm 11) - Create pnpm-workspace.yaml with allowBuilds map (esbuild, lefthook) - Bump packageManager to pnpm@11.2.1 - Bump engines.pnpm to >=11.0.0 Removes the pnpm 10 pin that was a tactical measure during the Node 22 engine bump. Reference: https://pnpm.io/migration Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
pnpm.onlyBuiltDependenciesfrompackage.json(key family removed in pnpm 11)pnpm-workspace.yamlwithallowBuildsmap (esbuild,lefthook) — the pnpm 11 replacementpackageManagertopnpm@11.2.1(pinned exactly)engines.pnpmto>=11.0.0This finishes the migration that was deferred during the Node 22 engine bump. The pnpm 10 pin was a tactical workaround; pnpm 11 is now fully supported with
pnpm-workspace.yamlconfig. Reference: https://pnpm.io/migrationNo user-facing behaviour change. Published package surface is identical.
Test plan
pnpm test)pnpm typecheck)pnpm lint)pnpm build)evals/suite,EVALS_RUN_ID=pnpm-11-cap-analyzer)🤖 Generated with Claude Code