Repository navigation
Allow release retries after Maven Central publication - #49
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.
The first 5.8.0 release attempt published to Maven Central, then failed while assembling GitHub download assets. Retrying currently fails because Central versions are immutable and the component already exists.
Tell the Central plugin to reuse published components and wait until a new component is published. Add a manual retry entry point restricted to
main, and serialize release attempts. Every retry still runs the validation gate, builds the signed artifacts, and assembles the GitHub downloads.Validation: downloaded the published 5.8.0 sources JAR and compared all 378 source/resource files against the current tree; all match. The previous release log confirms successful Central validation before the later failure. A local deployment run with
ignorePublishedComponents=truesuccessfully detected 5.8.0, excluded it from staging, and finished without uploading a duplicate.