chore(deps): batch patch bump (tokio, reqwest, quick-xml, blake3)#169
Merged
chore(deps): batch patch bump (tokio, reqwest, quick-xml, blake3)#169
Conversation
Four safe patch updates from the May 5 dependency check, all on the 1.x / 0.x stable lines: - tokio 1.52.1 -> 1.52.2 - reqwest 0.13.2 -> 0.13.3 - quick-xml 0.39.2 -> 0.39.3 - blake3 1.8.4 -> 1.8.5 russh / russh-sftp deliberately excluded from this batch. Bumping russh 0.60.1 -> 0.60.2 in isolation forces downgrades on a half-dozen pre-1.0 RC crypto crates (elliptic-curve, p256, p384, p521, rsa, spki, ml-kem) because the new russh has tighter version bounds. That needs a dedicated PR with a careful audit, not a drive through patch batch. Validation: cargo clippy --all-targets -D warnings clean (full rebuild after cargo clean, 4m28s).
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
axpnet
added a commit
that referenced
this pull request
May 5, 2026
The fallback-fixture job uses an isolated rust-cache shared-key (delta-sync-fallback) that is invalidated whenever Cargo.lock churns (deps-bump PRs from Dependabot, scheduled batch bumps, Tauri ecosystem upgrades). On a cold cache the workspace + Tauri + aeroftp lib compile takes 18-22 minutes before the integration test binary links, which exceeds the previous 15m ceiling and silently cancels the run. The sibling key-auth lane fits comfortably in 11 minutes with a warm default cache, so it stays at 15m. 25m on the fallback lane gives enough headroom for cold-start runs without parking PRs forever. Affects #168 and #169 which were both stuck on this timeout. Co-Authored-By: Claude Opus 4.7 (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
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.
Summary
Four safe patch updates from the May 5 dependency check, all on stable 1.x / 0.x lines:
Pure lockfile change (no `Cargo.toml` edits required, all four are declared with caret semver).
Why russh is not here
`russh` 0.60.1 -> 0.60.2 forces downgrades on a stack of pre-1.0 RC crypto crates (`elliptic-curve rc.31 -> rc.28`, `p256/p384/p521 rc.9 -> rc.7`, `rsa rc.17 -> rc.16`, `spki 0.8.0 -> 0.8.0-rc.4`, `ml-kem rc.2 -> rc.1`) because the new russh has tighter version bounds.
Downgrades on RC crypto crates are not safe to ship through a routine patch batch: they may revert security fixes that landed between rc.7 and rc.9. Tracking separately for a dedicated PR with audit.
Validation
Test plan