From 6dbebad5db6a20be8fc2ca7ab480d10ac7f4e3b1 Mon Sep 17 00:00:00 2001
From: William Callahan <william@aventure.vc>
Date: Sun, 8 Nov 2026 18:17:43 -0800
Subject: [PATCH] build(release): publish a validated Central Portal deployment
 automatically

Release v0.1.6 uploaded deployment c7a8e1c4 with publishingType
USER_MANAGED: the Portal validated it, then held it until someone
published it by hand in the Portal UI, so a published GitHub release left
Maven Central without the version consumers pin. The Portal's own
validation (signatures, POM, sources and javadoc jars) already gates the
upload, so the manual step blocked delivery without guarding anything
else. AUTOMATIC publishes the deployment once validation passes.

Agent-Session: 773d5d94-4b99-45c5-b312-e1a4935ccc6b
---
 build.gradle.kts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/build.gradle.kts b/build.gradle.kts
index e42ed5d..c7b29e6 100644
--- a/build.gradle.kts
+++ b/build.gradle.kts
@@ -243,6 +243,6 @@ nmcp {
     publishAllPublicationsToCentralPortal {
         username.set(providers.environmentVariable("SONATYPE_USERNAME").orNull)
         password.set(providers.environmentVariable("SONATYPE_PASSWORD").orNull)
-        publishingType.set("USER_MANAGED")
+        publishingType.set("AUTOMATIC")
     }
 }