Add GitHub workflow for npm publish #13
Open
Conversation
This file contains 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.
Closes #12
How to use
This requires a setup for github secrets with the name
NPM_TOKEN.This can be added on a organisation level from the settings and then go to
Security -> Secrets and Variables -> Actions, from here you can add the secret with the nameNPM_TOKENTo create a token go to you NPM user settings and then tokens (for example: https://www.npmjs.com/settings/hyva-theme/tokens), from here you can create a token
When added, anytime you create a release, so release is more than just creating a tag, a github action will be run that will publish a new version.
For more information see the docs on this: https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-nodejs-packages