Repository navigation
fix(release): bump central-publishing-maven-plugin to 0.12.0 for Maven 3.10 compatibility - #955
Merged
Conversation
…n 3.10 compatibility Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
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.
Problem
The release workflow failed for tag
v4.1.0-beta(run). Sonatype rejected every module withBundle has content that does NOT have a .pom file.Root cause
The GitHub
ubuntu-24.04runner image moved from Maven 3.9.16 (image 20260927.320) to Maven 3.10.0 (image 20261012.334). Maven 3.10.0 writesmaven-metadata-local.xmland_remote.repositoriesinto the staging repository.central-publishing-maven-plugin0.11.0 does not remove these files, so they end up in the bundle.The 4.0.1 release (Maven 3.9.16) logs
Bundling - deleted .../maven-metadata-central-staging.xmllines. The failed run has none.Sonatype fixed this in 0.12.0 (13 Oct 2026). See the Release Notes and sonatype-nexus-community/central-publishing-maven-plugin#1.
Change
Bumps
org.sonatype.central:central-publishing-maven-pluginfrom0.11.0to0.12.0in thesonatypeDeployprofile. Nothing else changes.Verified with
mvn -N help:effective-pom -PsonatypeDeploy: the plugin resolves to 0.12.0.