Repository navigation
Publish releases automatically when a version tag is pushed - #63
Merged
Merged
Conversation
Let central-publishing-maven-plugin publish the deployment and wait up to an hour for Central to report it published, then create the GitHub release directly instead of as a draft. The bundle dry run still uploads to an unreachable URL, so autoPublish never applies to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Pushing a
vX.Y.Ztag now publishes the whole release, with no manual steps.pom.xml: central-publishing-maven-plugin setsautoPublish=true,waitUntil=publishedandwaitMaxTime=3600. Central publishes the deployment after validation, and the job waits up to an hour until it's live.release.yml:gh release createno longer passes--draft, so the GitHub release (with generated notes) is published once Central is live.README.md: the release steps go from 5 to 3. Adds a note that the tag push is now final, and how to create the GitHub release by hand if the job fails after Central has published.The manual bundle dry run is unchanged and still safe: it uploads to
127.0.0.1:9with placeholder credentials, so the upload fails beforeautoPublishcould apply. Verified with a dry run on this branch.This only affects future tags. 5.0.0 was uploaded under the old flow and still needs publishing by hand.
🤖 Generated with Claude Code