CI - Disallow npm-installed pnpm - #5895
Merged
Merged
Conversation
clockwork-labs-bot
requested review from
bfops,
cloutiertyler,
jdetter and
rekhoff
as code owners
September 9, 2026 02:13
bfops
reviewed
Sep 9, 2026
bfops
changed the title
bfops
enabled auto-merge
September 9, 2026 14:35
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
3 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.
Description of Changes
Follow-up to #5894.
We have an existing check that disallows "raw"
pnpm/action-setupin CI, so that everything must go through our custom pnpm installation action that also sets minimum package age. However, we were not checking fornpm install pnpm. This PR fixes that.Also updates the existing release workflow pnpm setup step to use
./.github/actions/setup-pnpm, so the new check passes.API and ABI breaking changes
N/A
Rollback safety impact
n/a
Expected complexity level and risk
1
Testing
CI passes