security: bump anyhow to 1.0.103 (RUSTSEC-2026-0190) - #158
Merged
Conversation
anyhow 1.0.102 has an unsoundness in Error::downcast_mut() (borrow-rule violation -> UB when downcast_mut is called on an error that had context added). RUSTSEC-2026-0190; fixed in 1.0.103. Lockfile-only patch bump; clears the required cargo-deny-advisories gate (verified: 'advisories ok').
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.
What
Lockfile-only patch bump:
anyhow 1.0.102 -> 1.0.103.Why
anyhow 1.0.102has an unsoundness — RUSTSEC-2026-0190:Error::downcast_mut()violates borrow rules (UB) when called on an error that had context added via.context(). Fixed in 1.0.103.This is failing the required
cargo-deny-advisoriescheck on every open PR and onmain, so nothing can merge until it lands. Surfaced the moment build/test/clippy + advisories became enforced (#123).Verification
cargo update -p anyhow→ 1.0.103 (no API change; patch within 1.0.x)cargo deny check advisories→advisories ok(exit 0)Cargo.tomlchange;Cargo.lockonly.