Skip to content

fix(deps): bump anyhow → 1.0.103 (RUSTSEC-2026-0190) - #54

Merged
montfort merged 1 commit into
mainfrom
fix/rustsec-2026-0190-anyhow
Jul 3, 2026
Merged

fix(deps): bump anyhow → 1.0.103 (RUSTSEC-2026-0190)#54
montfort merged 1 commit into
mainfrom
fix/rustsec-2026-0190-anyhow

Conversation

@montfort

@montfort montfort commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Why

cargo-deny started failing the engine CI on every open PR (#52, #53, …) after RustSec published RUSTSEC-2026-0190 — an unsound advisory against anyhow: Error::downcast_mut() on an error carrying Error::context() violates borrow rules → undefined behavior (dtolnay/anyhow#451). This is environmental (advisory DB updated), not caused by any PR's diff.

Fix

Patch bump to the first non-affected release, as RustSec recommends (>=1.0.103). Engine workspace Cargo.lock only — that's the lockfile the cargo-deny job gates. Semver-compatible, no API changes; cargo deny check advisoriesok locally.

Merge order

Merge this first, then rebase/update #52 and #53 so their CI goes green.

Note: lnxdrive-gnome/Cargo.lock still carries anyhow 1.0.102 (also affected) but is not CI-gated and its crate isn't built into the Flatpak bundle. Tracked as a low-priority follow-up rather than dragging the git-dep pin into this minimal advisory fix.

🤖 Generated with Claude Code

RUSTSEC-2026-0190 (unsound): `Error::downcast_mut()` on an error that had
context added via `Error::context()` violates borrow rules → UB. Newly
published advisory; cargo-deny's advisory DB updated and now fails the
engine CI on every open PR (unrelated to those PRs' changes).

Fixed the RustSec-recommended way — patch bump to the first non-affected
release (>=1.0.103). Engine workspace only (the CI-gated lockfile);
semver-compatible, no API changes. `cargo deny check advisories` → ok.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@montfort
montfort merged commit 2aa1b74 into main Jul 3, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant