chore(deps): bump thiserror from 1.0.69 to 2.0.17#22
Merged
Conversation
dependabot
Bot
added
dependencies
Owner
|
@dependabot rebase |
Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.69 to 2.0.17. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](dtolnay/thiserror@1.0.69...2.0.17) --- updated-dependencies: - dependency-name: thiserror dependency-version: 2.0.17 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/thiserror-2.0.17
branch
from
967c441 to
6794d3c
Compare
hyperpolymath
added a commit
that referenced
this pull request
May 14, 2026
## Why `cargo fmt --check` is failing in the `test` job of `rust-ci.yml`, which blocks every Dependabot PR. RUSTFLAGS=-Dwarnings + fmt-check-strict means the workflow rejects any unformatted code. ## What Replays the exact rustfmt output captured from the failing CI log on PR #22. Five reformats: - `src/lib.rs:77` — `ImagePair::new()` signature wrapped - `src/lib.rs:138` — `partition_pairs()` signature + return tuple wrapped - `tests/smoke_test.rs:75` — `assert_eq!()` wrapped - `tests/smoke_test.rs:213` — `matches!()` wrapped - `tests/smoke_test.rs:236` — `.map(|i| ImagePair::new(...))` wrapped to multi-line block No semantic changes; only whitespace. ## Verify The test job's `cargo fmt --check` step should now pass. If rustfmt picks up any additional whitespace differences I missed, CI will tell us and we iterate. --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps thiserror from 1.0.69 to 2.0.17.
Release notes
Sourced from thiserror's releases.
... (truncated)
Commits
72ae716Release 2.0.17599fdceMerge pull request #434 from dtolnay/private9ec05f6Use differently named __private module per patch released2c492bRaise minimum tested compiler to rust 1.76fc3ab95Opt in to generate-macro-expansion when building on docs.rs819fe29Update ui test suite to nightly-2025-09-12259f48cEnforce trybuild >= 1.0.108470e6a6Update ui test suite to nightly-2025-08-24544e191Update actions/checkout@v4 -> v5cbc1ebaDelete duplicate cap-lints flag from build script