chore(deps): bump pnpm to 11.14.0 - #1032
Closed
ByronDWall wants to merge 1 commit into
Closed
Conversation
Matches the pnpm version already running cleanly in sibling repos (merchant-center-application-kit, nimbus, ui-kit, merchant-center-frontend). When on 11.10.0, two confirmed upstream memory regressions apply: pnpm/pnpm#12868 (11 resolution using ~47% more memory than pnpm 10 on a cold metadata cache), fixed by pnpm/pnpm#12870, and pnpm/pnpm#13077 (11.11+ OOMs by re-serializing full package metadata for concurrent workspace cache hits), fixed by pnpm/pnpm#13079. This bump lands past both fixes. No active OOM crash evidence in this repo; this is a proactive bump to bring it in line with siblings. pnpm-lock.yaml is unchanged.
|
Contributor
Author
|
Superseded by a consolidated PR targeting pnpm 11.17.0. |
ByronDWall
added a commit
that referenced
this pull request
Aug 10, 2026
Bumps the packageManager field to pnpm 11.17.0, which stays below the known bad pnpm deploy legacy regression introduced in 11.19.0/11.20.0 (pnpm/pnpm#13618). Adds a Renovate packageRule disabling pnpm updates until pnpm/pnpm#13755 ships in a release, since that fix is merged but not yet published. Supersedes #1032 and #1034, which targeted an earlier pnpm version and an earlier draft of this hold rule.
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.
What
Bumps the pinned
packageManagerfield frompnpm@11.10.0to:Why
This matches the exact pnpm version already running cleanly in sibling repos (merchant-center-application-kit, nimbus, ui-kit, merchant-center-frontend).
When pinned to 11.10.0, this repo predates two confirmed, since-fixed upstream pnpm memory regressions:
There is no known active OOM crash evidence in this repo (unlike some siblings). This is a proactive bump to bring it in line with siblings and past both regressions.
Verification
Installed and used pnpm 11.14.0 via
corepack use pnpm@11.14.0, then ran a fullpnpm install(not--lockfile-only) to regenerate the lockfile against the new pnpm version.pnpm-lock.yaml: no diff. Matches what sibling repos saw when they made the same bump.pnpm typecheck(tsc --noEmit): passes, no errors.pnpm build(preconstruct build): passes.pnpm lint(jest --config jest.eslint.config.js): 2820 suites passed.pnpm test(jest --config jest.test.config.js): 535 suites, 1691 tests, 42 snapshots, all passed.Nothing broke as a result of the pnpm version bump.
Notes
pnpm-lock.yamlunchanged, onlypackage.json'spackageManagerfield is touched.