From 564c6a1e9010acaa7d3823619f4154fe93187036 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 12 Oct 2026 13:40:28 +0000 Subject: [PATCH] fix: pin Maven 3.9.16 in the publish workflow ubuntu-latest now ships Maven 3.10.0, whose staging layout adds _remote.repositories and maven-metadata-local.xml to the Central bundle. The Central Portal rejects such bundles, which broke the 0.8.0 release. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01HvEwMTXhJm5YvHR3ZTBEer --- .github/workflows/java-publish.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/java-publish.yml b/.github/workflows/java-publish.yml index e70e984..ce02e14 100644 --- a/.github/workflows/java-publish.yml +++ b/.github/workflows/java-publish.yml @@ -55,6 +55,13 @@ jobs: gpg-private-key: ${{ secrets.MAVEN_GPG_PRIVATE_KEY }} gpg-passphrase: MAVEN_GPG_PASSPHRASE + # Maven 3.10 (now on ubuntu-latest) leaks local-repository files into the Central bundle, + # which the Central Portal rejects. Pin 3.9.x until central-publishing-maven-plugin handles it. + - name: Set up Maven + uses: stCarolas/setup-maven@v5 + with: + maven-version: 3.9.16 + # Gate the release on the same quality bar as CI so a broken build can never be published. - name: Check formatting (Spotless) run: mvn -B spotless:check