Fix missing NODE_AUTH_TOKEN in npm publish workflow step - #14
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job build-publish-npm
Fix missing NODE_AUTH_TOKEN in npm publish workflow step
Jul 22, 2026
shaipetel
approved these changes
Jul 22, 2026
shaipetel
marked this pull request as ready for review
July 22, 2026 16:56
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
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.
The
build-publish-npmjob was failing withnpm error 404 Not Found - PUT https://registry.npmjs.org/@kwiz%2fcommonbecausenpm publishwas running unauthenticated. Whenactions/setup-nodeis configured withregistry-url, it wires up an.npmrcthat reads fromNODE_AUTH_TOKEN— but that env var was never passed to the publish step.Change
.github/workflows/npm-publish.yml: AddNODE_AUTH_TOKENenv var to thenpm publishstep, sourced from theNPM_TOKENrepository secret.