Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump thiserror from 1.0.66 to 2.0.3 #497

Merged
merged 2 commits into from
Dec 1, 2024
Merged

build(deps): bump thiserror from 1.0.66 to 2.0.3 #497

merged 2 commits into from
Dec 1, 2024

Commits on Dec 1, 2024

  1. build(deps): bump thiserror from 1.0.66 to 2.0.3 

    Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.66 to 2.0.3.
- [Release notes](https://github.com/dtolnay/thiserror/releases)
- [Commits](dtolnay/thiserror@1.0.66...2.0.3)

---
updated-dependencies:
- dependency-name: thiserror
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
    @dependabot
    dependabot[bot] authored Dec 1, 2024
    Configuration menu
    Copy the full SHA
    20f9b24 View commit details
    Browse the repository at this point in the history

  2. fix(src/error.rs): breaking change after 2.x bump 

    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](https://redirect.github.com/dtolnay/thiserror/issues/354)

```rust #[derive(Error, Debug)]
//                  ^^^ Not allowed, use #[error("... {0} {n}", n = $N)]
pub struct TupleError(i32);
```
    @andros21
    andros21 committed Dec 1, 2024
    Configuration menu
    Copy the full SHA
    3c96ad8 View commit details
    Browse the repository at this point in the history