chore: set up NPM auto publish on new package version #150
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
|
mrderyk
force-pushed
the
chore/auto_publish
branch
23 times, most recently
from
5e352ea to
15df42a
Compare
mrderyk
changed the title
mrderyk
force-pushed
the
chore/auto_publish
branch
from
15df42a to
0a2da3a
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.
CONTEXT
In order to smoothly transfer changes from source to this repo, we'll need to auto-publish to NPM when a new package.json version is detected.
CHANGES
A release draft looks like this and would need to be filled in. It will only be this long for the next release because of the amount of changes since the last version.