Repository navigation
Retain v0.1.7 verification files and update SIGNING.md - #11
Merged
Merged
Conversation
Add the public verification artifacts for v0.1.7 (signing key, checksum manifest and the two detached signatures) under release-signatures/v0.1.7/, matching earlier releases, and update SIGNING.md to the v0.1.7 release URL and zero-breach.py SHA-256.
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.
Keeps the repository verification record in step with the published v0.1.7 release.
release-signatures/v0.1.7/: signing key,SHA256SUMS.txt, and the two detached signatures, copied from the release. Manifest signature verifies; the key is byte-identical to v0.1.6.SIGNING.md: release URL and expectedzero-breach.pySHA-256 updated to v0.1.7.No code changes.