ci: adjust maven publishing wait until condition#738
Merged
Conversation
mojito317
approved these changes
Sep 4, 2025
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.
PR summary
Adjust maven publishing wait until condition
Fixes: s1227
PR Checklist
Please make sure that your PR fulfills the following requirements:
Angular Commit Message Guidelines.
PR Type
What is the current behavior?
Waits up to half an hour for library to publish to Maven Central, polling for state every 5 seconds.
What is the new behavior?
Waits up to an hour for library to validate, polling for state every 15 seconds.
The sync from Central Portal to Maven Central timed out during the last release. Since we always check that the release has reached Maven Central before marking the release process completed anyway we can avoid potential future timeouts by waiting only for the
validatedstate. Invalidatedstate we know the upload is good and meets the requirements of Maven Central. The sync from Central Portal is outside of our control anyway, so there is little point in failing our build if it doesn't happen.Does this PR introduce a breaking change?
Other information