Skip to content

claude: silence GPG passphrase-decryption stacktrace in release logs #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Liam-DeVoe merged 1 commit into from
Jun 12, 2026
Merged

claude: silence GPG passphrase-decryption stacktrace in release logs #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -304,6 +304,15 @@
<goal>sign</goal>
</goals>
<configuration>
<!-- Never read a passphrase from settings.xml. Our release key has no
passphrase, but actions/setup-java templates a gpg.passphrase server
entry into the runner's settings.xml whenever gpg-private-key is
supplied (even with no gpg-passphrase input), and resolving it dumps
a harmless-but-noisy SecDispatcherException stacktrace (no
~/.m2/settings-security.xml) into the release logs. If the key ever
gains a passphrase, supply it via the MAVEN_GPG_PASSPHRASE
environment variable. -->
<bestPractices>true</bestPractices>
<gpgArguments>
<!-- don't ask for passphrase. might not be required-->
<arg>--pinentry-mode</arg>
Expand Down
Loading