Skip to content

Pin Maven 3.9 in the release workflow - #26

Merged
omphile-matheolane merged 1 commit into
mainfrom
fix-release-maven-pin
Nov 4, 2026
Merged

omphile-matheolane merged 1 commit into
mainfrom
fix-release-maven-pin

Conversation

@omphile-matheolane

Copy link
Copy Markdown
Member

Release run 2 signed and uploaded correctly, then Central rejected the bundle with "Bundle has content that does NOT have a .pom file". Root cause is Maven 3.10 on the hosted runners interacting with central-publishing-maven-plugin 0.11.0 (apache/maven#13388). Pins Maven 3.9.11 for the release job, switches to the non-deprecated gpg-passphrase-env-var input, and passes -DgenerateBackupPoms=false to versions:set.

Workflow-only change; CI does not run on it, so merge and re-dispatch.


Generated by Claude Code

Hosted runners now ship Maven 3.10, whose local-repository changes make
central-publishing-maven-plugin 0.11.0 stage bookkeeping files into the
bundle, which Central rejects. Pin 3.9.11 until the plugin catches up
(apache/maven#13388). Also move to the non-deprecated gpg-passphrase-env-var
input and skip versions:set backup POMs.
@omphile-matheolane
omphile-matheolane merged commit 3af7d9d into main Nov 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant