Clarify patch release procedures - #754
Merged
Merged
Conversation
I did a silly thing, and made a patch release PR against the release branch for the previous minor version. It was easy to make this mistake because our release instructions were unclear on patch releases. This PR fleshes them out. Historically, it's easy to see how we ended up in this situation. Our new branching model of patch releases didn't come around until after 0.5.0, and I never got around to fleshing out patch release procedures at that time. We _did_ update the release instructions right after 0.6.0, but we obviously didn't encounter any patch release steps in that release. So we should be in pretty good shape after this PR.
hoffbrinkle
approved these changes
Sep 4, 2026
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.
I did a silly thing, and made a patch release PR against the release
branch for the previous minor version. It was easy to make this mistake
because our release instructions were unclear on patch releases. This
PR fleshes them out.
Historically, it's easy to see how we ended up in this situation. Our
new branching model of patch releases didn't come around until after
0.5.0, and I never got around to fleshing out patch release procedures
at that time. We did update the release instructions right after
0.6.0, but we obviously didn't encounter any patch release steps in that
release. So we should be in pretty good shape after this PR.