Closed
Conversation
abmusse
force-pushed
the
add-release-it
branch
from
084a9e4 to
56dd35b
Compare
abmusse
force-pushed
the
add-release-it
branch
from
56dd35b to
0a1b0b2
Compare
Member
Author
|
closing in favor of #374 |
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.
https://www.npmjs.com/package/release-it
To generate a release use one of the npm scripts based on the release types.
npm run releasenpm run release-itwhich will prompt you for the release type.These scripts will bump the version number, make a release commit, tag the release, and finally create a github release if the user has
GITHUB_TOKENset.Otherwise release-it will output a URL with all the fields pre-populated see the release-it docs.
After the release is published the publish action will publish to npm.