From 2a31a6ec0076e1a576bbd53c7d0eb5d773daf998 Mon Sep 17 00:00:00 2001
From: Kevin Herron <kevinherron@gmail.com>
Date: Mon, 19 Oct 2026 06:15:47 -0700
Subject: [PATCH 1/2] Maven dependency updates 2026-10-19

Update central-publishing-maven-plugin from 0.11.0 to 0.12.0 and refresh
the release workflow comment while retaining the pinned Maven version.
---
 .github/workflows/maven-release.yml | 3 +--
 pom.xml                             | 2 +-
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/maven-release.yml b/.github/workflows/maven-release.yml
index 2ea8d7e420..7bbae691f2 100644
--- a/.github/workflows/maven-release.yml
+++ b/.github/workflows/maven-release.yml
@@ -72,8 +72,7 @@ jobs:
           distribution: 'temurin'
           overwrite-settings: false
 
-      # central-publishing-maven-plugin 0.11.0 leaves Maven 3.10 staging metadata in the bundle,
-      # and Central rejects it. Keep this in step with the Maven version in .mise.toml.
+      # Keep release publishing on the Maven version pinned in .mise.toml.
       - name: Set up Maven
         shell: bash
         env:
diff --git a/pom.xml b/pom.xml
index 6384319882..fef4eab1ce 100644
--- a/pom.xml
+++ b/pom.xml
@@ -72,7 +72,7 @@
     <xmlunit.version>2.14.0</xmlunit.version>
 
     <!-- Plugin Dependency Versions -->
-    <central-publishing-maven-plugin.version>0.11.0</central-publishing-maven-plugin.version>
+    <central-publishing-maven-plugin.version>0.12.0</central-publishing-maven-plugin.version>
     <checkstyle.version>12.3.1</checkstyle.version>
     <jaxb2-maven-plugin.version>4.2.0</jaxb2-maven-plugin.version>
     <license-tool-plugin.version>1.1.0</license-tool-plugin.version>

From e59f15bbca3d2f60e4f06c5e4237da1c615fb860 Mon Sep 17 00:00:00 2001
From: Kevin Herron <kevinherron@gmail.com>
Date: Mon, 19 Oct 2026 06:52:09 -0700
Subject: [PATCH 2/2] Maven dependency updates 2026-10-19

Update the mise Maven toolchain from 3.9.16 to 3.10.0 and remove the
release workflow's manual Maven installation. Central Publishing 0.12.0
fixes the metadata bundling failure that required the 3.9.16 workaround.
---
 .github/workflows/maven-release.yml | 17 -----------------
 .mise.toml                          |  2 +-
 2 files changed, 1 insertion(+), 18 deletions(-)

diff --git a/.github/workflows/maven-release.yml b/.github/workflows/maven-release.yml
index 7bbae691f2..ac7dc01e8f 100644
--- a/.github/workflows/maven-release.yml
+++ b/.github/workflows/maven-release.yml
@@ -72,23 +72,6 @@ jobs:
           distribution: 'temurin'
           overwrite-settings: false
 
-      # Keep release publishing on the Maven version pinned in .mise.toml.
-      - name: Set up Maven
-        shell: bash
-        env:
-          MAVEN_VERSION: 3.9.16
-          MAVEN_SHA512: 831a8591fe20c8243b1dbe7d71e3244f31d1665b0804b2e825e38cbbe5ce0cafb8338851f90780735568773e0a6cd07bbec107cda0b896b008b861075358b6f6
-        run: |
-          set -euo pipefail
-
-          archive="apache-maven-${MAVEN_VERSION}-bin.tar.gz"
-          curl -fsSL -o "${RUNNER_TEMP}/${archive}" \
-            "https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/${MAVEN_VERSION}/${archive}"
-          echo "${MAVEN_SHA512}  ${RUNNER_TEMP}/${archive}" | sha512sum -c -
-
-          tar -xzf "${RUNNER_TEMP}/${archive}" -C "${RUNNER_TEMP}"
-          echo "${RUNNER_TEMP}/apache-maven-${MAVEN_VERSION}/bin" >> "${GITHUB_PATH}"
-
       - name: Install GPG secret key
         run: |
           cat <(echo -e "${{ secrets.ORG_GPG_PRIVATE_KEY }}") | gpg --batch --import
diff --git a/.mise.toml b/.mise.toml
index 8f3fbf0cbe..18e28b284c 100644
--- a/.mise.toml
+++ b/.mise.toml
@@ -1,3 +1,3 @@
 [tools]
 java = "temurin-17.0.19+10"
-maven = "3.9.16"
+maven = "3.10.0"