Upgrade to pnpm 11 - #160
Open
sneridagh wants to merge 4 commits into
Open
Conversation
sneridagh
marked this pull request as ready for review
August 8, 2026 22:49
pnicolli
approved these changes
Aug 9, 2026
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
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
packageManagerfield.corepack prepare pnpm@* --activatein Read the Docs before the asdf reshim step.overridesandonlyBuiltDependenciesfrompackage.json#pnpmtopnpm-workspace.yaml, where pnpm 11.20.0 reads these settings.Why
The repository was pinned to pnpm 10.20.0. Upgrading to the current stable pnpm 11 release keeps the package manager current without adopting the pnpm 12 pre-release and native-binary installation constraints.
The pnpm version remains declared in one place:
package.json#packageManager. Corepack reads this field whenever pnpm runs in the repository, ensuring contributors and automated environments use the same exact pnpm release without duplicating the version in workflow or documentation files.pnpm 11.20.0 no longer reads the root
package.json#pnpmconfiguration block. Moving the existing overrides and build dependency allowlist topnpm-workspace.yamlpreserves their behavior and prevents frozen-install configuration mismatches.Developer and CI impact
Contributors install and enable current Corepack, then invoke pnpm normally. Corepack downloads and activates pnpm 11.20.0 based on the repository pin.
The shared GitHub Actions setup installs current Corepack before restoring the pnpm store cache and running the existing
make installstep.Read the Docs continues to prepare and activate pnpm explicitly before
asdf reshim nodejs; repository commands still resolve to the exact package-manager version declared inpackage.json.The dependency lockfile does not require regeneration for this upgrade.
Validation
corepack prepare pnpm@* --activatepnpm --version→11.20.0pnpm install --frozen-lockfile --ignore-scriptsgit diff --checklint-staged