chore(deps): update rust crate anyhow to v1.0.102

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
anyhow	dependencies	patch	1.0.58 → 1.0.102

---

Release Notes

dtolnay/anyhow (anyhow)

v1.0.102

Compare Source

• Remove backtrace dependency (#​438, #​439, #​440, #​441, #​442)

v1.0.101

Compare Source

• Add #[inline] to anyhow::Ok helper (#​437, thanks @​Ibitier)

v1.0.100

Compare Source

• Teach clippy to lint formatting arguments in bail!, ensure!, anyhow! (#​426)

v1.0.99

Compare Source

• Allow build-script cleanup failure with NFSv3 output directory to be non-fatal (#​420)

v1.0.98

Compare Source

• Add self.into_boxed_dyn_error() and self.reallocate_into_boxed_dyn_error_without_backtrace() methods for anyhow::Error (#​415)

v1.0.97

Compare Source

• Documentation improvements

v1.0.96

Compare Source

• Documentation improvements

v1.0.95

Compare Source

• Add Error::from_boxed (#​401, #​402)

v1.0.94

Compare Source

• Documentation improvements

v1.0.93

Compare Source

• Update dev-dependencies to thiserror v2

v1.0.92

Compare Source

• Support Rust 1.82's &raw const and &raw mut syntax inside ensure! (#​390)

v1.0.91

Compare Source

• Ensure OUT_DIR is left with deterministic contents after build script execution (#​388)

v1.0.90

Compare Source

• Documentation improvements

v1.0.89

Compare Source

• Make anyhow::Error's UnwindSafe and RefUnwindSafe impl consistently available between versions of Rust newer and older than 1.72 (#​386)

v1.0.88

Compare Source

• Documentation improvements

v1.0.87

Compare Source

• Support more APIs, including Error::new and Error::chain, in no-std mode on Rust 1.81+ (#​383)

v1.0.86

Compare Source

• Fix parse error in ensure! with non-literal after minus sign (#​373)

v1.0.85

Compare Source

• Improve ensure! macro's rules to unblock some rustc pretty-printer improvements (#​368, #​371)

v1.0.84

Compare Source

• Disallow calling ensure! through a Not impl for a type that is not bool (#​367)

v1.0.83

Compare Source

• Integrate compile-time checking of cfgs (#​363)

v1.0.82

Compare Source

• Documentation improvements

v1.0.81

Compare Source

• Make backtrace support available when using -Dwarnings (#​354)

v1.0.80

Compare Source

• Fix unused_imports warnings when compiled by rustc 1.78

v1.0.79

Compare Source

• Work around improperly cached build script result by sccache (#​340)

v1.0.78

Compare Source

• Reduce spurious rebuilds under RustRover IDE when using a nightly toolchain (#​337)

v1.0.77

Compare Source

• Make anyhow::Error::backtrace available on stable Rust compilers 1.65+ (#​293, thanks @​LukasKalbertodt)

v1.0.76

Compare Source

• Opt in to unsafe_op_in_unsafe_fn lint (#​329)

v1.0.75

Compare Source

• Partially work around rust-analyzer bug (rust-lang/rust-analyzer#9911)

v1.0.74

Compare Source

• Add bootstrap workaround to allow rustc to depend on anyhow (#​320, thanks @​RalfJung)

v1.0.73

Compare Source

• Update backtrace support to nightly's new Error::provide API (rust-lang/rust#113464, #​319)

v1.0.72

Compare Source

• Documentation improvements

v1.0.71

Compare Source

• Documentation improvements

v1.0.70

Compare Source

• Update syn dependency to 2.x

v1.0.69

Compare Source

• Documentation improvements

v1.0.68

Compare Source

• Opt out of -Zrustdoc-scrape-examples on docs.rs for now

v1.0.67

Compare Source

• Improve the backtrace captured when context() is used on an Option (#​280)

v1.0.66

Compare Source

• Reduce unhelpful backtrace frames in backtraces captured during a context call (#​279)

v1.0.65

Compare Source

• impl Provider for anyhow::Error

v1.0.64

Compare Source

• Correctly propagate Backtrace when using #[source] anyhow::Error with thiserror crate (#​231)

v1.0.63

Compare Source

• Expose backtraces via the new "generic member access" API on the Error trait (rust-lang/rust#99301, rust-lang/rust#96024)

v1.0.62

Compare Source

• Fix extra rebuilding when interleaving command-line cargo invocations with IDE builds (#​261)

v1.0.61

Compare Source

• Work around rust-analyzer builds poisoning all subsequent command-line cargo builds (#​252)

v1.0.60

Compare Source

• Propagate --target to rustc invocation when deciding about backtrace support (#​249, thanks @​RalfJung)

v1.0.59

Compare Source

• Update crates.io metadata to include no-std category

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: mvsqlite/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path mvsqlite/Cargo.toml --package anyhow@1.0.58 --precise 1.0.83
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: package ID specification `anyhow@1.0.58` did not match any packages
Did you mean one of these?

  anyhow@1.0.83

File name: mvfs/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path mvfs/Cargo.toml --package anyhow@1.0.58 --precise 1.0.83
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: package ID specification `anyhow@1.0.58` did not match any packages
Did you mean one of these?

  anyhow@1.0.83

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: mvfs/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path mvfs/Cargo.toml --package anyhow@1.0.58 --precise 1.0.102
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
  |
  = note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
  = note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
  = note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: package ID specification `anyhow@1.0.58` did not match any packages
help: there are similar package ID specifications:

  anyhow@1.0.102

File name: mvsqlite/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path mvsqlite/Cargo.toml --package anyhow@1.0.58 --precise 1.0.102
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
  |
  = note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
  = note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
  = note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
error: package ID specification `anyhow@1.0.58` did not match any packages
help: there are similar package ID specifications:

  anyhow@1.0.102