-
Notifications
You must be signed in to change notification settings - Fork 427
New issue
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
Support SHA224, SHA384 and SHA512 source hashes. #4793
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks Good!
Co-authored-by: Ken Odegard <[email protected]>
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
CodSpeed Performance ReportMerging #4793 will not alter performanceComparing Summary
|
) | ||
break |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is interesting, we were only computing the weakest one and ignoring the rest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah that's fun.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments above.
Co-authored-by: jaimergp <[email protected]>
Co-authored-by: jaimergp <[email protected]>
This is ready for another look @jaimergp! |
Thanks for taking over @beckermr |
Description
Provides support for validating source checksums via SHA224, SHA384 and SHA512, in addition to the existing MD5, SHA1 and SHA256 options. A similar request has been made for
boa
(see here).In addition, when multiple checksums are provided in the recipe, a
RuntimeError
will now be raised if any of the checksums are wrong. Previously, this error would not necessarily be raised if one of the provided checksums was valid (if this was an intentional design choice then this part can be reverted/excluded from the pull).Documentation and appropriate test-recipes have been updated to include examples of using the new checksums.
Checklist - did you ...
news
directory (using the template) for the next release's release notes?