chore(deps): bump Tauri ecosystem to 2.11#168
Conversation
Upstream tauri 2.11.0 is out, which unblocks the @tauri-apps/api 2.11.0 npm bump that has been pending since the May 4 dependabot batch. Three earlier dependabot PRs (#156 @tauri-apps/api, #153 @tauri-apps/plugin-fs, #158 @tauri-apps/plugin-dialog) were closed with EVERSIONMISMATCH because the Rust crate was still on 2.10.x. Aligning everything in a single commit to clear the lock. Source-level changes: - package.json: @tauri-apps/api ^2.9.1 -> ^2.11.0 - Cargo.toml: tauri-plugin-single-instance 2.4.1 -> 2.4.2 Lockfile-level (cargo update on the tauri family): - tauri 2.10.3 -> 2.11.0 - tauri-build 2.5.6 -> 2.6.0 - tauri-runtime / tauri-runtime-wry 2.10.1 -> 2.11.0 - tauri-utils 2.8.3 -> 2.9.0 - tauri-codegen / tauri-macros 2.5.5 -> 2.6.0 - tao 0.34.8 -> 0.35.2 - wry 0.54.4 -> 0.55.1 - tray-icon 0.21.3 -> 0.23.1 - muda 0.17.2 -> 0.19.1 Validation: cargo clippy --all-targets -D warnings clean, npm run build clean. Side note: tauri-plugin-fs 2.5.1 and tauri-plugin-dialog 2.7.1 were already on main from the May 5 dependabot triage (PR #157 merged, #153 closed and resolved by upstream caret semver), so they are not in this diff.
✅ 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThe PR updates two dependencies: ChangesDependency Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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) <[email protected]>
Summary
Bumps the Tauri ecosystem to 2.11 across both the Rust and the JS sides, unblocking the `@tauri-apps/api` 2.11.0 bump that was previously stuck behind the `tauri` crate version lock.
Three earlier Dependabot PRs from the May 4 batch (#156 `@tauri-apps/api`, #153 `@tauri-apps/plugin-fs`, #158 `@tauri-apps/plugin-dialog`) were closed with the same root cause: the npm bump tried to land while the Rust crate was still on 2.10.x, and `tauri info` rejects the install with `EVERSIONMISMATCH`. With 2.11.0 now upstream, this PR aligns both sides at once so future Tauri bumps can flow normally.
Source-level changes
Lockfile changes (cargo update on the tauri family)
Plus the usual transitive churn (objc2 family, dtor, ctor v0.2 -> v0.8, etc.).
Validation
Test plan
Side notes
Summary by CodeRabbit
These dependency updates are routine maintenance and may result in minor runtime improvements or compatibility adjustments visible to end users.