This repository was archived by the owner on Sep 26, 2026. It is now read-only.
Repository navigation
fix(ci): enable corepack before Setup Node so the pnpm cache resolves - #2
Open
danjdewhurst wants to merge 1 commit into
Open
danjdewhurst wants to merge 1 commit into
danjdewhurst wants to merge 1 commit into
Conversation
`actions/setup-node` with `cache: pnpm` shells out to `pnpm store path` to locate the cache directory. That ran before `corepack enable`, so no `pnpm` binary existed yet and the Setup Node step failed. `ci` has been red on `main` since 2026-04-18 for this reason. Moving `corepack enable` ahead of Setup Node makes the shim available when the cache probe runs. No other change. Co-Authored-By: Paperclip <noreply@paperclip.ing>
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can type 'qodo, fix this' on a finding and the fix lands right on your PR |
PR Summary by QodoEnable Corepack before pnpm cache setup in CI
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Found by the weekly maintenance sweep.
cihas been failing onmainsince 2026-04-18 — the last run on the default branch is 24613931302, and the failing step isSetup Node, step 3.Cause
actions/setup-nodewithcache: pnpmresolves the cache directory by shelling out topnpm store path. In the current workflow that step runs beforecorepack enable, so there is nopnpmonPATHyet and the cache probe fails the step before anything is installed.package.jsondeclares"packageManager": "pnpm@10.33.0", sopnpmonly exists once corepack has been enabled.Fix
Move
Enable corepackahead ofSetup Node. This is the orderingactions/setup-nodedocuments for corepack-managed package managers: the corepack shim lands in the system npm prefix, which stays onPATHaftersetup-nodeprepends its own toolchain, so the cache probe resolves.One-line reorder, no other change, no new action dependencies.
Verification
Not verified by CI on this branch. GitHub Actions jobs in this org are currently not starting at all — they fail in a few seconds with zero steps executed, which is a billing / spending-limit block rather than a code problem. The same signature is visible right now on
forjd/polar,forjd/sl-rp-webandforjd/qa. Until that clears, this PR's checks will not be meaningful either.Reviewed by reading the workflow and
package.jsonrather than by a green run. Flagging that explicitly so it is a conscious call at merge time.Not merging this — handing it over for sign-off.