setup CI for publish #263
Merged
setup CI for publish #263
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
|
If we want to go down the path of setting up a monorepo then using chanegsets in the CI for publishing would be an easier route. That way we can handle semver much easier, and roll multiple merges into single releases. Changesets seems to be a common standard these days. Here’s an example of how I have it setup on another project. |
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.
Setup CI for automatic publish of NPM package based on the tag:
v*pattern with-presubstring will be published as pre-release versions (npm publish --tag next)v*pattern will be published as latest package version (npm publish)