Merged
Conversation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
priettt
force-pushed
the
priettt/mavenCentralMigration
branch
from
bba578c to
6059c8d
Compare
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.
Goal
The legacy OSSRH publishing service will be sunset on June 30th, 2025. [Notice here]
[Here] are the differences between Legacy OSSRH and Central Portal.
I already migrated the repo through self-service migration and generated a new token, which will be set as a secret in this repo.
This PR follows the docs on [this page] to use the new URLs. It seems like it's a short-term solution for the migration, as they intend users to use another API for publication. I'd wait until there's an official Gradle plugin released for Central Portal publication, or we could also migrate everything to use https://github.com/vanniktech/gradle-maven-publish-plugin.
In the meantime, this should allow us to release after June 30th.