From 3881ac20be4c8720a643665e92372ecb15e54ff5 Mon Sep 17 00:00:00 2001
From: Doug Mealing <doug@dougmealing.com>
Date: Fri, 23 Oct 2026 03:25:20 -0400
Subject: [PATCH 1/3] fix(java): central-publishing-maven-plugin 0.12.0 so
 Maven 3.10 staging metadata stays out of the bundle

---
 server/java/pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/server/java/pom.xml b/server/java/pom.xml
index d60bcbb2c..3a1a64c8a 100644
--- a/server/java/pom.xml
+++ b/server/java/pom.xml
@@ -465,7 +465,7 @@
           <plugin>
             <groupId>org.sonatype.central</groupId>
             <artifactId>central-publishing-maven-plugin</artifactId>
-            <version>0.11.0</version>
+            <version>0.12.0</version>
             <extensions>true</extensions>
             <configuration>
               <publishingServerId>central</publishingServerId>

From bf2aa35287577381fda9ab4da61fcb29d6d7b5b6 Mon Sep 17 00:00:00 2001
From: Doug Mealing <doug@dougmealing.com>
Date: Fri, 23 Oct 2026 03:46:38 -0400
Subject: [PATCH 2/3] docs(releasing): note runner Maven version drift and the
 missing-.pom Central rejection

---
 docs/RELEASING.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/RELEASING.md b/docs/RELEASING.md
index a7fb9eb50..d6733ed61 100644
--- a/docs/RELEASING.md
+++ b/docs/RELEASING.md
@@ -852,6 +852,13 @@ versioned on its own major line — npm major + 7, so `7.x` while npm was `0.x`
 > failed with `Polling for … timed out before the deployment completed`, yet 8.0.11 is on
 > Central (HTTP 200). Check Central with the loop above before any re-run: a re-run of a
 > published version fails as a duplicate.
+>
+> **The runner's Maven version can change under the workflow.** `java-v8.1.0` was rejected with
+> `Bundle has content that does NOT have a .pom file`: the `ubuntu-24.04` image (2026-10-12 and
+> later) ships Maven 3.10.0, which writes `maven-metadata-local.xml` into the install target, and
+> `central-publishing-maven-plugin 0.11.0` left it in the staged bundle. Fixed in plugin `0.12.0`;
+> if that signature returns, inspect the bundle for `maven-metadata-local.xml` and check the
+> runner's `mvn -v` before suspecting the poms.
 
 **The `minor.patch` is CONVERGENT across languages, not lockstepped** (standing policy since
 0.25.0): npm, PyPI and NuGet share one `major.minor.patch` and Maven Central takes the same

From 32c423e367e284b2153b160f998cc098c638e6ea Mon Sep 17 00:00:00 2001
From: Doug Mealing <doug@dougmealing.com>
Date: Fri, 23 Oct 2026 03:48:40 -0400
Subject: [PATCH 3/3] docs(releasing): name the runner label and the confirming
 release

---
 docs/RELEASING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/RELEASING.md b/docs/RELEASING.md
index d6733ed61..5028ef3db 100644
--- a/docs/RELEASING.md
+++ b/docs/RELEASING.md
@@ -854,9 +854,9 @@ versioned on its own major line — npm major + 7, so `7.x` while npm was `0.x`
 > published version fails as a duplicate.
 >
 > **The runner's Maven version can change under the workflow.** `java-v8.1.0` was rejected with
-> `Bundle has content that does NOT have a .pom file`: the `ubuntu-24.04` image (2026-10-12 and
+> `Bundle has content that does NOT have a .pom file`: the `ubuntu-latest` (24.04) image (2026-10-12 and
 > later) ships Maven 3.10.0, which writes `maven-metadata-local.xml` into the install target, and
-> `central-publishing-maven-plugin 0.11.0` left it in the staged bundle. Fixed in plugin `0.12.0`;
+> `central-publishing-maven-plugin 0.11.0` left it in the staged bundle. Fixed in plugin `0.12.0` (`8.1.0` published with it);
 > if that signature returns, inspect the bundle for `maven-metadata-local.xml` and check the
 > runner's `mvn -v` before suspecting the poms.