docs: add guide for patching and shipping older releases#866
Open
nathanklick wants to merge 1 commit into
Open
docs: add guide for patching and shipping older releases#866nathanklick wants to merge 1 commit into
nathanklick wants to merge 1 commit into
Conversation
Document the tag-driven release flow and the steps to back-port a fix to an older release line (worked example: patching off v0.14.5). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Nathan Klick <nathan@swirldslabs.com>
anthony-swirldslabs
approved these changes
Jun 24, 2026
Contributor
|
The commit on this PR is unverified. |
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
3 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.
Summary
Adds
docs/patch-release.md, a guide for back-porting a fix to an older release line and shipping a new patch version.It documents:
vX.Y.Ztag, derives the version from the tag name, and publishes to Maven Central + the Gradle Plugin Portal (non-prerelease tags only).main, so patching means branching off the old tag.v0.14.5, including the version-collision gotcha (the new release must bev0.14.7sincev0.14.6already exists), cherry-pick with-x -s, build verification, and tag/push to ship.Docs-only change.
🤖 Generated with Claude Code