Enable GitHub Actions publishing #83
Merged
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
friederbluemle
force-pushed
the
publish
branch
from
82cdf51 to
3f8f692
Compare
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.
This enables publishing of new releases to npm via GitHub Actions, reducing the "manual" steps to two simple commands:
npm version <major|minor|patch>git push --follow-tagsThe first command updates the version in
package.json, commits the changes, and creates a tag. The second command pushes both the commit and tag in a single operation. That's it!Once GitHub Actions sees a new version tag, it will take care of the rest: Publishing the new version to npm. The required token (
NPM_TOKEN) has already been added to this repo.