chore: update dependencies 2026-08-03 - #815
Merged
Merged
Conversation
Sweep every workspace dependency to its latest release (`cargo upgrade --incompatible` + `cargo update`), and the UI's npm lockfile (vanilla-jsoneditor 3.11 -> 3.13). Major/minor bumps that needed attention: - sentry 0.48 -> 0.49 makes `ClientOptions` `#[non_exhaustive]`, so struct expressions no longer compile. Build it through the new setters instead; `dsn` is still assigned as a field because the `dsn` setter takes a `&str` and panics on a malformed value, where `get_sentry_dsn` warns and disables Sentry. - serial_test 3 -> 4, base64 0.22 -> 0.23, jsonschema 0.48 -> 0.49, aws-sdk-s3 1.138 -> 1.140, aws-config 1.9 -> 1.10: no source changes. The bigger AWS SDK / reqwest / Tauri / Sentry state machines pushed the whole command-future cluster from ~18.4 KB to ~19.7 KB, so `clippy.toml`'s `future-size-threshold` moves with it (18500 -> 19800). Boxing instead would have meant `Box::pin` at ~20 call sites, mostly in tests — the trade-off `clippy.toml` already documents. Verified: `cargo fmt --check`, `just lint` (native + wasm), `cargo nextest run` (597 core + 276 quilt-sync tests), `cargo test --doc`, `just test-frontend` (35 wasm tests), `trunk build --release`, `cargo deny check` — all pass. Every `deny.toml` advisory ignore is still live (checked with `unused-ignored-advisory`), so none were pruned. Co-Authored-By: Claude Opus 5 (1M context) <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
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.
Sweeps every workspace dependency to its latest release (
cargo upgrade --incompatible+cargo update) and the UI's npm lockfile, ahead of the QuiltSync v0.20.1 release.Bumps
Manifests: base64 0.22 → 0.23, aws-config 1.9 → 1.10.1, aws-sdk-s3 1.138.1 → 1.140.0, aws-types 1.4 → 1.5, clap 4.6.2 → 4.6.5, jsonschema 0.48.1 → 0.49.3, tokio 1.53.0 → 1.53.1, tokio-stream 0.1.18 → 0.1.19, sentry 0.48.5 → 0.49.1, serial_test 3 → 4, leptos_router 0.8.14 → 0.8.15.
Lockfiles: 35 transitive crates; npm
vanilla-jsoneditor3.11 → 3.13. Two transitive crates stay behind latest (crypto-common,proc-macro-crate) — held back by upstream requirements.Source changes the bumps forced
sentry 0.49 makes
ClientOptions#[non_exhaustive], so neither struct expression intelemetry/sentry.rscompiles any more (E0639— functional-update syntax is barred too). It is now built through the new setters.dsnstays a direct field assignment because thedsnsetter takes a&strand panics on a malformed value, whereget_sentry_dsnwarns and disables Sentry instead.clippy.toml'sfuture-size-thresholdmoves 18500 → 19800. The fatter AWS SDK / reqwest / Tauri / Sentry state machines shifted the whole command-future cluster from ~18.4 KB to ~19.7 KB, trippinglarge_futuresin 23 places. Boxing instead would have meantBox::pinat ~20 call sites, 16 of them inquilt-clitests — the whack-a-mole trade-offclippy.tomlalready documents. Boxing the two app-side outliers first was tried; it only exposed the rest of the shifted cluster.Verification
Every CI gate run locally on this branch, rebased onto
main:cargo fmt --all -- --checkjust lint— native + wasm, zerolarge_futuresat the new budgetcargo nextest run --workspace --all-targets --exclude quilt-sync --exclude quilt-sync-ui— 597 passedcargo nextest runinquilt-sync/src-tauri— 281 passedcargo test --doc— passjust test-frontend— 40 wasm tests passedtrunk build --release— passcargo deny check— advisories, bans, licenses, sources okEvery
deny.tomladvisory ignore is still live — checked by temporarily settingunused-ignored-advisory = "warn", which reported noadvisory-not-detected. Nothing to prune.Open Renovate PRs covering these crates (#757, #775, #777, #778, #779, #792, #794, #801, #805, #806) are subsumed by this sweep but left open deliberately.
🤖 Generated with Claude Code
Greptile Summary
The PR updates workspace Rust and frontend dependencies ahead of QuiltSync v0.20.1, adapts Sentry configuration to its non-exhaustive options API, and adjusts the large-future lint budget for dependency-driven growth.
vanilla-jsoneditorand related packages.Confidence Score: 5/5
The PR appears safe to merge, with no concrete changed-code defect identified.
The Sentry migration preserves the existing configuration values, the dependency manifests and lockfiles remain internally consistent, and the investigated security advisories belong to unchanged, explicitly acknowledged transitive dependencies.
Important Files Changed
Reviews (1): Last reviewed commit: "chore: update dependencies 2026-08-03" | Re-trigger Greptile
Context used: