Repository navigation
docs: say how to check a downloaded release - #218
Merged
Merged
Conversation
ingvarch
enabled auto-merge (rebase)
November 9, 2026 22:33
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.
What changes
Every release has a checksums file, and the install guide did not say how to use it.
docs/install.mdgets a section "Check a download": the commands for Linux, macOS and Windows, what the check shows, and how to see that the macOS binary is signed and notarized.spctl --assess --type execute -v ./urga. For a bare command-line binary it printsrejected (the code is valid but does not seem to be an app), so the guide usesspctl --assess --type open --context context:primary-signature -v ./urga, which printsacceptedandsource=Notarized Developer ID.Run against the v0.18.1 release (darwin_arm64, linux_amd64 and windows_amd64 archives with the checksums file), as written in the guide:
shasum -a 256 --check --ignore-missing urga_*_checksums.txt:OKfor each of the three; with one byte added to an archive it printsFAILEDand exits 1.sha256sum --check --ignore-missing urga_*_checksums.txt:OKfor each, with thesha256sumof macOS. The GNU coreutils one of Linux was not run here; it has--ignore-missingsince coreutils 8.25.spctl ... ./urgain the unpacked darwin_arm64 archive:./urga: accepted,source=Notarized Developer ID.Issues
Closes #202
Checklist
make checkis greendocs/is updated if users see a differencefeat(ui): ...,fix(nomad): ...