chore(external-tools): bump pnpm 11.1.3 → 11.3.0#286
Closed
John-David Dalton (jdalton) wants to merge 1 commit into
Closed
chore(external-tools): bump pnpm 11.1.3 → 11.3.0#286John-David Dalton (jdalton) wants to merge 1 commit into
John-David Dalton (jdalton) wants to merge 1 commit into
Conversation
Updates all 8 platform integrity hashes from the GitHub Release v11.3.0 assets + the npm-registry tgz for darwin-x64. Released 2026-05-24; past the 7-day soak window for fleet adoption. Unblocks fleet CI which has been red since fleet package.json files were cascaded to pnpm@11.3.0 ahead of this canonical pin update.
Collaborator
Author
|
Closing per direct-push policy; pushing directly to main. |
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.
Summary
Why
Fleet CI is currently red across every repo because fleet `package.json` files were cascaded from the wheelhouse template to require `pnpm@11.3.0`, but this canonical pin (which drives the CI setup action's pnpm install) still pointed at 11.1.3. The mismatch makes every CI install fail with:
Merging this unblocks CI everywhere that uses `setup-and-install`.
Test plan