Publish to GitHub packages in addition to npmjs #1330
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.
This PR updates the NPM package publish workflow to publish to GitHub packages in addition to npmjs.
There are a few changes here:
The proposed change now uses the workflow described in https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-nodejs-packages to use the setup-node action to set up the node environment. As a result of this action, the following is added to
.npmrc
in the runner (including the variable placeholder):After this we add the following line to
.npmrc
by invokingnpm config set
:Now, when publishing to npmjs, we set the environment value
NODE_AUTH_TOKEN
to the NPM publish token, which is resolved asnpm publish
reads.npmrc
.After that, there is a new step that publishes to GitHub packages, which sets the registry for the
@fastly
scope tonpm.pkg.github.com
. For this step we set the environment valueNODE_AUTH_TOKEN
to the GitHub token, which is resolved asnpm publish
reads.npmrc
.