From 6c3d1a106bfc319645fe7cf1293e783658a9610b Mon Sep 17 00:00:00 2001 From: Steven Ourada Date: Thu, 14 Nov 2024 14:53:57 -0600 Subject: [PATCH] Update to user tokens Per https://central.sonatype.org/news/20240301_changes_to_account_management/#new-publishers-who-will-be-publishing-via-ossrh (and because we got a 401 error publishing the old way), we now have to use user tokens to publish. I followed the instructions here: https://central.sonatype.org/publish/generate-portal-token/ and generated a token username/password pair, which I added to the 1Password entry for Sonatype, and to Github actions secrets. I think this yml update will cause the publish action to use the new things. --- .github/workflows/publish.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index 98a953a..c108c43 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -31,8 +31,8 @@ jobs: ./gradlew \ -P signingKey=${{ secrets.ORG_GRADLE_PROJECT_signingKey }} \ -P signingPassword=${{ secrets.ORG_GRADLE_PROJECT_signingPassword }} \ - -P sonatypeUsername=${{ secrets.SONATYPE_USERNAME }} \ - -P sonatypePassword=${{ secrets.SONATYPE_PASSWORD }} \ + -P ossrhUsername=${{ secrets.OSSRH_USERNAME }} \ + -P ossrhPassword=${{ secrets.OSSRH_PASSWORD }} \ publishToSonatype \ closeAndReleaseSonatypeStagingRepository ./scripts/publish.sh