Fix Central publish plugin bug; bump to 0.1.1-SNAPSHOT#3
Merged
Conversation
The 0.1.0 release published to Maven Central successfully, but the release workflow reported failure: central-publishing-maven-plugin 0.7.0 crashes deserializing Central's deployment-status response now that Central returns a 'warnings' field the 0.7.0 model doesn't recognize (UnrecognizedPropertyException). The crash happens after the bundle is uploaded and set to auto-publish, so the artifacts publish anyway — but the job exits non-zero. Bump the plugin to 0.11.0, which handles the new field, so future releases report success accurately. Also move the project to 0.1.1-SNAPSHOT for post-release development. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016Bb8BttJZHuy6zh957NMGT
thinkingfish
marked this pull request as ready for review
July 12, 2026 21:16
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
2 participants
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.
Summary
Post-release follow-up.
0.1.0published to Maven Central successfully — all artifacts (jar,.ascsignature, sources, javadoc) are live atsystems.iop:h2histogram:0.1.0. But the release workflow exited non-zero due to a client-side bug in the publishing plugin, and main was left on the release version. This PR fixes both.What happened
central-publishing-maven-plugin0.7.0 crashes while polling Central's deployment-status endpoint:Central now returns a
warningsfield in that response which the 0.7.0 model doesn't know about, so Jackson throws. Crucially this happens after the bundle is uploaded and set to auto-publish — which is why 0.1.0 published fine despite the red ❌. Re-running the old workflow was not an option (Central versions are immutable).Changes
central-publishing-maven-plugin0.7.0→0.11.0(current release; tolerates the new response field), so future releases report success accurately.0.1.0→0.1.1-SNAPSHOT(main + benchmarks module) for post-release development.Verification
mvn -Prelease dependency:resolve-pluginsresolves the 0.11.0 plugin.mvn test— 36 tests pass.No action needed for the 0.1.0 release itself; it's already live. This just makes the next release green.
🤖 Generated with Claude Code
https://claude.ai/code/session_016Bb8BttJZHuy6zh957NMGT
Generated by Claude Code