Does your snapshot publishing to Maven Central wor...

# random

[Piotr Krzemiński]

Does your snapshot publishing to Maven Central work fine? Mine stopped working with

Could not PUT '<https://s01.oss.sonatype.org/content/repositories/snapshots/io/github/typesafegithub/shared-internal/2.1.1-SNAPSHOT/shared-internal-2.1.1-20240615.071023-13.jar|https://s01.oss.sonatype.org/content/repositories/snapshots/io/github/typesafegithub/shared-internal/2.1.1-SNAPSHOT/shared-internal-2.1.1-20240615.071023-13.jar>'. Received status code 401 from server: Content access is protected by token

(full logs). I rotated the access token, doesn't help.

[louiscad]

Try #C8C4JTXR7

[Piotr Krzemiński]

I'll probably get not kotlin but kotlin colored there :P

[louiscad]

Who cares

[eygraber]

I got an email about something like this recently.

Dear Maven Central publisher,

We are making changes to the OSSRH authentication backend. For most users this should be a transparent process, and you should be able to continue to use your existing username and password to connect the Nexus UI. In case you need to update your password, please follow our documentation.

To configure a publisher’s plugin authentication you would need to update your plugin settings to use a user token instead of the Nexus UI username and password login.

For more information about publishing to legacy OSSRH please consult our documentation at https://central.sonatype.org/register/legacy/

Thank you,

The Central Team

[Piotr Krzemiński]

Yeah, I got it as well, but I don't quite get what else I should do apart from using the user token. I've already done it

[Piotr Krzemiński]

problem solved - it turned out I had to generate the token via the UI under https://s01.oss.sonatype.org/, not https://oss.sonatype.org/. Looks like they use separate token spaces. It's unclear to me why I have access to both, kinda weird

[louiscad]

How did you find out?

[Piotr Krzemiński]

Thanks to this helpful soul that somehow noticed the ticket: https://github.com/typesafegithub/github-workflows-kt/issues/1501#issuecomment-2178942775. Sonatype folks were responsive, but they asked me to write from the e-mail that is attached to my account, but by then I already had the solution