ci: pin actions/setup-node to v4.0.4
CI / Architecture Guardrails (push) Successful in 6m48s
CI / Lint (push) Successful in 6m38s
CI / Unit Tests (push) Failing after 3m5s
CI / Typecheck (push) Successful in 10m1s
CI / Build (push) Failing after 18s
CI / E2E Tests (push) Has been skipped
CI / Assistant Split Regression (push) Successful in 10m59s
CI / Release Images (push) Has been skipped
CI / Fresh-Linux Docker Deploy (push) Has been skipped
CI / Architecture Guardrails (push) Successful in 6m48s
CI / Lint (push) Successful in 6m38s
CI / Unit Tests (push) Failing after 3m5s
CI / Typecheck (push) Successful in 10m1s
CI / Build (push) Failing after 18s
CI / E2E Tests (push) Has been skipped
CI / Assistant Split Regression (push) Successful in 10m59s
CI / Release Images (push) Has been skipped
CI / Fresh-Linux Docker Deploy (push) Has been skipped
act_runner sometimes checks out moving tag @v4 without the built dist/ output, breaking all jobs with MODULE_NOT_FOUND on setup/index.js. Pinning to a tagged release avoids the incomplete checkout.
This commit is contained in:
@@ -22,7 +22,7 @@ jobs:
|
||||
- name: Install pnpm
|
||||
run: npm install -g pnpm@${{ env.PNPM_VERSION }}
|
||||
|
||||
- uses: actions/setup-node@v4
|
||||
- uses: actions/setup-node@v4.0.4
|
||||
with:
|
||||
node-version: ${{ env.NODE_VERSION }}
|
||||
cache: pnpm
|
||||
|
||||
Reference in New Issue
Block a user