ci: add publish action for releases #2181
Merged
+28
−0
Conversation
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.
Defines a GitHub action to publish releases from GitHub CI using the npm trusted publishers method.
I've tested this on a smaller project I maintain (jsonresume/jsonresume-theme-class) and everything went great, so I'm adopting this in svg/svgo as well.
This makes the process of releasing a little less stressful, and significantly reduces the likelihood for human error, like releasing versions under the wrong dist-tag. 😓
The only difference between this workflow and other ones I've defined is that for SVGO, I use
jqto check if the version name includes-rc.which indicates it's a release candidate. If so, we use thercdist-tag.