chore(deps): bump pnpm to 11.17.0 and hold future updates - #1035
Merged
Conversation
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.
|
ByronDWall
marked this pull request as ready for review
August 10, 2026 17:54
tylermorrisford
approved these changes
Aug 10, 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.
Summary
Bumps
packageManagertopnpm@11.17.0and adds a Renovate hold rule to prevent automatic updates past this version until a known regression is fixed upstream.Why
pnpm deploy --legacyis broken in pnpm 11.19.0 and 11.20.0 (pnpm/pnpm#13618). The fix landed in pnpm/pnpm#13755 but has not been published in a release yet. Pinning to 11.17.0 keeps this repo safely below the affected versions while staying ahead of the previously pinned 11.10.0.Changes
package.json:packageManagerset topnpm@11.17.0+sha512.cca3cea332ad254bb84145f966d19f4879615210346fc92c79a047f23a0d7b3cca3c3792f0076ba1f1831d277efbcf0a9119b31a9a60eca7fb3d6231f331ef72.github/renovate.json: newpackageRulesentry disabling Renovate-proposed pnpm updates, with a description pointing at the upstream issue/fix and instructions to remove the rule once pnpm ships a release containing the fix.Supersedes
Both were closed in favor of this consolidated PR.
Verification
pnpm installcompleted cleanly with pnpm 11.17.0.pnpm typecheckpassed.pnpm buildpassed.pnpm lintpassed (2820 suites).pnpm testpassed (535 suites, 1691 tests)..github/renovate.jsonvalidated as well formed JSON viajqandnode -e "JSON.parse(...)".