feat: adds in auto release and auto-publishing #70
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 #67
You will need to add two secret variables to the repo,
GITHUB_TOKEN, which needs write access, andNPM_TOKENwhich you can generate from NPM. This should only run when you make a push to the master branch.I tested an almost exact setup in my fork of the repository at https://github.com/jhechtf/yrv/tree/wip/auto-publish, which worked as expected. However, in that case I was publishing to a Verdaccio registry I setup on a self-hosted EC2 instance. I'll leave the EC2 instance up for the next couple of days JIC you want to see the registry to verify you can grab the URL from the linked branch.