Stop using OSSRH (Migrate to Maven Central Publishing)

[sgoudham]

We've received the following email on releases@catppuccin.com

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

I'm a little unsure if we are regarded as a "publisher" but we should look to see if we need to switch to a token based authentication workflow.

[sgoudham]

Turns out publishing to OSSRH is now considered to be the legacy workflow, we should migrate to the new workflow detailed in the link below:

https://central.sonatype.org/publish-ea/publish-ea-guide/