Skip to content

fix: set up Node.js in validate-release-pr before the rebuild #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mldangelo merged 1 commit into from
May 22, 2026
Merged

fix: set up Node.js in validate-release-pr before the rebuild #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion .github/workflows/validate-release-pr.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,14 @@ jobs:

echo "Branch ${{ github.head_ref }} is not a generated release branch; artifact mirror files are unchanged."

# setup-node gives `npm install -g` a writable global prefix and pins the
# rebuild toolchain to match promptfoo's release job (.nvmrc -> Node 24).
- name: Set up Node.js
if: ${{ startsWith(github.head_ref, 'release/code-scan-action-v') }}
uses: actions/setup-node@v6
with:
node-version: '24'

- name: Validate generated release payload
if: ${{ startsWith(github.head_ref, 'release/code-scan-action-v') }}
env:
Expand Down Expand Up @@ -90,7 +98,7 @@ jobs:
exit 1
fi

npm install -g npm@latest
npm install -g npm@11.11.0
npm ci
npm ci --prefix code-scan-action
npm run tsc --prefix code-scan-action
Expand Down