Skip to content

publish-central: unlock the signing key before the build - #130

Merged
jcombs-pointblue merged 1 commit into
masterfrom
publish-central-pinentry
Nov 11, 2026
Merged

jcombs-pointblue merged 1 commit into
masterfrom
publish-central-pinentry

Conversation

@jcombs-pointblue

Copy link
Copy Markdown
Contributor

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-central signs 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.
  • Maven runs without -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

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>
@jcombs-pointblue
jcombs-pointblue merged commit 0a3ea19 into master Nov 11, 2026
4 checks passed
@jcombs-pointblue
jcombs-pointblue deleted the publish-central-pinentry branch November 11, 2026 18:42
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