chore(deps): bump sha2 from 0.10.9 to 0.11.0 - #8
Merged
Conversation
dependabot
Bot
added
dependencies
MotherSphere
added a commit
that referenced
this pull request
Aug 25, 2026
Dependabot #8 bumps sha2 0.10.9 to 0.11.0 and does not compile. 0.11 drops `io::Write` on the hashers and returns an `Array` that no longer implements `LowerHex`, so `std::io::copy(&mut f, &mut hasher)` and `format!("{:x}", …)` both stop working — the two idioms every call site here used. Reading in a loop and hex-encoding by hand compiles against 0.10 and 0.11 alike, so the bump becomes a version bump again rather than a migration hiding inside one. Three sites, not two. The CI build only showed cfc-cli/rules.rs and cfc-daemon/process_resolve.rs; provenance.rs:1848 is `#[cfg(test)]` and only appears under --all-targets. Merging #8 on the strength of a green `build` job would have left the test suite uncompilable. This is the code behind `--pin-hash`, which binds a rule to a binary's contents rather than its path. A digest that changed would not fail loudly — the rule would simply stop matching, and a firewall would quietly stop enforcing something someone asked it to enforce. So it was checked rather than assumed: cargo check clean under both 0.10 and 0.11, and the suite green under 0.10 including sha256_of_known_content, which asserts a fixed digest.
Member
|
@dependabot rebase |
dependabot
Bot
force-pushed
the
dependabot/cargo/sha2-0.11.0
branch
from
August 25, 2026 14:10
6b8b0fc to
315350c
Compare
Member
|
@dependabot rebase |
Bumps [sha2](https://github.com/RustCrypto/hashes) from 0.10.9 to 0.11.0. - [Commits](RustCrypto/hashes@sha2-v0.10.9...sha2-v0.11.0) --- updated-dependencies: - dependency-name: sha2 dependency-version: 0.11.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/sha2-0.11.0
branch
from
August 25, 2026 14:43
315350c to
2ca8a8e
Compare
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
1 participant
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.
Bumps sha2 from 0.10.9 to 0.11.0.
Commits
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...ed514f2Use published version ofkeccakv0.2 (#799)702bcd8Migrate to closure-basedkeccak(#796)827c043sha3 v0.11.0-rc.8 (#794)