Skip to content

fix: extract GPG key ID from imported key#120

Merged
rtibbles merged 1 commit into
mainfrom
fix/extract-gpg-key-id
Mar 21, 2026
Merged

fix: extract GPG key ID from imported key#120
rtibbles merged 1 commit into
mainfrom
fix/extract-gpg-key-id

Conversation

@rtibbles

Copy link
Copy Markdown
Member

Summary

The GPG_KEY_ID secret doesn't exist in the repo — only GPG_SIGNING_KEY and GPG_PASSPHRASE are configured. Extract the key ID automatically from the imported key using gpg --list-secret-keys --with-colons and pass it via GITHUB_ENV to the signing step.

References

Reviewer guidance

Single-line change: after importing the GPG key, extract its ID using the machine-parseable --with-colons format (field 5 = key ID) and export via GITHUB_ENV. Removes the dependency on a GPG_KEY_ID secret.

AI usage

Claude Code identified the missing secret and proposed extracting the key ID from the imported key. Verified the extraction command in an ubuntu:latest container.

There is no GPG_KEY_ID secret configured. Extract the key ID from the
imported GPG_SIGNING_KEY using gpg --list-secret-keys --with-colons
and pass it via GITHUB_ENV.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@rtibbles rtibbles merged commit 2f40ca2 into main Mar 21, 2026
14 checks passed
@rtibbles rtibbles deleted the fix/extract-gpg-key-id branch March 21, 2026 01:41
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