Repository navigation
fix(deps): revert @tauri-apps npm minors to the crate-aligned set that built v3.6.0 - #289
Conversation
…t built v3.6.0 Dependabot PR #281 bumped the @tauri-apps npm side one minor past the Rust crates (api 2.12.0 vs tauri crate 2.11.1, plugin-dialog 2.8.0 vs 2.7.1, plugin-shell 2.4.0 vs 2.3.5, plugin-notification 2.5.0 vs 2.4.0) and moved the CLI to 2.12.0, whose new version-mismatch check fails 'tauri build' at startup. Both tag builds since then died there — v3.7.0 (run 39142261007) and v3.8.0 (run 39169196832) shipped ZERO release assets, so the v3.8.0 release page has no .deb and the installed dpkg is still 3.6.0. The frontend src/ is byte-identical between v3.6.0 and v3.8.0 (verified: git diff --stat v3.6.0 v3.8.0 -- src/ is empty), so the app needs none of the new minors. This restores exactly the dependency state of the last green tag build (v3.6.0, run 39078950717); the lockfile diff is confined to the six @tauri-apps entries. A coordinated Rust-side bump can ride a later Dependabot round once both sides move together.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly identifies the dependency revert and the reason for it: restoring the crate-aligned @tauri-apps minor versions. |
| Description check | |
The description directly explains the Tauri build failures, the dependency mismatch, the six-package revert, and the reported verification results. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
A rabbit checks the version list,
Six pins hop back, each neatly placed.
The package leaves no crumb amiss,
Then bounds away at its own pace.
Soft paws tap out a tidy trace.
Comment @coderabbitai help to get the list of available commands.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
ℹ️ No reviewable code changes in this PR Last run: 2026-10-18 22:17 UTC |
|
🎉 This PR is included in version 3.8.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
1 participant
Problem
Both tag builds since Dependabot #281 merged (2026-10-18 03:15Z) fail at
tauri build:.deb; the installed dpkg is still 3.6.0.The @tauri-apps/cli 2.12 bump introduced the strict npm↔crate minor-alignment check; the Rust crates were not bumped to match.
Fix
Revert the six
@tauri-apps/*entries (incl.plugin-openerandcli) to exactly the values of the last green tag build (v3.6.0, run 39078950717), and regenerate the lockfile withpnpm install --lockfile-only.Why the revert is safe
git diff --stat v3.6.0 v3.8.0 -- src/is empty — the frontend is byte-identical to what v3.6.0 shipped, so it uses none of the new-minor APIs.tauriand friends unchanged inCargo.lockbetween v3.6.0 and v3.8.0).Verification
pnpm install --lockfile-onlyclean; lockfile diff confined to the six reverted entries.