Add GPG signing key preflight verification job to CI - #138
Merged
Conversation
Adds a standalone `verify-signing-key` job to publish.yml that reproduces what maven-gpg-plugin does at deploy time, so a bad/expired key or wrong passphrase is caught in ~20s instead of failing the publish stage. - No `needs:` — runs in parallel at the very start of the pipeline. - `environment: maven-central` — reads the SAME GPG_PRIVATE_KEY / GPG_PASSPHRASE secret the publish jobs use. - Gated to workflow_dispatch + a new `verify_signing_key` checkbox, so it never runs on normal PR/push CI and only exercises the environment gate on demand. - Prints only PUBLIC key metadata (key id, fingerprint, owner UID, algorithm, created/expiry); validates the passphrase via a throwaway sign+verify roundtrip. Passphrase is passed on fd 3 (never argv/logs), `set -x` is never enabled, and the passphrase is `::add-mask::`ed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018pwn51YPBbtiuUyiLRrfrG
Drop the workflow_dispatch checkbox and the if-gate so verify-signing-key runs unconditionally in parallel at the start of every pipeline. A red on refs where the secret is not delivered (fork PRs, other contributors' branches) is the intended signal — "this ref cannot sign a release" — not a regression. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018pwn51YPBbtiuUyiLRrfrG
bernardladenthin
had a problem deploying
to
startgate
July 9, 2026 09:16 — with 
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
July 9, 2026 09:16 — with
GitHub Actions
Failure
GitHub Actions
Failure
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
verify-signing-keyjob to the publish workflow that validates the GPG signing key and passphrase before the actual publish stageset -xto prevent accidental secret leakageTest plan
needs:dependency) and uses themaven-centralenvironment to access the same GPG secrets as the publish jobsRelated issues / PRs
Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdhttps://claude.ai/code/session_018pwn51YPBbtiuUyiLRrfrG