Upgrade central-publishing-maven-plugin to 0.11.0 - #17
Merged
merlimat merged 1 commit intoJul 31, 2026
Conversation
The 0.8.0 release deployed successfully but the workflow failed red: the Central portal API now returns a "warnings" field in the deployment status response, which the 0.7.0 client rejects as an unrecognized property while polling. 0.11.0 understands the current API.
There was a problem hiding this comment.
Pull request overview
Updates the build’s Sonatype Central publishing tooling to avoid CI failures caused by new fields in the Central portal deployment-status API response, ensuring future releases can complete successfully.
Changes:
- Bump
central-publishing-maven-pluginfrom0.7.0to0.11.0.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
The v0.8.0 publish workflow failed after the deployment had already succeeded server-side (all 7 modules are live on Maven Central): the Central portal's deployment-status API now includes a
warningsfield, and the 0.7.0 client fails deserializing it while polling:Bumping to the current 0.11.0 so future tag pushes go green.