📝 Document Release Artifact Checksum Verification#90
Merged
Conversation
Add a "Verifying your download" step to the README install section and the pixee-shared skill so users and coding agents verify a directly-downloaded archive against the SHA256SUMS manifest published on each release before extracting the binary. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
nahsra
approved these changes
Jul 16, 2026
nahsra
approved these changes
Jul 16, 2026
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.
pixee-sharedskill so users and coding agents verify a directly-downloaded archive against theSHA256SUMSmanifest published on each release before extracting the binary.sha256sum -candshasum -a 256 -ccheck with--ignore-missing, so it works even when only one archive was downloaded./towards ISS-8092