feat(release): publish checksums.txt and verify downloads in the installer#68
Merged
Merged
Conversation
…aller The build now writes a sha256sum-compatible checksums.txt next to the release archives and uploads it with them. The install script fetches it and verifies the downloaded archive before extraction, failing with the expected/actual digests on mismatch. Releases published before checksums.txt skip verification, as do systems with no sha256 tool.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Fixes #50.
The build step now computes sha256 digests for every release archive as it creates them and uploads a
checksums.txt(sha256sum format) with the release assets. The install script downloads it from the same release directory as the archive and verifies before extraction:Verified with a sandboxed
HOME, cleanPATH, pinned--version 1.2.3install: full download runs, verification skips gracefully (that release has no checksums file), binary lands and reports its version. The checksum-parsing awk was exercised against a synthetic manifest. Both install-script copies stay in sync (diff -qin CI keeps it that way after #66).