search

detekt / sarif4k

Kotlin data bindings for the Static Analysis Results Interchange Format (SARIF)
Apache License 2.0
15 stars 7 forks source link

Release publishing broken #128

Open TWiStErRob opened 3 days ago

TWiStErRob commented 3 days ago 
> Task :publishJvmPublicationToSonatypeRepository FAILED

15 actionable tasks: 7 executed, 8 up-to-date
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':publishJvmPublicationToSonatypeRepository'.
> Failed to publish publication 'jvm' to repository 'sonatype'
   > Could not PUT 'https://oss.sonatype.org/content/repositories/snapshots/io/github/detekt/sarif4k/sarif4k-jvm/0.7.0-SNAPSHOT/sarif4k-jvm-0.7.0-20240628.120230-9.jar'. Received status code 401 from server: Content access is protected by token

I have the same problem in my Gradle plugin repository. I've read some news about moving to a new Auth mechanism, but I read it as optional and hoped for a longer grace period. apparently that's not the case.

@cortinico @chao2zhang who has access to Sonatype password? There'll be some secrets setup need changing probably, will know more after I fixed my repo.

TWiStErRob commented 2 days ago

Email that alerted about this for reference:

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

The process was quite simple:

  1. Log in to https://oss.sonatype.org (based on our usage of sonatype())
  2. Follow https://central.sonatype.org/publish/generate-token/
  3. Instead of step 5, replace MAVEN_CENTRAL_USER and MAVEN_CENTRAL_PW secrets at https://github.com/detekt/sarif4k/settings/secrets/actions