Repository navigation
publish-central: unlock the signing key before the build - #130
Merged
Merged
Conversation
Maven's gpg plugin will not open the passphrase dialog in batch mode (-B), so a release whose passphrase was no longer cached failed with "No pinentry". The script now signs a line first (the dialog appears up front, gpg-agent caches the passphrase) and runs Maven without -B, so the plugin may still ask the agent if the cache runs out during a long build. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Simulator 1.9.0's first publish attempt failed with
gpg: signing failed: No pinentry. When Maven runs in batch mode (-B), the gpg plugin stops gpg-agent from opening the passphrase dialog. Its own documentation says to unlock the key in the agent beforehand ("prime" it). trace-core 1.12.0 only got through because the passphrase was still cached from a test signature.bin/publish-centralsigns a line first. The passphrase dialog appears before the build, and gpg-agent then holds the passphrase. If no key is found or the passphrase isn't given, the script stops with a clear message.-B, so the plugin can still ask the agent if the cache expires during a long build.Tested: used for the Simulator 1.9.0 publish.
🤖 Generated with Claude Code