Repository navigation
fix: bump central-publishing-maven-plugin to 0.12.0 - #171
Merged
Merged
Conversation
Maven 3.10 names the staging metadata file maven-metadata-local.xml. Plugin 0.11.0 only removes maven-metadata-central-staging.xml before bundling, so the file was uploaded and Central rejected the deployment with 'Bundle has content that does NOT have a .pom file'. 0.12.0 removes it.
nawforce
approved these changes
Oct 16, 2026
nawforce
approved these changes
Oct 16, 2026
This was referenced Oct 21, 2026
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 5.3.0 Maven publish failed twice with a Central validation error:
The GitHub ubuntu-24.04 runner image moved from Maven 3.9.16 to 3.10.0 between the 5.2.0 and 5.3.0 releases. Maven 3.10 writes the staging metadata as
maven-metadata-local.xml, but plugin 0.11.0 only removesmaven-metadata-central-staging.xmlbefore bundling, so the file ended up in the bundle at the artifact level with no pom alongside it. The 5.2.0 log shows the old file being removed; the 5.3.0 log doesn't.Checked locally with Maven 3.10.0 by building the bundle with the upload pointed at a dead port. With 0.11.0 the zip contains
io/github/apex-dev-tools/apex-parser/maven-metadata-local.xml. With 0.12.0 the plugin removes it and the zip has only the5.3.0/artifacts. Fullnpm run buildpasses (203 npm tests, 202 JVM tests).Once merged, running the Publish to Maven workflow manually on
mainwill publish 5.3.0, sincemainis still at that version.