From 03e02ad04ed4a41333d6aa9ff77f1c382d62ae09 Mon Sep 17 00:00:00 2001
From: Pratyush Sharma <56130065+pratyush618@users.noreply.github.com>
Date: Sun, 28 Jun 2026 14:57:08 +0530
Subject: [PATCH] ci(java): auto-release the Maven Central deployment
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

publishToMavenCentral only stages the Central Portal deployment (state stays VALIDATED, needs a manual Publish click). Use publishAndReleaseToMavenCentral so the release completes automatically — 0.18.0 had to be released by hand.
---
 .github/workflows/publish-java.yml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/publish-java.yml b/.github/workflows/publish-java.yml
index c853abf9..5307c735 100644
--- a/.github/workflows/publish-java.yml
+++ b/.github/workflows/publish-java.yml
@@ -162,7 +162,10 @@ jobs:
           ORG_GRADLE_PROJECT_mavenCentralPassword: ${{ secrets.MAVEN_CENTRAL_PASSWORD }}
           ORG_GRADLE_PROJECT_signingInMemoryKey: ${{ secrets.SIGNING_KEY }}
           ORG_GRADLE_PROJECT_signingInMemoryKeyPassword: ${{ secrets.SIGNING_KEY_PASSWORD }}
-        run: ./gradlew publishToMavenCentral -x cargoBuild -x copyNative --no-daemon
+        # `publishAndReleaseToMavenCentral` uploads AND releases the Central Portal
+        # deployment. Plain `publishToMavenCentral` only stages it (state stays
+        # VALIDATED), requiring a manual "Publish" click in the portal.
+        run: ./gradlew publishAndReleaseToMavenCentral -x cargoBuild -x copyNative --no-daemon
 
       - name: Create git tag
         if: github.event_name != 'push' && !inputs.dry-run