Document the release process #247
Merged
Conversation
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
Merged
Kobzol
force-pushed
the
document-release-process
branch
from
1fc1d49 to
76a3c7b
Compare
oli-obk
reviewed
Jul 8, 2025
Kobzol
force-pushed
the
document-release-process
branch
from
76a3c7b to
f7a70a5
Compare
oli-obk
approved these changes
Jul 8, 2025
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 tried to add support for
release-plz, but this repo is a bit complicated regarding the package setup, and since we do releases infrequently, I think we can just continue using what we do now. However, the process was undocumented. I tried to recreate the process based on historical discussions and PRs in this repo, hopefully it is accurate.I'll try to do a release based on it.