Stage changes to release v9.1.2 #302
Merged
+1
−1
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
v9.1.1 got released from the main branch, which contained a breaking change. Need to remove the tag from the main branch so that semantic-release can release v9.1.2 from this branch.
jonluca
approved these changes
Jan 24, 2023
|
LGTM |
|
🎉 This PR is included in version 9.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 9.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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 PR will configure semantic-release to release a patch version v9.1.2 off the v9 branch, which should revert the breaking change introduced in v9.1.1.
Once this is merged, the release should actually fail with error:
The
v9.1.1tag will need to be moved from the main branch to thev9.1.xbranch. (This means the git tag will become out of sync with what got released to npm.) Once this tag is moved, rerunning the actions should releasev9.1.2.Once this is released, version 9.1.1 will need to be deprecated on npm manually.