Sonatype have announced the End-of-Life Sunset Date for OSSRH, aka oss.sonatype.org: 30th June 2025. All users will need to migrate to the Central Publisher Portal.

Support for the new API

gha-scala-library-release-workflow uses the sbt-sonatype plugin to upload to Sonatype - with version v3.11.0 this has apparently gained support for new Sonatype Central API :

• feature: Support the new Sonatype Central API xerial/sbt-sonatype#474

Necessary steps

• Use updated sbt-sonatype(that has support for Sonatype's Central Portal API) #58

• Migrate Namespace at https://central.sonatype.com/publishing/namespaces is now possible, checked at 22nd May 2025. The migration tool now says "Migration of your OSSRH (oss.sonatype.org) namespace com.gu and related namespace(s) com.gu.play-googleauth to the Central Portal is possible" - we just need to decide when to do this:

• Update the default SONATYPE_CREDENTIAL_HOST used by projects to central.sonatype.com Switch to using central.sonatype.com by default #63

  gha-scala-library-release-workflow/.github/workflows/reusable-release.yml

  Lines 18 to 22 in abe60aa

  	SONATYPE_CREDENTIAL_HOST:
  	description: 'The host of your SONATYPE_PROFILE_NAME, either "oss.sonatype.org" or "s01.oss.sonatype.org"'
  	default: 'oss.sonatype.org' # The default host is going to be whatever "com.gu" is using
  	required: false # ...but if you're not the Guardian, you'll want to set this explicitly
  	type: string

• Credentials

  • An admin needs to use Generate User Token at https://central.sonatype.com/account
  • A GitHub Owner needs to update the AUTOMATED_MAVEN_RELEASE_SONATYPE_TOKEN organisation secret using the new token (in the format username:password)

• Tag and release the updated workflow, update the v1 tag

  • v1.0.4

Gradle

See:

• [Chore] Migrate to Sonatype central publisher portal source-apps#209

https://central.sonatype.com/publishing/namespaces