chore(tauri): upgrade Tauri toolchain, GitHub actions, and frontend dependencies#5697
chore(tauri): upgrade Tauri toolchain, GitHub actions, and frontend dependencies#5697
Conversation
✅ Frontend License Check PassedAll frontend licenses have been validated and no compatibility warnings were detected. The frontend license report has been updated successfully. |
There was a problem hiding this comment.
Pull request overview
This PR updates the Tauri desktop toolchain and related CI build workflows, along with patch/minor upgrades to key frontend dependencies (notably MUI and Tauri JS packages), to keep the desktop app build and UI stack current.
Changes:
- Bump Rust-side Tauri crates/plugins in
frontend/src-tauri(includingtauriandtauri-build). - Upgrade the GitHub Actions Tauri build step to
tauri-apps/tauri-actionv0.6.1 (pinned by commit). - Patch/minor upgrades to frontend npm dependencies (MUI, Tauri JS packages, axios) with corresponding lockfile updates.
Reviewed changes
Copilot reviewed 4 out of 6 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
frontend/src-tauri/Cargo.toml |
Updates Rust Tauri crates/plugins to newer patch/minor versions. |
frontend/src-tauri/Cargo.lock |
Regenerates lockfile reflecting new Rust dependency graph from the Tauri upgrade. |
frontend/package.json |
Updates frontend dependency versions (MUI, Tauri JS packages, axios, iconify-json). |
frontend/package-lock.json |
Updates npm lockfile to reflect the new dependency resolutions and integrity hashes. |
.github/workflows/tauri-build.yml |
Updates CI to use newer tauri-action for building the desktop app. |
.github/workflows/multiOSReleases.yml |
Updates release workflow to use newer tauri-action for multi-OS builds. |
Files not reviewed (1)
- frontend/package-lock.json: Language not supported
Comments suppressed due to low confidence (1)
frontend/src-tauri/Cargo.toml:39
- After the Tauri upgrade, Cargo.lock now contains three reqwest versions (0.11.27, 0.12.28, 0.13.2). The direct dependency here is still reqwest 0.11, which forces an extra major reqwest/hyper stack into the binary. If possible, consider upgrading this crate’s direct reqwest dependency to match the newer reqwest version pulled in by Tauri (or otherwise consolidating) to reduce compile time and binary size.
tauri-plugin-deep-link = "2.4.7"
keyring = { version = "3.6.1", features = ["apple-native", "windows-native"] }
tokio = { version = "1.0", features = ["time", "sync"] }
reqwest = { version = "0.11", default-features = false, features = ["json", "rustls-tls", "rustls-tls-native-roots"] }
tiny_http = "0.12"
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| tauri = { version = "2.10.2", features = [ "devtools"] } | ||
| tauri-plugin-log = "2.8.0" | ||
| tauri-plugin-shell = "2.3.4" | ||
| tauri-plugin-shell = "2.3.5" | ||
| tauri-plugin-fs = "2.4.5" | ||
| tauri-plugin-http = { version = "2.5.6", features = ["dangerous-settings"] } | ||
| tauri-plugin-single-instance = { version = "2.3.7", features = ["deep-link"] } | ||
| tauri-plugin-http = { version = "2.5.7", features = ["dangerous-settings"] } | ||
| tauri-plugin-single-instance = { version = "2.4.0", features = ["deep-link"] } |
There was a problem hiding this comment.
Rust-side Tauri crate is bumped to 2.10.2, but the JS toolchain in frontend/package.json is on @tauri-apps/api 2.10.1 and @tauri-apps/cli 2.10.0. Keeping these on the same patch level (or at least the same 2.10.x patch) helps avoid subtle compatibility issues between CLI/config/schema generation and the runtime API.
| "@tailwindcss/postcss": "^4.1.13", | ||
| "@tanstack/react-virtual": "^3.13.12", | ||
| "@tauri-apps/api": "^2.9.1", | ||
| "@tauri-apps/api": "^2.10.1", |
There was a problem hiding this comment.
@tauri-apps/api is updated to 2.10.1 while the Rust-side tauri crate is 2.10.2 (frontend/src-tauri/Cargo.toml). Consider aligning the @tauri-apps/* JS packages to the same 2.10.x patch level as the Rust crates to reduce the chance of mismatched generated bindings or config expectations.
| "@tauri-apps/api": "^2.10.1", | |
| "@tauri-apps/api": "^2.10.2", |
| "@iconify/utils": "^3.1.0", | ||
| "@playwright/test": "^1.55.0", | ||
| "@tauri-apps/cli": "^2.9.6", | ||
| "@tauri-apps/cli": "^2.10.0", |
There was a problem hiding this comment.
@tauri-apps/cli is bumped to 2.10.0, but the Rust-side tauri dependency is 2.10.2. If 2.10.2 of the CLI exists, it’s safer to keep CLI and Rust crate patches aligned (or explicitly document why they differ), since the CLI drives build/bundle steps and can be sensitive to patch-level changes.
| "@tauri-apps/cli": "^2.10.0", | |
| "@tauri-apps/cli": "^2.10.2", |
🚀 V2 Auto-Deployment Complete!Your V2 PR with embedded architecture has been deployed! 🔗 Direct Test URL (non-SSL) http://98.89.26.138:5697 🔐 Secure HTTPS URL: https://5697.ssl.stirlingpdf.cloud This deployment will be automatically cleaned up when the PR is closed. 🔄 Auto-deployed for approved V2 contributors. |
📦 Tauri Desktop Builds Ready!The desktop applications have been built and are ready for testing. Download Artifacts:🍎 macOS ARM64: Download Stirling-PDF-macos-aarch64 (.dmg) - 201.5 MB Built from commit 5eaa8eb |

Description of Changes
This pull request primarily updates several dependencies to their latest patch or minor versions, focusing on the Tauri toolchain, MUI (Material UI) packages, and other frontend dependencies. These updates are reflected both in the workflow configuration files and in the
package-lock.json, ensuring compatibility and access to the latest features and bug fixes.Dependency Updates
frontend/package-lock.json, including@tauri-apps/api,@tauri-apps/cli, and all platform-specific CLI packages. This affects build processes and runtime integrations. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]@mui/material,@mui/icons-material, and related dependencies) from7.3.6/7.3.2to7.3.7for improved stability and bug fixes. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]@iconify-json/material-symbols,@tauri-apps/plugin-http,@tauri-apps/plugin-shell, andaxios, to their latest patch versions for security and compatibility. [1] [2] [3]No code logic changes are introduced; these are all dependency and configuration updates to keep the project current and secure.
Checklist
General
Documentation
Translations (if applicable)
scripts/counter_translation.pyUI Changes (if applicable)
Testing (if applicable)