Conversation
85a64df to
66b668b
Compare
66b668b to
a03f2ae
Compare
Contributor
|
🚀 Published in:
|
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
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.
Switches the pre-release npm tag from
betatocanary. Major/minor/patch versions are preserved, and the increment counter is carried over (e.g.7.0.0-beta.116→7.0.0-canary.116). The next changeset bump produces7.0.0-canary.117.Modeled on the previous switch from
canary→alphain ec517bb (#6355). Two intentional deviations from that PR:.0; this one preserves it so canary picks up where beta left off.initialVersionsinpre.json; this one leaves it untouched.initialVersionsis informational — the next-version computation reads from currentpackage.json, not from this field, so leaving it stale has no effect on the release plan.