Skip to content

fix(ci): add setup-node to release test job to fix npm install failure#33

Merged
seanseannery merged 2 commits intomainfrom
fix/npm-install-test-ci
Mar 7, 2026
Merged

fix(ci): add setup-node to release test job to fix npm install failure#33
seanseannery merged 2 commits intomainfrom
fix/npm-install-test-ci

Conversation

@seanseannery
Copy link
Owner

@seanseannery seanseannery commented Mar 7, 2026

Key Changes

  • Split the test job into two parallel jobs:
    • test — Go unit tests on ubuntu-latest
    • install-test — install smoke tests on macos-latest (has Homebrew pre-installed)
  • release job now waits on both (needs: [test, install-test])
  • Expose GITHUB_TOKEN in the install-test job environment
  • Update install.sh to pass Authorization: Bearer $GITHUB_TOKEN header to GitHub API when env var is set
  • Update npm_install.js to pass the token header and add error guards on the API response (release.message, missing release.assets)

Why do we need this?

Two failures in the install smoke tests:

  1. spawn sh ENOENT — npm couldn't run the postinstall hook without proper Node setup (fixed by moving to macos-latest with setup-node)
  2. curl: 403 / Cannot read properties of undefined (reading 'find') — GitHub API rate limits unauthenticated requests from Actions runners. Passing GITHUB_TOKEN authenticates the requests (5000/hr limit instead of 60/hr)

New modules or other dependencies introduced

None.

How was this tested?

Will verify by re-running the release workflow after merge. All three install methods (curl, brew, npm) should pass on the macOS runner.

@seanseannery seanseannery merged commit 62bf9c3 into main Mar 7, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant