fix(npm-publish): setup node with registry url #8841
Merged
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
(MP-385)
Problem
The "npm publish" workflow is failing, and the real reason (after 3 unsuccessful tries) seems to be that npm doesn't actually use
NPM_AUTH_TOKEN
orNODE_AUTH_TOKEN
, unless these are referenced in an.npmrc
file.Solution
Call the
setup-node
action with theregistry-url
input, which causes it to create an.npmrc
file that references theNODE_AUTH_TOKEN
environment file.Also:
--access
revert (this is not necessary for scoped packages that are already published and public).How did you test this change?
🤞