Repository navigation
Conversation
Maven 3.10 only sends the credentials of server id 'central' to Maven Central itself (repo.maven.apache.org), so deploys to central.sonatype.com fail with HTTP 401. Use the id 'sonatype-central' instead.
This branch has not been deployed
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.
GitHub's ubuntu runners now come with Maven 3.10, which only hands the credentials of server id
centralto Maven Central itself. Snapshot deploys to central.sonatype.com then fail with HTTP 401. I ran into this in other projects today, so this switches the id tosonatype-centralin the pom and in the deploy workflow.Your last snapshot deploy on Sep 21 still went through, so the next push to master would probably be the first one to fail.
Please note that for releases, the
<server>entry in your ~/.m2/settings.xml needs the new idsonatype-centralas well. The GitHub secrets can stay as they are.