build(deps): bump sha1 from 0.10.6 to 0.11.0#126
build(deps): bump sha1 from 0.10.6 to 0.11.0#126dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [sha1](https://github.com/RustCrypto/hashes) from 0.10.6 to 0.11.0. - [Commits](RustCrypto/hashes@sha1-v0.10.6...sha1-v0.11.0) --- updated-dependencies: - dependency-name: sha1 dependency-version: 0.11.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 30e06e4e99
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| tracing = "0.1.44" | ||
| tracing-subscriber = "0.3.23" | ||
| sha1 = "0.10.6" | ||
| sha1 = "0.11.0" |
There was a problem hiding this comment.
Keep SHA crates on the same digest major
Bumping sha1 to 0.11.0 pulls in digest 0.11, but this crate still uses sha2 0.10 (which is on digest 0.10), and multiple modules rely on a single Digest import from sha1 while calling sha2::Sha256 methods (for example src/hash.rs, src/utils.rs, and src/internal/pack/wrapper.rs). With mixed digest majors, those Sha256::new/update/finalize/digest calls no longer have the required trait in scope, so the crate fails to compile in all build contexts until the hash crates are kept on compatible digest versions or imports are split accordingly.
Useful? React with 👍 / 👎.
Bumps sha1 from 0.10.6 to 0.11.0.
Commits
2f00175Release sha1 v0.11.0 (#810)07d370csha1: refactor backends selection (#808)7c7cb76Fix md5 project link in README (#809)ffe0939Release sha2 0.11.0 (#806)8991b65Use the standard order of the[package]section fields (#807)3d2bc57sha2: refactor backends (#802)faa55fbsha3: bumpkeccakto v0.2 (#803)d3e6489sha3 v0.11.0-rc.9 (#801)bbf6f51sha2: tweak backend docs (#800)155dbbfsha3: add default value for theDSgeneric parameter onTurboShake128/256...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)