Repository navigation
Add checksum verification to CLI installation and upgrades - #370
Merged
AmoebaProtozoa merged 3 commits intoOct 15, 2026
Merged
Conversation
|
|
baiyuqing
approved these changes
Oct 15, 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.
Add SHA-256 verification to CLI installation and upgrade downloads. Upgrades resolve a concrete release version, then download
install.shandchecksums.txtfrom that release. The installer is verified before execution, and the release archive is verified before extraction.The release build stamps the installer with the release version, publishes it as a release asset, and includes its SHA-256 in the generated checksum manifest. This keeps installer versions and checksums in the release pipeline without embedding a revision or checksum in the CLI.
Both upgrade modes share the same verification flow. Version lookup, download, and checksum failures stop the upgrade. Custom mirrors remain supported over HTTPS, with checksum manifests fetched from the official GitHub release.
The new upgrade flow requires the installer asset and checksum entry, which will be published automatically starting with the next release.
Validation:
go test -race -cover -count=1 ./...golangci-lint v1.64.7 run ./...with Go 1.24.0install.sh