RUN-4569 Fix Maven Central publishing endpoint#49
Merged
Conversation
Point nexusPublishing at the new Central endpoint instead of the decommissioned oss.sonatype.org, which returns 402 and blocks the release publish.
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.
Summary
nexusPublishingat the new Central endpoint (ossrh-staging-api.central.sonatype.com) instead of the baresonatype()default, which targets the decommissionedoss.sonatype.organd now returns402, blocking release publishing.Context
The 2.0.1 release (Jackson CVE fix) built and created a GitHub Release, but the "Publish to Maven Central" step failed on
initializeSonatypeStagingRepository(402). This aligns git-plugin with the other plugin repos' publishing config so a re-released 2.0.1 reaches Maven Central.Test plan