build: auto-release to Maven Central (no manual Portal click)

Flip automaticRelease false -> true so a published GitHub release goes
live on Maven Central once it passes Portal validation, with no manual
"Publish" click. The coordinate has been through Portal validation since
0.1.0, so the one-time gate is no longer needed. (vgi-rpc-java already
auto-releases.) Update release.yml comments to match.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: rustyconover

.github/workflows/release.yml

@@ -4,9 +4,10 @@ name: Release to Maven Central
 # Publishes the library module (farm.query:vgi) to the Sonatype Central Portal
 # when a GitHub Release is published.
 #
-# NOTE: the upload is validated but NOT auto-released (automaticRelease = false
-# in build.gradle.kts). After this workflow succeeds, finish the release with
-# the "Publish" button at https://central.sonatype.com/publishing/deployments.
+# NOTE: the upload auto-releases (automaticRelease = true in build.gradle.kts):
+# once it passes Portal validation it goes live on Maven Central with no manual
+# "Publish" click. Set automaticRelease = false to re-gate on the Portal UI
+# (https://central.sonatype.com/publishing/deployments).
 #
 # Required repository secrets:
 #   MAVEN_CENTRAL_USERNAME  - Central Portal user-token username
@@ -71,7 +72,7 @@ jobs:
       - name: Test
         run: ./gradlew --no-daemon :vgi:test
 
-      - name: Publish to Maven Central (manual release in Portal UI)
+      - name: Publish to Maven Central (auto-released after validation)
         run: ./gradlew --no-daemon :vgi:publishToMavenCentral
         env:
           ORG_GRADLE_PROJECT_mavenCentralUsername: ${{ secrets.MAVEN_CENTRAL_USERNAME }}

build.gradle.kts

@@ -107,11 +107,11 @@ subprojects {
         }
 
         extensions.configure<com.vanniktech.maven.publish.MavenPublishBaseExtension> {
-            // Upload to the Central Portal but gate the final release on a
-            // manual "Publish" click in the Portal UI (https://central.sonatype.com/
-            // publishing/deployments). Flip to automaticRelease = true once the
-            // coordinate has been through Portal validation at least once.
-            publishToMavenCentral(automaticRelease = false)
+            // Auto-release to Maven Central: once the upload passes Portal
+            // validation the deployment is published without a manual "Publish"
+            // click. (The coordinate has been through validation since 0.1.0;
+            // set this back to false to re-gate on the Portal UI.)
+            publishToMavenCentral(automaticRelease = true)
 
             // Sign only when a key is available (CI / local release). Plain
             // `publishToMavenLocal` and contributor builds without a key still work.