CI publishing failure

[TonioGela]

https://github.com/davenverse/shellfish/actions/runs/9536591783/job/26283758538

I think it may be related to this and that we may need to update the credentials in the repo secrets, but maybe I'm wrong. Arman may know something about it.

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

[armanbilge]

we may need to update the credentials in the repo secrets

In Davenverse, the credentials are not repo secrets but org-wide secrets. So if this is broken, chances are it's broken for all the repositories and we need Chris to fix it.

[ChristopherDavenport]

Give it a shot again, I have updated secrets. I may need to reverify all my domains, which concerns me. But definitely a starting point to have the new user token credential flow.

[TonioGela]

Thanks Chris, I will!

[TonioGela]

Give it a shot again, I have updated secrets. I may need to reverify all my domains, which concerns me. But definitely a starting point to have the new user token credential flow.

Apparently is still a no-go? https://github.com/davenverse/shellfish/actions/runs/9828576168/job/27132698089

[armanbilge]

I think we need to add ThisBuild / tlSonatypeUseLegacyHost := true to the build. Davenverse is still on the old host.

[TonioGela]

I think we need to add ThisBuild / tlSonatypeUseLegacyHost := true to the build. Davenverse is still on the old host.

It still doesn't seem to fix :\

[ChristopherDavenport]

https://github.com/davenverse/whale-tail/actions/runs/9960562772/job/27520171122

Success! You are go for launch!

[TonioGela]

https://github.com/davenverse/whale-tail/actions/runs/9960562772/job/27520171122

Success! You are go for launch!

I just retriggered and this time I got a 403. Maybe you've find the right method to do that but this repo has different credentials?

[TonioGela]

Gentle nudge to @ChristopherDavenport