fix(ci): add npm registry auth to release publish job#319
Merged
tmchow merged 1 commit intoEveryInc:mainfrom Mar 20, 2026
Merged
fix(ci): add npm registry auth to release publish job#319tmchow merged 1 commit intoEveryInc:mainfrom
tmchow merged 1 commit intoEveryInc:mainfrom
Conversation
The publish-cli job calls `npm publish --provenance --access public` but the setup-node step did not configure the registry URL or auth token, causing ENEEDAUTH on every release attempt. - Add `registry-url: https://registry.npmjs.org` to setup-node step - Add `NODE_AUTH_TOKEN` env var to the publish step Closes EveryInc#317 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Collaborator
|
Thanks @tonymfer :) |
Merged
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
registry-url: https://registry.npmjs.orgtoactions/setup-node@v4stepNODE_AUTH_TOKENenv var to the npm publish stepWhy
The
publish-clijob in the release workflow callsnpm publish --provenance --access publicbut the Node.js setup step doesn't configure the npm registry URL or auth token. This causesENEEDAUTHon every release attempt.Closes #317
Test plan
🤖 Generated with Claude Code