build(deps): update rust crate anyhow to v1.0.91

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
anyhow	dependencies	patch	1.0.66 -> 1.0.91

---

Release Notes

dtolnay/anyhow (anyhow)

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 (https://github.com/rust-lang/rust-analyzer/issues/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 (https://github.com/rust-lang/rust/pull/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)

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai generate interesting stats about this repository and render them as a table.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.