Repository navigation
ci(signing): verify GPG signatures in GitHub Actions - #35
Merged
Merged
Conversation
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
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
Creating a separate GPG-signing job in the CI pipeline.
That :
Is triggered manually via
workflow_dispatch;can be triggered after a push to
main;imports the private key;
runs
mvn clean verify -Pgpg-signing;verifies the generated
.ascfiles.This aligns with the Maven recommendation to use
MAVEN_GPG_PASSPHRASEfor unattended/CI environments, while allowing developer machines to continue using the GPG agent.This provides a genuine GPG test within GitHub Actions without cluttering the standard CI process.