fix: upgrade nexus-publish to 2.0.0 for Maven Central compatibility - #317
Merged
Conversation
- Upgrade io.github.gradle-nexus.publish-plugin from 1.1.0 to 2.0.0 - Add in-memory PGP signing support in mvn-publish.gradle - The URLs in promote.gradle were already correct; only the plugin version was stale
didiergarcia
force-pushed
the
fix/maven-central-publish-2.0
branch
from
July 27, 2026 17:20
02946dc to
ca8f5ad
Compare
wenxi-zeng
approved these changes
Jul 27, 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
2 participants
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
io.github.gradle-nexus.publish-pluginfrom1.1.0to2.0.0to fix compatibility with Maven Central's new OSSRH Staging API (ossrh-staging-api.central.sonatype.com)mvn-publish.gradle(required by nexus-publish 2.x)VERSION_NAMEto1.26.0/VERSION_CODEto1260Problem
The 1.x plugin calls the legacy
oss.sonatype.orgstaging API which no longer works with our Central Portal account, causing:The
promote.gradleURLs were already updated to point at the new portal endpoints — only the plugin version was stale.Test plan
./scripts/release.shand confirm it gets past:initializeSonatypeStagingRepositorycom.segment.analytics.kotlin:1.26.0