Repository navigation
Fix Central publishing credential lookup on Maven 3.10 - #1000
Merged
Merged
Conversation
cushon
approved these changes
Oct 12, 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.
Snapshot publishing began failing (example) with HTTP 401 after the GitHub runner upgraded to Maven 3.10. The publishing credentials used the ID
central, which Maven associated with the built-in dependency repository atrepo.maven.apache.org; it therefore withheld those credentials when uploading tocentral.sonatype.com.Use
central-portalconsistently in the publishing plugin and both snapshot and release workflows. This separates publishing credentials from the dependency repository and lets Maven use its existing fallback for publishing server IDs without a declared origin.Publishing against Sonatype remains to be confirmed in CI. Explicit origin binding and removal of the fallback warning are tracked in #999, once actions/setup-java#1282 is available in a released action version.