Skip to content
This repository was archived by the owner on Oct 27, 2025. It is now read-only.

chore(deps): update rust crate thiserror to v2#233

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/thiserror-2.x
Open

chore(deps): update rust crate thiserror to v2#233
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/thiserror-2.x

Conversation

@renovate

@renovate renovate Bot commented Nov 7, 2024

Copy link
Copy Markdown
Contributor

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

Compare Source

  • Use differently named __private module per patch release (#​434)

v2.0.16

Compare Source

  • Add to "no-std" crates.io category (#​429)

v2.0.15

Compare Source

  • Prevent Error::provide API becoming unavailable from a future new compiler lint (#​427)

v2.0.14

Compare Source

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

v2.0.13

Compare Source

  • Documentation improvements

v2.0.12

Compare Source

  • Prevent elidable_lifetime_names pedantic clippy lint in generated impl (#​413)

v2.0.11

Compare Source

v2.0.10

Compare Source

  • Support errors containing a generic type parameter's associated type in a field (#​408)

v2.0.9

Compare Source

  • Work around missing_inline_in_public_items clippy restriction being triggered in macro-generated code (#​404)

v2.0.8

Compare Source

  • Improve support for macro-generated derive(Error) call sites (#​399)

v2.0.7

Compare Source

  • Work around conflict with #[deny(clippy::allow_attributes)] (#​397, thanks @​zertosh)

v2.0.6

Compare Source

  • Suppress deprecation warning on generated From impls (#​396)

v2.0.5

Compare Source

  • Prevent deprecation warning on generated impl for deprecated type (#​394)

v2.0.4

Compare Source

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),
    }

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

@renovate

renovate Bot commented Nov 7, 2024

Copy link
Copy Markdown
Contributor Author

⚠️ 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.69 --precise 2.0.17
    Updating crates.io index
error: failed to select a version for the requirement `thiserror = "^1.0.24"`
candidate versions found which didn't match: 2.0.17
location searched: crates.io index
required by package `async-graphql v7.0.3`
    ... which satisfies dependency `async-graphql = "^7.0.3"` of package `graphql-example v0.1.0 (/tmp/renovate/repos/github/dbanty/rust-lambda-graphql-example)`

@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 4 times, most recently from ba08844 to 9d22300 Compare November 11, 2024 04:40
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 2 times, most recently from 2cb1897 to 9707832 Compare November 18, 2024 04:46
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 4 times, most recently from 933819f to 1ce0f35 Compare November 29, 2024 19:53
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 5 times, most recently from 0dc28f7 to 3ef1a97 Compare December 9, 2024 04:20
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 3 times, most recently from 30a873f to a7f263e Compare December 16, 2024 07:11
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 2 times, most recently from 7a9babf to e4650a6 Compare December 23, 2024 04:12
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 2 times, most recently from 0419c96 to 5c3261d Compare January 6, 2025 03:01
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 3 times, most recently from ca33a44 to 83cc776 Compare January 13, 2025 05:32
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 4 times, most recently from e965c0f to 427d778 Compare January 22, 2025 20:46
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 4 times, most recently from 45ae03d to 6043dbd Compare March 17, 2025 05:52
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch from 6043dbd to 3e221b3 Compare March 20, 2025 10:09
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 2 times, most recently from a4463eb to 0e17fce Compare April 5, 2025 22:02
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 2 times, most recently from 8e5fdad to f9da197 Compare April 14, 2025 05:35
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 3 times, most recently from 95c2665 to 12c4c31 Compare April 28, 2025 03:12
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 2 times, most recently from cd39789 to fbf42d4 Compare May 6, 2025 10:16
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch from fbf42d4 to 98f135b Compare May 12, 2025 07:43
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 5 times, most recently from 67c2d62 to 19916bb Compare May 28, 2025 14:58
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 3 times, most recently from bcd9303 to 4f35e7f Compare June 9, 2025 05:51
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 2 times, most recently from 7dca86a to 754610d Compare June 23, 2025 05:56
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch 3 times, most recently from 26668c9 to 2f613c1 Compare July 5, 2025 00:46
@renovate renovate Bot force-pushed the renovate/thiserror-2.x branch from 2f613c1 to 7a8178b Compare July 14, 2025 05:08
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants