feat: sign release tags when git signing is configured#5
Merged
outofcoffee merged 1 commit intomainfrom Apr 20, 2026
Merged
Conversation
When tag.gpgSign or tag.forceSignAnnotated is set in any git config scope, TagRelease now creates an annotated signed tag by delegating to the git CLI, which handles key lookup and passphrase prompts.
outofcoffee
changed the title
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
2 participants
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.
Adds support for GPG/SSH-signed annotated tags when the repository has tag signing enabled in git config.
Summary
TagRelease()now checks for tag signing configuration before creating a tagisTagSigningEnabled()checkstag.gpgSignandtag.forceSignAnnotatedacross all git config scopescreateSignedTag()delegates togit tag -srather than go-git, enabling proper GPG/SSH key lookup and passphrase promptingImplementation details
Signed tag creation deliberately bypasses the go-git library and shells out to
git tag -s. go-git does not support GPG or SSH signing, so delegating to the CLI is the only way to correctly handle key resolution and interactive passphrase entry. Error handling distinguishes between an unset config key (exit code 1, silently skipped) and a real config read failure.