Skip to content

build(deps): bump anyhow to 1.0.103 for RUSTSEC-2026-0190 - #10849

Merged
gustavovalverde merged 2 commits into
mainfrom
bump-anyhow
Jul 1, 2026
Merged

build(deps): bump anyhow to 1.0.103 for RUSTSEC-2026-0190#10849
gustavovalverde merged 2 commits into
mainfrom
bump-anyhow

Conversation

@upbqdn

@upbqdn upbqdn commented Jun 29, 2026

Copy link
Copy Markdown
Member

Motivation

Closes #10848

Solution

Bump anyhow 1.0.102 -> 1.0.103 in the lockfile to patch RUSTSEC-2026-0190 (unsoundness in Error::downcast_mut()). Lockfile-only; the workspace requirement stays 1.0.

AI Disclosure

  • AI tools were used: Claude for the bump and PR text.

Patches an unsoundness in `anyhow::Error::downcast_mut()` (affects
< 1.0.103). Lockfile-only; the workspace requirement stays `1.0`.

Claude-Session: https://claude.ai/code/session_01VUPwpe81Ws8c5MeXWWgZb7
Copilot AI review requested due to automatic review settings June 29, 2026 15:24
@upbqdn upbqdn self-assigned this Jun 29, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

Carry the `safe-to-deploy` exemption forward to the bumped version so
`cargo vet check` passes; otherwise 1.0.103 is unaudited.

Claude-Session: https://claude.ai/code/session_01VUPwpe81Ws8c5MeXWWgZb7
@mergify mergify Bot added the queued label Jun 30, 2026
@mergify

mergify Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • Entered queue2026-06-30 10:12 UTC · Rule: batched · triggered by rule move to any queue if GitHub Rulesets are satisfied
  • Checks failed · on draft merge queue: checking main (aae2059) and #10849 together #10858
  • 🚫 Left the queue2026-06-30 10:29 UTC · at 45467bed5ca09eb4bba83bc598fbc41ad2c2d16b

This pull request spent 17 minutes 17 seconds in the queue, including 5 minutes 19 seconds running CI.

Waiting for
  • any of: [🛡 GitHub repository ruleset rule PR Requirements]
    • check-neutral = @github-actions/lint
    • check-skipped = @github-actions/lint
    • check-success = @github-actions/lint
  • any of: [🛡 GitHub repository ruleset rule PR Requirements]
    • check-neutral = test-crates
    • check-skipped = test-crates
    • check-success = test-crates
  • any of: [🛡 GitHub repository ruleset rule PR Requirements]
    • check-neutral = unit-tests
    • check-skipped = unit-tests
    • check-success = unit-tests
All conditions

Reason

The merge conditions cannot be satisfied due to failing checks

  • @github-actions/lint

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

  • Requeue this pull request

mergify Bot added a commit that referenced this pull request Jun 30, 2026
mergify Bot added a commit that referenced this pull request Jun 30, 2026
@mergify mergify Bot added dequeued and removed queued labels Jun 30, 2026
@gustavovalverde

Copy link
Copy Markdown
Member

admin-merging because of flaky tests

@gustavovalverde
gustavovalverde merged commit 8d90981 into main Jul 1, 2026
195 of 199 checks passed
@gustavovalverde
gustavovalverde deleted the bump-anyhow branch July 1, 2026 10:04
@gustavovalverde gustavovalverde linked an issue Jul 6, 2026 that may be closed by this pull request
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

deny advisories: RUSTSEC-2026-0190 (anyhow unsoundness) task: investigate and catalogue flaky tests across the suite

5 participants