Repository navigation
[release] bump central-publishing plugin to 0.12.0 - #38
Merged
Merged
Conversation
0.6.0 bundles maven-metadata-local.xml and _remote.repositories from its staging repo. Central rejects the bundle: "Bundle has content that does NOT have a .pom file". Both v1.0.2 attempts failed on this.
stevewithey
approved these changes
Oct 22, 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.
Both v1.0.2 release attempts failed at Maven Central validation. Nothing was published.
Why
Sonatype's Publisher API gives the same error for both deployments (
d67cf8a0…,513d463b…):I rebuilt the release bundle in CI using the real release steps (GPG signing,
versions:set) but dummy Sonatype credentials, so the upload is rejected and nothing can publish. Withcentral-publishing-maven-plugin0.6.0, the bundle includes Maven's local-repository bookkeeping files from the staging repo:ai/gradientlabs/<artifact>/maven-metadata-local.xml, at the artifact level outside the version folder. These are the paths Central flags.<artifact>/1.0.2/_remote.repositories#37 (starter sources and javadoc) was a real gap too, but not the cause of this error.
What
Bump the plugin 0.6.0 → 0.12.0. The
publishingServerId,autoPublishandwaitUntilconfig is unchanged.Testing
Same dummy-credentials CI run with 0.12.0: the bundle has 54 files, all under
1.0.2/, with nomaven-metadata-local.xmlor_remote.repositories, and all three poms present. The upload then fails only on the dummy credentials.Releasing after merge
Move tag
v1.0.2to the merge commit; nothing has been published under it.