fix(ci): authenticate @void-sdk fetches in e2e + release workflows#104
Merged
fix(ci): authenticate @void-sdk fetches in e2e + release workflows#104
Conversation
PR #103 introduced a dependency on @void-sdk/* (published to GitHub Packages), but only deploy-landing.yml was updated to authenticate. The e2e and release workflows still ran `pnpm install --frozen-lockfile` without credentials and failed with ERR_PNPM_FETCH_401 on main after subsequent merges. Fix by teaching `.npmrc` to pull the token from `NODE_AUTH_TOKEN` and injecting that env var on every install step that needs it. No other changes — deploy-landing.yml keeps working as-is because setup-node already sets NODE_AUTH_TOKEN via its registry-url path. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
Fixes the post-merge CI failure on
mainintroduced by PR #103 (landing → void migration). That PR added@void-sdk/*packages hosted on GitHub Packages and updateddeploy-landing.ymlto authenticate — but forgot aboute2e.ymlandrelease.yml, both of which runpnpm install --frozen-lockfileand now hitERR_PNPM_FETCH_401.Example failure: https://github.com/spool-lab/spool/actions/runs/24768493984
Change
Central the auth configuration in the repo-root
.npmrc, then inject theNODE_AUTH_TOKENenv var on every install step that needs it..npmrcgrows one line://npm.pkg.github.com/:_authToken=\${NODE_AUTH_TOKEN}— pnpm expands the env ref at install time, so the token still only lives in repo secrets.e2e.yml(unit + e2e jobs): addsNODE_AUTH_TOKENenv on the two install steps.release.yml(build-mac + build-linux): same two-line addition on each.deploy-landing.ymlleft unchanged — its existingsetup-noderegistry-url path keeps working because the secret is still namedNODE_AUTH_TOKEN.No code paths touched — purely CI.
Test plan
@void-sdk/*under the new auth path)🤖 Generated with Claude Code