Sonatype migration - #733
Merged
Merged
Conversation
CherryPerry
force-pushed
the
publishing-migration
branch
6 times, most recently
from
May 10, 2025 16:30
d7e5162 to
7104bbd
Compare
CherryPerry
marked this pull request as ready for review
May 10, 2025 16:30
CherryPerry
force-pushed
the
publishing-migration
branch
from
May 12, 2025 14:12
7104bbd to
5c11611
Compare
KovalevAndrey
approved these changes
May 12, 2025
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.
Description
Sonatype is deprecating the way we publish the library. We have to migrate to the new process before the June 30, 2025, deadline.
Unfortunately, we have to use a third-party plugin, as Gradle does not support it yet.
Migration doc: https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/
Check list
CHANGELOG.mdif required.