We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Something a number of packages do is have a .sha256 (and/or others) alongside the file in the releases:
.sha256
https://github.com/mozilla/sccache/releases/download/v0.3.0/sccache-dist-v0.3.0-x86_64-unknown-linux-musl.tar.gz https://github.com/mozilla/sccache/releases/download/v0.3.0/sccache-dist-v0.3.0-x86_64-unknown-linux-musl.tar.gz.sha256
https://github.com/orhun/git-cliff/releases/download/v0.9.2/git-cliff-0.9.2-x86_64-apple-darwin.tar.gz https://github.com/orhun/git-cliff/releases/download/v0.9.2/git-cliff-0.9.2-x86_64-apple-darwin.tar.gz.sha512
Once we have checksum-checking support, we should auto-discover those for common hash algorithms (sha256, sha512, b2, b3).
sha256
sha512
b2
b3
The text was updated successfully, but these errors were encountered:
Also the format of these is a text file containing either:
shaNsum
Sorry, something went wrong.
Also the format of these is a text file containing the hash in hex and nothing else.
git-cliff also contains the filename of the archive, which I think is generated by sha512 command. We can simply trim that though.
No branches or pull requests
Something a number of packages do is have a
.sha256
(and/or others) alongside the file in the releases:Once we have checksum-checking support, we should auto-discover those for common hash algorithms (
sha256
,sha512
,b2
,b3
).The text was updated successfully, but these errors were encountered: