fix(ci): set up node in the github-release job#25
Merged
Conversation
The `github-release` job runs `node scripts/extract-changelog-section.mjs` on a self-hosted arc runner that does not have node preinstalled, so v0.2.0 hit `node: command not found` on the release notes step. The verify job already installs node via `actions/setup-node@v6`, so mirror the same setup in github-release before invoking node. This was masked on v0.2.0 by the docker.yml pipeline completing independently, so the image was still published; the GitHub release was backfilled manually. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
kimo-ice
approved these changes
Apr 16, 2026
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
2 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.
Summary
The
github-releasejob inrelease.ymlrunsnode scripts/extract-changelog-section.mjson a self-hostedarc-runner-setrunner that does not have node preinstalled. The v0.2.0 tag run hit `node: command not found` and failed on the release notes step.The `verify` job already installs node via `actions/setup-node@v6`, so this PR mirrors the same setup in `github-release` before the node invocation.
Impact
Test plan
Note
Low Risk
Low risk workflow-only change that adds a missing runtime dependency; main risk is potential Node version/environment drift on the self-hosted runner.
Overview
Fixes the tag
releaseworkflow so thegithub-releasejob explicitly installs Node.js (viaactions/setup-node@v6, Node 22) before generating release notes.This prevents
node: command not foundfailures on self-hostedarc-runner-setrunners when runningscripts/extract-changelog-section.mjsto buildRELEASE_NOTES.md.Reviewed by Cursor Bugbot for commit 710a6ef. Bugbot is set up for automated code reviews on this repo. Configure here.