fix(deps): update rust crate thiserror to v2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
thiserror	dependencies	major	1.0.37 -> 2.0.0

---

Release Notes

dtolnay/thiserror (thiserror)

v2.0.3

Compare Source

• Support the same Path field being repeated in both Debug and Display representation in error message (#​383)
• Improve error message when a format trait used in error message is not implemented by some field (#​384)

v2.0.2

Compare Source

• Fix hang on invalid input inside #[error(...)] attribute (#​382)

v2.0.1

Compare Source

• Support errors that contain a dynamically sized final field (#​375)
• Improve inference of trait bounds for fields that are interpolated multiple times in an error message (#​377)

v2.0.0

Compare Source

Breaking changes

• Referencing keyword-named fields by a raw identifier like {r#type} inside a format string is no longer accepted; simply use the unraw name like {type} (#​347)

  This aligns thiserror with the standard library's formatting macros, which gained support for implicit argument capture later than the release of this feature in thiserror 1.x.

  #[derive(Error, Debug)]
  #[error("... {type} ...")]  // Before: {r#type}
  pub struct Error {
      pub r#type: Type,
  }

• Trait bounds are no longer inferred on fields whose value is shadowed by an explicit named argument in a format message (#​345)

  // Before: impl<T: Octal> Display for Error<T>
  // After: impl<T> Display for Error<T>
  #[derive(Error, Debug)]
  #[error("{thing:o}", thing = "...")]
  pub struct Error<T> {
      thing: T,
  }

• Tuple structs and tuple variants can no longer use numerical {0} {1} access at the same time as supplying extra positional arguments for a format message, as this makes it ambiguous whether the number refers to a tuple field vs a different positional arg (#​354)

  #[derive(Error, Debug)]
  #[error("ambiguous: {0} {}", $N)]
  //                  ^^^ Not allowed, use #[error("... {0} {n}", n = $N)]
  pub struct TupleError(i32);

• Code containing invocations of thiserror's derive(Error) must now have a direct dependency on the thiserror crate regardless of the error data structure's contents (#​368, #​369, #​370, #​372)

Features

• Support disabling thiserror's standard library dependency by disabling the default "std" Cargo feature: thiserror = { version = "2", default-features = false } (#​373)

• Support using r#source as field name to opt out of a field named "source" being treated as an error's Error::source() (#​350)

  #[derive(Error, Debug)]
  #[error("{source} ==> {destination}")]
  pub struct Error {
      r#source: char,
      destination: char,
  }
  
  let error = Error { source: 'S', destination: 'D' };

• Infinite recursion in a generated Display impl now produces an unconditional_recursion warning (#​359)

  #[derive(Error, Debug)]
  #[error("??? {self}")]
  pub struct Error;

• A new attribute #[error(fmt = path::to::myfmt)] can be used to write formatting logic for an enum variant out-of-line (#​367)

  #[derive(Error, Debug)]
  pub enum Error {
      #[error(fmt = demo_fmt)]
      Demo { code: u16, message: Option<String> },
  }
  
  fn demo_fmt(code: &u16, message: &Option<String>, formatter: &mut fmt::Formatter) -> fmt::Result {
      write!(formatter, "{code}")?;
      if let Some(msg) = message {
          write!(formatter, " - {msg}")?;
      }
      Ok(())
  }

• Enums with an enum-level format message are now able to have individual variants that are transparent to supersede the enum-level message (#​366)

  #[derive(Error, Debug)]
  #[error("my error {0}")]
  pub enum Error {
      Json(#[from] serde_json::Error),
      Yaml(#[from] serde_yaml::Error),
      #[error(transparent)]
      Other(#[from] anyhow::Error),
  }

v1.0.69

Compare Source

• Backport 2.0.2 fixes

v1.0.68

Compare Source

• Handle incomplete expressions more robustly in format arguments, such as while code is being typed (#​341, #​344)

v1.0.67

Compare Source

• Improve expression syntax support inside format arguments (#​335, #​337, #​339, #​340)

v1.0.66

Compare Source

• Improve compile error on malformed format attribute (#​327)

v1.0.65

Compare Source

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

v1.0.64

Compare Source

• Exclude derived impls from coverage instrumentation (#​322, thanks @​oxalica)

v1.0.63

Compare Source

• Documentation improvements

v1.0.62

Compare Source

• Support referring to nested tuple struct fields inside #[error("…", …)] attribute (#​309)

v1.0.61

Compare Source

• Use core::fmt and core::panic to facilitate error_in_core support (#​299, thanks @​jordens)

v1.0.60

Compare Source

• Resolve unexpected_cfgs warning (#​298)

v1.0.59

Compare Source

• Unblock testing of rustc debug-fmt-detail option (#​297)

v1.0.58

Compare Source

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

v1.0.57

Compare Source

• Generate more efficient Display impl for error message which do not contain any interpolated value (#​286, thanks @​nyurik)

v1.0.56

Compare Source

• Update proc-macro2 to fix caching issue when using a rustc-wrapper such as sccache

v1.0.55

Compare Source

• Work around improperly cached build script result by sccache – second attempt (#​280)

v1.0.54

Compare Source

• Work around improperly cached build script result by sccache – first attempt (#​279)

v1.0.53

Compare Source

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

v1.0.52

Compare Source

• Fix interaction with RUSTC_BOOTSTRAP (#​269)

v1.0.51

Compare Source

• Improve diagnostics when an invalid attribute previously caused thiserror to generate no Error impl (#​266)

v1.0.50

Compare Source

• Improve diagnostic when a #[source], #[from], or #[transparant] attribute refers to a type that has no std::error::Error impl (#​258, thanks @​de-vri-es)

v1.0.49

Compare Source

• Access libcore types through ::core in generated code (#​255, thanks @​mina86)

v1.0.48

Compare Source

• Improve implementation of displaying Path values in a generated Display impl (#​251, thanks @​mina86)

v1.0.47

Compare Source

• Work around rust-analyzer bug (https://github.com/rust-lang/rust-analyzer/issues/9911)

v1.0.46

Compare Source

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

v1.0.45

Compare Source

• Update backtrace support to nightly's new Error::provide API (https://github.com/rust-lang/rust/pull/113464, #​246)

v1.0.44

Compare Source

• Documentation improvements

v1.0.43

Compare Source

v1.0.42

Compare Source

• Fix compile error in derived Display impl if there was a nonstandard write! macro in scope (#​239)

v1.0.41

Compare Source

v1.0.40

Compare Source

• Update syn dependency to 2.x

v1.0.39

Compare Source

• Set html_root_url attribute

v1.0.38

Compare Source

• Documentation 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 Cargo.toml --package [email protected] --precise 2.0.0
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]