ci: install pnpm 11.12 directly with npm - #151
Merged
Merged
Conversation
rvagg
reviewed
Jul 13, 2026
rvagg
approved these changes
Jul 13, 2026
rvagg
left a comment
Contributor
There was a problem hiding this comment.
this will need to be undone .. can you open an issue in the repo for it too please so we don't lose track?
Contributor
Author
I opened it here: #152 |
Co-authored-by: Rod Vagg <rod@vagg.org>
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
Why
The stability job in run 29227598125 started the devnet successfully, then failed before scenario execution while pnpm/action-setup@v6 tried to self-update its pnpm 11.7.0 bootstrap to 11.12.0.
The initial standalone workaround also proved unsuitable: pnpm setup completed, but the published @pnpm/exe 11.12.0 platform package lacked its executable, causing scenario pnpm installs to fail with
@pnpm/exe/pnpm: 1: This: not found.Node.js 24 is already configured earlier in the workflow, so installing the regular
pnpm@11.12.0npm package avoids both upstream failures while keeping CI on the current release.Upstream references:
Fixes #149.
Fixes #150.
Impact
Nightly stability and frontier jobs can proceed through pnpm setup and execute scenarios with pnpm 11.12.0. The version remains explicit, so future releases do not alter CI without review.
Validation
pnpm@11.12.0package reports version 11.12.0