[10.x] Improve releases flow #51213
Merged
[10.x] Improve releases flow #51213
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
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.
I finally managed to crack the way to generate release notes and automatically clean them up. We can now release everything from a single starting point. Additionally, the changelog is updated as soon as a release is done.
Unfortunately doing it all from the GitHub releases UI was a bit too much as deleting and regenerating the tag loses the connection between the release and the GitHub action. But with this action we still have a nice way to do releases.
Lastly, I added an additional safety check to make sure we don't accidentally tag the wrong branch.