From ca0ed14c6ff1acab022f3dc48510d890522a8364 Mon Sep 17 00:00:00 2001 From: Eirini Galati Date: Wed, 4 Nov 2026 16:47:25 +0100 Subject: [PATCH] fix(ci): bump central-publishing-maven-plugin to 0.12.0 Publishing 1.9.0 to Maven Central failed validation: Bundle has content that does NOT have a .pom file: com/tinify/tinify The runner image ships Maven 3.10.0, which writes maven-metadata-local.xml and _remote.repositories into the local repository layout the plugin stages from. 0.7.0 bundles them as-is, so the uploaded zip contains com/tinify/tinify/maven-metadata-local.xml -- a file at the artifact level with no version directory and therefore no .pom beside it, which is exactly what Central reports. Reproduced with Maven 3.10.0 against this pom: the staging tree gains maven-metadata-local.xml and _remote.repositories. The same build under Maven 3.9.15 is clean, which is why this never showed up locally. 0.12.0 strips them before bundling: Pre Bundling - deleted .../com/tinify/tinify/maven-metadata-local.xml Pre Bundling - deleted .../com/tinify/tinify/1.9.0/_remote.repositories Pre Bundling - deleted .../central-staging/.locks leaving the 20-file bundle Central expects, the same shape as 1.8.8. Also passes --show-version so the Maven version is in the log; its absence is what made this take a while to pin down. --- .github/workflows/ci-cd.yml | 1 + pom.xml | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci-cd.yml b/.github/workflows/ci-cd.yml index 6f8286c..aa5c8b3 100644 --- a/.github/workflows/ci-cd.yml +++ b/.github/workflows/ci-cd.yml @@ -150,6 +150,7 @@ jobs: -P release \ --settings settings.xml \ --no-transfer-progress \ + --show-version \ --batch-mode env: GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }} diff --git a/pom.xml b/pom.xml index b5fbaec..a9bf7f6 100644 --- a/pom.xml +++ b/pom.xml @@ -256,7 +256,7 @@ org.sonatype.central central-publishing-maven-plugin - 0.7.0 + 0.12.0 true central