Migrate publishing to Central Portal
NOTE: If you have already migrated your namespace(s) to Maven Central this email does not apply to you and thank you for your initiative.
Greetings OSSRH Publisher,
As you may have heard, OSSRH is reaching end of life on June 30, 2025. OSSRH users need to migrate their namespaces to the Central Portal as soon as possible.
Instructions for self migration are located here: https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/#self-service-migration
To make the transition smoother we will be automatically migrating publishers that have not used oss.sonatype.org or s01.sonatype.org to publish artifacts in some time starting with the oldest and working our way forward. To avoid disruption to your publishing processes we strongly encourage migrating before the June 30, 2025 deadline.
Thank you for your assistance,
The Central Team
Just in case you are not aware as many others, you can continue using maven-publish or any other plugin using the "classical way".
You just have to use a different URL, and generate a new user token from the new system.
@Vampire , what is the url? I have not seen such urls. However, I guess publishing with maven-publish won't be transactional, so if the release includes several artifacts, then some of them might get published while the rest might fail validation errors. Is it the case?
@Vampire , what is the url? I have not seen such urls.
Ah, sorry, should have posted the doc link: https://central.sonatype.org/publish/publish-portal-ossrh-staging-api/
However, I guess publishing with maven-publish won't be transactional, so if the release includes several artifacts, then some of them might get published while the rest might fail validation errors. Is it the case?
I have no idea, but I guess you end the transaction by the "close" call?
I missed they implemented staging api which is very kind of them to support backward compatibility. Staging is indeed transactional.
Publishing snapshots stopped working, probably related to this issue: https://github.com/typesafegithub/github-workflows-kt/actions/runs/16058322307/job/45318155169
Of course it did. Those servers are now decommissioned, also for snapshots you have to use a different URL and enable snapshots on the web interface.
3.5.0 published successfully through the compatibility endpoint.