Feature: action for publishing package update #1546
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
talyguryn
requested review from
gohabereg,
khaydarov and
neSpecc
as code owners
This was referenced Feb 18, 2021
neSpecc
reviewed
Feb 19, 2021
docs/releases.md
Outdated
|
|
||
| ### Release candidate publishing | ||
|
|
||
| If you want to publish release candidate version, use suffix `-rc.*` for package version in package.json file and git tag. |
There was a problem hiding this comment.
and git tag.
Can't find this step in the example pipeline
Co-authored-by: Peter Savchenko <specc.dev@gmail.com>
Co-authored-by: Peter Savchenko <specc.dev@gmail.com>
neSpecc
approved these changes
Feb 19, 2021
gohabereg
approved these changes
Feb 19, 2021
khaydarov
approved these changes
Feb 19, 2021
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.
Release publishing
There is an action that fired on a new release publishing on GitHub.
After update merging, when a new package version is ready to be published,
create a new release with the correct version tag.
Use target version changelog as a description.
Then you can publish the release and wait for package publishing via action.
This package version will be published to NPM with default
latesttag.Release candidate publishing
If you want to publish release candidate version, use suffix
-rc.*for package version in package.json file and git tag.This package version will be published to NPM with
nexttag.Stable version:
2.19.0Release candidate:
2.19.1-rc.0,2.19.1-rc.1, ...Next version:
2.19.1Do not forget to mark this release as a pre-release!