fix: trigger release #470
Merged
fix: trigger release #470
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
|
derberg
approved these changes
Dec 13, 2023
|
/rtm |
|
🎉 This PR is included in version 6.2.0 🎉 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.
Description
Due to an issue with semantic-release not understanding a force push we had to do in order to fix authors of a commit that was already released in v6.0.1, we had to re-tag that version in order to point to the new commit hash. That triggered a release wrongly because the race condition between me manually creating the tag and CI running semantic-release.
This PR just commits an empty commit that will, if everything goes as expected, trigger a new minor release (according to release messages after v6.0.1)
Expected commits to be released:
cc @derberg