Publish to Maven Central with new interface

[Tammo0987]

Hello,
I am asking for help. Since it seems like, that the old Jira from Sonatype will be shutdown and only https://central.sonatype.com will be used. I wanted to ask if I can get currently the plugin running with an user token created from the new interface and how I should configure it.

When I use s01.oss.sonatype.org as described, I get an error for to many redirects.

[rlemaitre]

I've the same issue. I cannot publish to central.sonatype.org due to too many redirect errors

[xerial]

I wasn't aware of this change: https://central.sonatype.org/register/central-portal/#switching-to-ossrh-during-portal-early-access. In fact, I don't know much about this change and I don't have an account on the new http://central.sonatype.org/ to test it.

It seems Sonatype has renewed almost all steps to register new domains, so I also need to relearn everything from scratch, including its API and token management 😓

[xerial]

If you can identify what needs to be fixed in sbt-sonatype and highlight the necessary code changes (for example, a pull request), I would appreciate it. I can create a new release soon.

[windymelt]

Almost same issue here (encountered by using sbt-typelevel). Sonatype says they provide new API for publishing artifacts. We may use new endpoint, new API.

I'll check code anyway :)

[xerial]

It looks like a big change and more automation has been added on the sonatype side 😮 https://central.sonatype.org/publish/publish-portal-api/

[xerial]

At first glance, it looks like a huge improvement. I'd like to support the new https://central.sonatype.com/ API in sbt-sonatype 4.x

[windymelt]

According to the documentation, it is no longer possible to create a new account on the old system, so Scala library author who recently created an account on the new system are effectively unable to publish libraries (except hand-made publish process).

[Andrapyre]

See the following PR for an initial implementation that offers Sonatype Central support: #474

[Andrapyre]

For users needing immediate support to publish libraries, the following is a temporary workaround:

1. Download the changes in feature: Support the new Sonatype Central API #474.
2. Run

sbt "compile; publishLocal"

3. Copy the package id from the output: <User Dir>/.ivy2/local/org.xerial.sbt/sbt-sonatype/scala_2.12/sbt_1.0/<package-id>/ivys/ivy.xml
4. Go to your project, checkout a new branch, and add the following to plugins.sbt :

addSbtPlugin("org.xerial.sbt" % "sbt-sonatype" % "<package-id>")

5. In your project, add the following to your build.sbt:

import xerial.sbt.Sonatype.sonatypeCentralHost

ThisBuild / sonatypeCredentialHost := sonatypeCentralHost
ThisBuild / version := "<target version>"

6. Generate credentials in Sonatype Central and add them to your .zsh like so:

export SONATYPE_USERNAME="<sonatype_username>"
export SONATYPE_PASSWORD="<sonatype_password>"

7. If you have not already done so, follow the instructions here to set up GPG.
8. Run the following and paste in your gpg-generated passphrase when prompted

sbt "publishSigned" 

9. Run

sbt "sonatypeBundleRelease"

10. Go to https://central.sonatype.com/publishing/deployments, verify that all is working as expected with your deployment and publish your component when ready.

[Ragazoor]

Heyo! Really happy to see that support for the new interface is moving along. Are there any info that can be shared regarding when we can expect a release candidate with this change included? Like was mentioned here #474

[Andrapyre]

I was in contact with Taro and he needed some extra time to review this, with one or two further considerations around user flow and naming, which are still TBD. @xerial , could we still get a release commit out in the current form, with a target date for a full 4.0.0 release in a month or two? That way we can gather user feedback while still making clear that setting names, etc. are open to change.

[Andrapyre]

@xerial , I am confused about this new release, as I'd thought that this was permanently blocked and I instead invested effort to create a separate plugin here - https://github.com/lumidion/sbt-sonatype-central with a maintenance and feature roadmap. This plugin is now in its first release...as of a few minutes before #474 was merged.

The next step to make this feature widely available is to integrate it into sbt-ci-release. Do you have bandwidth/interest in maintaining it in this repo? If yes, I will continue with my original plan from several months ago and add the changes to sbt-ci-release without introducing the plugin I've created. If not, I would request that this feature be reverted (it has commands that will conflict with the new plugin) and I will integrate the new plugin into sbt-ci-release instead.

[BillyAutrey]

Reading through this issue, a reader might assume that this is not fixed. As far as I can tell @xerial, this should be closed.

• The fix is available since https://github.com/xerial/sbt-sonatype/releases/tag/v3.11.0
• Since Update sbt-sonatype to 3.11.2 sbt/sbt-ci-release#303, 3.11.x has been upstreamed.