Improve CI Release Workflow#2208
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Motivation:
The Release workflow failed on every push to main — it ran mvnw deploy on each commit, but main sat on the already-released 3.0.11, and Maven Central rejected re-publishing immutable coordinates (async-http-client@3.0.11 already exists).
Modification:
Keep main on -SNAPSHOT and drive releases via maven-release-plugin — pushes deploy SNAPSHOTs, while a manual workflow_dispatch release checkbox strips -SNAPSHOT, tags, publishes to Central (autoPublish=true), and auto-bumps to the next -SNAPSHOT.
Result:
Pushes publish SNAPSHOTs without collision and final releases are a one-click auto-bumping run, so the pipeline no longer fails on every commit.