docs: tell how to create branches for releases#2613
Merged
aignas merged 1 commit intobazel-contrib:mainfrom Feb 15, 2025
Merged
docs: tell how to create branches for releases#2613aignas merged 1 commit intobazel-contrib:mainfrom
aignas merged 1 commit intobazel-contrib:mainfrom
Conversation
aignas
approved these changes
Feb 15, 2025
Collaborator
aignas
left a comment
aignas
left a comment
There was a problem hiding this comment.
+1 on doing patch releases through branches.
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
2 participants
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.
It's easier to do patch releases when the branch is already created. Some of the bugs
fixes in recent releases we probably could have easily released as patch releases if
we already had the branch ready.