Handle delayed Maven Central publication and retries - #4
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.
Maven Central accepted SDK 0.0.983, but publication exceeded the plugin's default 30-minute polling limit. The workflow failed even though Central subsequently published the artifact.
Increase the publication wait to 60 minutes and enable the plugin's built-in ignorePublishedComponents option so retries omit already-published releases. Keep waitUntil=published so successful uploads alone cannot make the workflow green.
Validation: local mvn compile and git diff --check passed. Confirmed 0.0.983 is available in Central. Local retry verification reaches the authenticated component-status API, which requires CI-held credentials; verify the full signed publish workflow after merge.