🔧 Fixing npm auth in the release workflow - #13
Merged
Merged
Conversation
…hes authenticated
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.
The 1.1.0 publish (run 37015827418) failed with
E404: Not Found - PUT https://registry.npmjs.org/pdfmonkey, and so did 1.0.0 (#7), which was then published by hand.actions/setup-nodewithregistry-urlwrites an.npmrcthat reads${NODE_AUTH_TOKEN}. The workflow only exportsNPM_TOKEN, so the log showsFailed to replace env in config: ${NODE_AUTH_TOKEN}and npm publishes anonymously, which the registry answers with a 404.This passes the same
NPM_TOKENorg secret asNODE_AUTH_TOKEN. Once it's merged, the Release workflow finds no changesets and publishes the unpublishedpdfmonkey@1.1.0.