Sonatype integration broken

[brizzbuzz]

https://central.sonatype.org/news/20240109_issues_sonatype_org_deprecation/

:( maybe cuz of this?

[n3ziniuka5]

It's a shame that publishing to maven central is broken, because to pull an artifact from GitHub packages you must authenticate, so that needs to be done by every team member and also CI.

[brizzbuzz]

yep :( but, tbqh... i'm not very sure when I'll have time to debug this. Sonatype issues are such a pain, because there is horrible documentation, not great tooling, and a huge delay between when changes actually appear in the system.

[brizzbuzz]

Just FYI... This has led to a state where the docs are currently published for the 4.0 release, but the release is not available beyond pulling it from GitHub... hopefully I'll find some time soon to fix whatever broke with maven publishing, but till then docs will be unfortunately not matching with the actual available code :(

[brizzbuzz]

Something is completely broken w/ the sonatype ecosystem. I logged into the JIRA system they maintain to try to open a ticket, and got a message that permissions to create new tickets have been turned off.

They also seem to be in the progress of some large scale migration, not sure when that will be completed, but, unless I can somehow get in contact with support, then this project will likely just be completely blocked / broken until they finish up whatever migrations have caused all these problems.

It's really dejecting to be stuck like this, but I'm not sure what more can be done.

In the mean time, I'll likely roll back the docs to match with the latest 3.X release, and all the changes that were set for 4.0 and beyond will likely just be stuck in limbo until all of this crap is sorted out

[rocketraman]

Did you get this email from them?

Greetings Maven Central Publisher,

We are reaching out to you because you are registered as a publisher with Maven Central’s oss.sonatype.org or s01.oss.sonatype.org services. Although there are no immediate changes to how you publish, we want to inform you of a number of upcoming changes to your account. Currently, you manage your account credentials through issues.sonatype.org. On Tuesday the 12th of March, we are moving account management to a temporary service located at https://account.oss.sonatype.org/realms/central-ossrh/account/. This should hopefully involve minimal disruption for our publishers. You will still use the same username and password to log in to the OSSRH instance, and should only need to interact with the new account management service when you wish to change or reset your account credentials.

Also, you will likely see information directed at new OSSRH publishers registering via central.sonatype.com (documented here -- https://central.sonatype.org/register/legacy/). While this does not impact you at the moment, you should be aware that we are moving account management to a unified system across the Central Publishing Portal and OSSRH. We will communicate again before that takes place, to ensure that our users have a clear understanding of where and how they will be able to manage their accounts.

You may also have been impacted by the retirement of issues.sonatype.org which you previously used for signing up for new namespaces and getting publishing support. We have transitioned to using the same workflow system used for our paid products. To generate a ticket, you can email central-support@sonatype.com. We acknowledge that, in doing so, you have lost some of the self-service functionality for requesting and being granted publisher access to new namespaces. We are working on restoring that functionality on central.sonatype.com. The migration to a unified account management system we mentioned previously enables us to build integrations between the two services later in the year, such as displaying a user’s complete list
of registered namespaces and allowing self-service migration to the Publisher Portal.

[brizzbuzz]

hmmm no don't think so, though I easily could have missed it... it's the same-ish info that's available in the link I mentioned above. The problem here is mostly that I don't have the time/energy to go and hunt down whatever I need to do to get this sorted. I don't personally use this library / Kotlin any more :(

[rocketraman]

I don't personally use this library / Kotlin any more :(

Oh, that's too bad. You seem to have done a pretty amazing job with this lib. Hopefully you find some way to move forward with it, or someone to take it over.

[brizzbuzz]

Update, I've reached out to the central team via email, so will wait on their response. It looks like they've done a complete rehaul of their identity platform, and my credentials seem to have gotten messed up in the process.

So I'm going to need them to assign the bkbn namespace to my new identity, and then I should be able to publish 🤞