chore: pin pnpm via packageManager field#5
Merged
Merged
Conversation
Lets Corepack auto-install the exact pnpm version across contributors and CI, preventing lockfile churn from mismatched pnpm installs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
6 tasks
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.
Adds
packageManager: pnpm@10.10.0(with integrity hash) topackage.jsonso Corepack auto-installs the exact pnpm version across contributors and CI.What this prevents: lockfile churn from mismatched pnpm installs on different machines.
Breaking: none. Contributors who don't use Corepack continue to work as before.
Test plan
jq . package.json— validates.corepack enable && pnpm --version— should print10.10.0after cloning.🤖 Generated with Claude Code