fix: bump central-publishing-maven-plugin to 0.11.0 - #484
Conversation
Sonatype Central now returns a "warnings" field in the deployment status response. Plugin 0.4.0 rejects unknown fields, so release:perform fails after the bundle is already uploaded. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (9)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe pull request updates the Sonatype Central publishing Maven plugin from ChangesCentral publishing plugin version alignment
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Sonatype Central started returning a
warningsfield in the deployment status response. Plugin 0.4.0 fails Jackson deserialization on it, sorelease:performerrors out after the bundle has already been uploaded (1.22.78 is on Central despite the red build). 0.11.0'sDeploymentApiResponsemodel has the field. Same bump in the generated poms so the next release does not depend on regeneration order.🤖 Generated with Claude Code
Summary by CodeRabbit