chore: bump pnpm to 11.24.0 - #827
Merged
Merged
Conversation
The root `packageManager` field is the single source of truth for the pnpm version: Netlify reads it via Corepack (it has no PNPM_VERSION variable) and `pnpm/action-setup` resolves it there, since the workflows pass no `version` input. Bumping it here moves both at once. The lockfile stays at lockfileVersion 9.0, unchanged across pnpm 11.x. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for commercelayer-react-components ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
gciotola
approved these changes
Sep 1, 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
2 participants
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.
Bumps the root
packageManagerfield frompnpm@11.22.0topnpm@11.24.0.Why this one line matters more than it looks
packageManageris the only source of the pnpm version for the whole project, in two places that have no fallback of their own:PNPM_VERSIONvariable to override it — this is spelled out innetlify.toml:7.pnpm/action-setup@v6with noversioninput (e.g.publish.yaml:19-20), so the action resolves the version from this field. Without it the step fails outright.So merging this moves CI and the Netlify builds to 11.24.0 together. That is the intended effect, and it is the reason the field must not be removed —
preinstall: npx only-allow pnpmenforces which package manager, not which version.Compatibility
pnpm-lock.yamlstays atlockfileVersion: 9.0, which is unchanged across pnpm 11.x, so no lockfile churn and no reinstall required.Note
The
.claude/worktrees/merge-main-into-v5worktree carries its ownpackage.jsonstill pinned atpnpm@11.22.0. It will pick this up when main is merged into it.