Repository navigation
Verify CLI installs against committed checksums - #73
Merged
Merged
Conversation
Contributor
axelniklasson
approved these changes
Oct 5, 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.
Pins the SHA-256 checksums of each CLI release in
cli-checksums.txt, so installs of a listed version skip the GitHub API entirely: directreleases/downloadURL, verified against the committed hash. No token, no rate limit, nojq. This removes the anonymous-rate-limit risk #72 leaves on GitHub Enterprise runners.install.shcheckscli-checksums.txtfirst;latest, legacy, and unlisted versions keep their current paths.release.shasserts the CLI release is immutable and appends its checksums before creating the release branch. Backfilled v0.17.0 through v0.18.0.checksums.txt.Immutability is now checked once at release time instead of on every install. A committed hash can't go stale on an immutable release, and a mismatch fails closed.
Towards LIN-87430