docs(release): document signing release tags with gitsign - #250
Merged
Conversation
Resolves the deferred signed-tags item (7.1) via the documented-gitsign approach: maintainers sign release tags with keyless Sigstore (gitsign) when they create them, keeping the developer-driven push-a-tag release flow intact. Updates the generated projects' release how-to and the template repo's own release-process doc with git tag -s and the one-time gitsign config. Complements the PEP 740 artifact attestations.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Resolves the deferred signed-tags item (7.1) via the option you chose: document keyless Sigstore signing with gitsign, so maintainers sign release tags when they create them (
git tag -s), keeping the current push-a-tag release flow.Advisory (opt-in) by design; the published artifacts already carry PEP 740 attestations, so this makes the git tag itself verifiable too. Docs-only; fast suite 383 green. A v0.37.0 candidate — release + fan out whenever convenient.