Repository navigation
Exclude tag signature from release notes - #3
Merged
Merged
Conversation
%(contents) includes the signature of signed tags, so the SSH signature block ended up in the GitHub release notes. Use the subject and body only, which leave the signature out. 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.
The release workflow reads release notes with
git tag -l --format='%(contents)'. For signed tags that output includes the signature, so the-----BEGIN SSH SIGNATURE-----block would be published in the GitHub release notes. The previousgh release create --notes-from-tagleft it out.This switches to
%(contents:subject)%0a%0a%(contents:body), which excludes the signature.Checked locally against
v0.3.0: the old format prints the signature block, and the new one prints only the tag message.