Update Rust crate thiserror to v2 #152

Open

pierre wants to merge 1 commits from renovate/thiserror-2.x into master

pull from: renovate/thiserror-2.x

merge into: pierre:master

pierre:master

pierre:renovate/anyhow-1.x-lockfile

pierre:renovate/reqwest-0.x-lockfile

pierre:renovate/thiserror-1.x-lockfile

pierre:renovate/serde-1.x-lockfile

pierre:renovate/serde_json-1.x-lockfile

pierre:renovate/futures-0.x-lockfile

pierre:renovate/k8s-openapi-0.x

pierre:renovate/kube-0.x

pierre:renovate/schemars-0.x-lockfile

Conversation 2 Commits 1 Files Changed 1 +1 -1

pierre commented 2024-11-07 00:14:11 +00:00

Owner

Copy Link

This PR contains the following updates:

Package	Type	Update	Change
thiserror	dependencies	major	1.0.59 -> 2.0.0

---

Release Notes

dtolnay/thiserror (thiserror)

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.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)

---

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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [thiserror](https://github.com/dtolnay/thiserror) | dependencies | major | `1.0.59` -> `2.0.0` | --- ### Release Notes <details> <summary>dtolnay/thiserror (thiserror)</summary> ### [`v2.0.0`](https://github.com/dtolnay/thiserror/releases/tag/2.0.0) [Compare Source](https://github.com/dtolnay/thiserror/compare/1.0.68...2.0.0) #### 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}` ([#&#8203;347](https://github.com/dtolnay/thiserror/issues/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. ```rust #[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 ([#&#8203;345](https://github.com/dtolnay/thiserror/issues/345)) ```rust // 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 ([#&#8203;354](https://github.com/dtolnay/thiserror/issues/354)) ```rust #[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 ([#&#8203;368](https://github.com/dtolnay/thiserror/issues/368), [#&#8203;369](https://github.com/dtolnay/thiserror/issues/369), [#&#8203;370](https://github.com/dtolnay/thiserror/issues/370), [#&#8203;372](https://github.com/dtolnay/thiserror/issues/372)) #### Features - Support disabling thiserror's standard library dependency by disabling the default "std" Cargo feature: `thiserror = { version = "2", default-features = false }` ([#&#8203;373](https://github.com/dtolnay/thiserror/issues/373)) - Support using `r#source` as field name to opt out of a field named "source" being treated as an error's `Error::source()` ([#&#8203;350](https://github.com/dtolnay/thiserror/issues/350)) ```rust #[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 ([#&#8203;359](https://github.com/dtolnay/thiserror/issues/359)) ```rust #[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 ([#&#8203;367](https://github.com/dtolnay/thiserror/issues/367)) ```rust #[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 ([#&#8203;366](https://github.com/dtolnay/thiserror/issues/366)) ```rust #[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.68`](https://github.com/dtolnay/thiserror/releases/tag/1.0.68) [Compare Source](https://github.com/dtolnay/thiserror/compare/1.0.67...1.0.68) - Handle incomplete expressions more robustly in format arguments, such as while code is being typed ([#&#8203;341](https://github.com/dtolnay/thiserror/issues/341), [#&#8203;344](https://github.com/dtolnay/thiserror/issues/344)) ### [`v1.0.67`](https://github.com/dtolnay/thiserror/releases/tag/1.0.67) [Compare Source](https://github.com/dtolnay/thiserror/compare/1.0.66...1.0.67) - Improve expression syntax support inside format arguments ([#&#8203;335](https://github.com/dtolnay/thiserror/issues/335), [#&#8203;337](https://github.com/dtolnay/thiserror/issues/337), [#&#8203;339](https://github.com/dtolnay/thiserror/issues/339), [#&#8203;340](https://github.com/dtolnay/thiserror/issues/340)) ### [`v1.0.66`](https://github.com/dtolnay/thiserror/releases/tag/1.0.66) [Compare Source](https://github.com/dtolnay/thiserror/compare/1.0.65...1.0.66) - Improve compile error on malformed format attribute ([#&#8203;327](https://github.com/dtolnay/thiserror/issues/327)) ### [`v1.0.65`](https://github.com/dtolnay/thiserror/releases/tag/1.0.65) [Compare Source](https://github.com/dtolnay/thiserror/compare/1.0.64...1.0.65) - Ensure OUT_DIR is left with deterministic contents after build script execution ([#&#8203;325](https://github.com/dtolnay/thiserror/issues/325)) </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS43LjAiLCJ1cGRhdGVkSW5WZXIiOiIzOS43LjAiLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIiLCJsYWJlbHMiOltdfQ==-->

pierre added 1 commit 2024-11-07 00:14:11 +00:00

Update Rust crate thiserror to v2 cbb94bef4f

pierre commented 2024-11-07 00:14:11 +00:00

Author

Owner

Copy Link

⚠️ 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 thiserror@1.0.64 --precise 2.0.0
    Updating crates.io index
error: failed to select a version for the requirement `thiserror = "^1.0.29"`
candidate versions found which didn't match: 2.0.0
location searched: crates.io index
required by package `kube-client v0.90.0`
    ... which satisfies dependency `kube-client = "=0.90.0"` (locked to 0.90.0) of package `kube v0.90.0`
    ... which satisfies dependency `kube = "^0.90.0"` (locked to 0.90.0) of package `minio-operator v0.1.0 (/tmp/renovate/repos/gitea/pierre/MinioK8sBuckets)`

### ⚠️ 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 thiserror@1.0.64 --precise 2.0.0 Updating crates.io index error: failed to select a version for the requirement `thiserror = "^1.0.29"` candidate versions found which didn't match: 2.0.0 location searched: crates.io index required by package `kube-client v0.90.0` ... which satisfies dependency `kube-client = "=0.90.0"` (locked to 0.90.0) of package `kube v0.90.0` ... which satisfies dependency `kube = "^0.90.0"` (locked to 0.90.0) of package `minio-operator v0.1.0 (/tmp/renovate/repos/gitea/pierre/MinioK8sBuckets)` ```

pierre commented 2024-11-08 00:13:31 +00:00

Author

Owner

Copy Link

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

### Edited/Blocked Notification Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠️ **Warning**: custom changes will be lost.

Some checks failed

Hide all checks

renovate/artifacts Artifact file update failure

continuous-integration/drone/push Build is passing

Details

continuous-integration/drone/pr Build is passing

Details

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/thiserror-2.x:renovate/thiserror-2.x

git checkout renovate/thiserror-2.x

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No Label

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

1 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: pierre/MinioK8sBuckets#152

No description provided.