chore(deps): bump thiserror from 1.0.69 to 2.0.19 - #74
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
dependabot
Bot
added
dependencies
Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.69 to 2.0.19. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](dtolnay/thiserror@1.0.69...2.0.19) --- updated-dependencies: - dependency-name: thiserror dependency-version: 2.0.19 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.19
branch
from
August 1, 2026 20:42
f9c1a89 to
fb2ebd0
Compare
blackaxgit
added a commit
that referenced
this pull request
Aug 1, 2026
…ity-framework 3.x (#78) ## Summary Consolidates 8 Dependabot bumps that **mutually conflict on `Cargo.lock`** if merged separately, and migrates the one real breaking change. **Supersedes #69, #70, #71, #72, #73, #74, #75, #76.** Bumps: indicatif 0.17→0.18.6 · thiserror 1.0→2.0.19 · dirs 5→6.0 · colored 2→3.1.1 · shlex 1.3→2.0.1 · crossterm 0.28→0.29 · core-foundation 0.9→0.10.1 · security-framework 2.11→3.7.0. ## Breaking-change migration core-foundation 0.10 reorganized `TCFType`, removing the `as_CFTypeRef().cast_mut()` path used by the macOS keychain-ACL FFI. Now uses the typed `as_concrete_TypeRef().cast()` (`SecKeychainItemRef` → `*mut c_void`). This also aligns the direct `security-framework` dep with keyring 3.x (single dependency tree, no duplicate). The other seven bumps needed no code changes. ## Division of labor Implemented by **Cursor** (the coding worker, via agent-hub); **Claude validated** — caught and fixed one `E0308` type-mismatch (`--all-features`-gated FFI path) that Cursor's build (default features) hadn't surfaced. ## Verification - `cargo build --workspace` ✅ - `cargo clippy --workspace --all-targets --all-features -- -D warnings` ✅ - `cargo test --workspace` ✅ (no failures) - `cargo fmt --all -- --check` ✅ - gitleaks pre-push gate: clean Co-authored-by: blackax <blackaxgit@users.noreply.github.com>
Contributor
Author
|
Looks like thiserror is up-to-date now, so this is no longer needed. |
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
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.19.
Release notes
Sourced from thiserror's releases.
... (truncated)
Commits
e13a785Release 2.0.190a0e76cUpdate to syn 3ec42ea7Update actions/upload-artifact@v6 -> v74178c4aUpdate actions/checkout@v6 -> v77214e0eIgnore items_after_statements pedantic clippy lint in testfebcc03Merge pull request #451 from vip892766gma/maint/20260521171412c50e387chore: improve thiserror maintenance pathd4a2507Raise minimum tested compiler to rust 1.8599e8a6cUnpin CI miri toolchain9ac165cPin CI miri to nightly-2026-02-11