Skip to content

[VFDLIBM] Move maven-gpg-plugin to 3.2.8 - #135

Merged
MaxGekk merged 1 commit into
mainfrom
gpg-plugin-3.2.8
Nov 22, 2026
Merged

MaxGekk merged 1 commit into
mainfrom
gpg-plugin-3.2.8

Conversation

@MaxGekk

@MaxGekk MaxGekk commented Nov 22, 2026

Copy link
Copy Markdown
Contributor

What changes were proposed in this pull request?

The release profile's maven-gpg-plugin moves from 3.2.7 to 3.2.8, the newest release; it is one of the plugins .github/dependabot.yml leaves out, moved by hand after a release (AGENTS.md, "Releases").
3.2.8 moves its Bouncy Castle from 1.78.1 to 1.81 (the signer the dry run uses), fixes an empty classifier passed as an empty string, adds **/*.sigstore.json to the default excludes and drops plexus-xml.
The sign goal's parameters and defaults are the same in both versions' plugin.xml, and the required Maven (3.6.3) and Java are unchanged.

Why are the changes needed?

To keep the signing plugin current, with its newer Bouncy Castle, before the next release rather than during it.

Does this PR introduce any user-facing change?

No. Build only; the jar is unchanged.

How was this patch tested?

The dry run (release.yml, which runs on a change to pom.xml) builds the bundle and signs it under 3.2.8 with the Bouncy Castle signer.
The owner's own signing through gpg and its agent is not covered by any run; it is first exercised at the next deploy, or by a local mvn -B -Prelease verify with signing before it.
A code-review high found nothing.

Generated-by: Claude Code (Opus 5.5)

Generated-by: Claude Code (Opus 5.5)
@MaxGekk
MaxGekk merged commit d3bb335 into main Nov 22, 2026
14 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