ci: restore pnpm action setup#156
Merged
Merged
Conversation
rvagg
approved these changes
Jul 23, 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
pnpm/action-setup@v6version: latestso CI tracks the current pnpm releaseWhy
The workflow moved to
npm install --global pnpm@11.12.0after both pnpm/action-setup's self-update path and the 11.12.0 standalone artifacts failed.pnpm/action-setup#276 confirms that the self-update failure is resolved in pnpm 11.13.0. The standalone platform packages were still incomplete in 11.13.0; pnpm/pnpm#12955 confirms 11.13.1 as the repaired release. With both upstream prerequisites now shipped, the workflow can return to the maintained setup action and its previous current-release tracking behavior.
Fixes #152.