Update Rust crate anyhow to v1.0.100

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
anyhow	dependencies	patch	1.0.41 -> 1.0.100

---

Release Notes

dtolnay/anyhow (anyhow)

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

v1.0.58

Compare Source

• Fix some broken links in documentation

v1.0.57

Compare Source

• Remove a log4rs-specific workaround from bail! macro implementation

v1.0.56

Compare Source

• Add must_use warning when an Error created by anyhow! is not used, perhaps because the programmer meant to write bail! instead (#​229)

v1.0.55

Compare Source

• Documentation improvements

v1.0.54

Compare Source

• Construct more helpful error message from ensure! when the expression involves a negative literal const generic as the first generic argument of a method call (#​224)

v1.0.53

Compare Source

• Retrigger docs.rs build to work around rustdoc regression (rust-lang/rust#92331)

v1.0.52

Compare Source

• Reduce overhead of backtrace capture in the case that backtraces are not enabled (#​212)

v1.0.51

Compare Source

• Show doc for Ok fn

v1.0.50

Compare Source

• Recognize more types of expressions in ensure! macro (#​199, #​200, #​202, #​203, #​204, #​205, #​206)

v1.0.49

Compare Source

• Add a function anyhow::Ok(v) equivalent to Ok::<_, anyhow::Error>(v) (#​192)

v1.0.48

Compare Source

• Include a Debug rendering of lhs and rhs in ensure! messages (#​193, #​194, #​195, #​196, #​197, #​198)

Example:

```rust
ensure!(flags.len() <= 40);
```

```rust
ensure!(kind == Kind::File);
```

Before:

```console
Condition failed: `flags.len() <= 40`
Condition failed: `kind == Kind::File`
```

After:

```console
Condition failed: `flags.len() <= 40` (99 vs 40)
Condition failed: `kind == Kind::File` (Symlink vs File)
```

v1.0.47

Compare Source

• Fixes for implicit format args support

v1.0.46

Compare Source

• Support for implicit format args to match println and other std macros (https://rust-lang.github.io/rfcs/2795-format-args-implicit-identifiers.html)

  let var = ...;
  let error = anyhow!("interpolate {var}");  // equivalent to anyhow!("interpolate {var}", var=var)

• Detect missing fmt arguments at compile time: anyhow!("{} not found") (#​55)

• Reduce occurrence of "future cannot be shared between threads safely" in async code using anyhow macros (#​186)

v1.0.45

Compare Source

• Fix non-compilable macro expansion if downstream crate calls anyhow!, ensure!, or bail! with format args and is built with #![no_std] or #![no_implicit_prelude] (#​177)

v1.0.44

Compare Source

• Mark error constructors cold to help LLVM optimize code paths not leading to error (#​166, thanks @​stepancheg)

v1.0.43

Compare Source

• Take -Zallow-features restrictions from Cargo configuration file into account on sufficiently new versions of nightly Cargo (#​157, thanks @​jonhoo)

v1.0.42

Compare Source

• Enable Android's automated tooling to pull in test coverage improvements

---

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 an artifact 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: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path experimental/udev-device-manager/Cargo.toml --workspace
error: current package believes it's in a workspace when it's not:
current:   /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/experimental/udev-device-manager/Cargo.toml
workspace: /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/Cargo.toml

this may be fixable by adding `experimental/udev-device-manager` to the `workspace.members` array of the manifest located at: /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact 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: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path experimental/udev-device-manager/Cargo.toml --package [email protected] --precise 1.0.100
error: current package believes it's in a workspace when it's not:
current:   /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/experimental/udev-device-manager/Cargo.toml
workspace: /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/Cargo.toml

this may be fixable by adding `experimental/udev-device-manager` to the `workspace.members` array of the manifest located at: /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.