Skip to content

Upgrade Tauri ecosystem to 2.10.x#446

Open
AnthonyRonning wants to merge 1 commit intomasterfrom
chore/upgrade-tauri-2.10
Open

Upgrade Tauri ecosystem to 2.10.x#446
AnthonyRonning wants to merge 1 commit intomasterfrom
chore/upgrade-tauri-2.10

Conversation

@AnthonyRonning
Copy link
Contributor

@AnthonyRonning AnthonyRonning commented Feb 26, 2026

Upgrades all Tauri dependencies to latest versions.

Rust (Cargo.toml)

  • tauri 2.9.2 -> 2.10.2
  • tauri-build 2.5.1 -> 2.5.5
  • tauri-plugin-deep-link 2.4.5 -> 2.4.7
  • tauri-plugin-log 2.7.1 -> 2.8.0
  • tauri-plugin-updater 2.9.0 -> 2.10.0
  • tauri-plugin 2.1.1 -> 2.5.3
  • tauri-plugin-single-instance 2.3.6 -> 2.4.0
  • tauri-plugin-opener 2.5.2 -> 2.5.3
  • tauri-plugin-fs 2.4.4 -> 2.4.5

JS (package.json)

  • @tauri-apps/api 2.9.0 -> 2.10.1
  • @tauri-apps/cli 2.9.2 -> 2.10.0
  • @tauri-apps/plugin-deep-link 2.4.5 -> 2.4.7
  • @tauri-apps/plugin-dialog 2.4.2 -> 2.6.0
  • @tauri-apps/plugin-fs 2.4.4 -> 2.4.5
  • @tauri-apps/plugin-opener 2.5.2 -> 2.5.3

CI Workflows

Notable upstream changes

  • iOS simulator deadlock fix (2.9.3)
  • Android local video file access fix (2.10.0)
  • Deep link: Linux registration fix for paths with spaces (2.4.7)
  • CLI: tauri dev now only watches dependent workspace members (faster rebuilds)
  • No breaking changes for our codebase

Open with Devin

Summary by CodeRabbit

  • Chores
    • Updated Tauri CLI version from 2.9.2 to 2.10.0 in all build workflows (Android, desktop, mobile, and release pipelines) to maintain compatibility.
    • Upgraded Tauri API, CLI, and related plugins (deep-link, dialog, fs, opener, updater, and log) to compatible versions for improved stability and consistency across the project.

- tauri 2.9.2 -> 2.10.2, tauri-build 2.5.1 -> 2.5.5
- tauri-plugin-deep-link 2.4.5 -> 2.4.7, tauri-plugin-log 2.7.1 -> 2.8.0
- tauri-plugin-updater 2.9.0 -> 2.10.0, tauri-plugin 2.1.1 -> 2.5.3
- tauri-plugin-single-instance 2.3.6 -> 2.4.0, tauri-plugin-opener 2.5.2 -> 2.5.3
- tauri-plugin-fs 2.4.4 -> 2.4.5
- @tauri-apps/api 2.9.0 -> 2.10.1, @tauri-apps/cli 2.9.2 -> 2.10.0
- @tauri-apps/plugin-deep-link 2.4.5 -> 2.4.7, plugin-dialog 2.4.2 -> 2.6.0
- CI workflows: tauri-cli 2.9.2 -> 2.10.0, fix workaround comment to reference #14413

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
@coderabbitai
Copy link

coderabbitai bot commented Feb 26, 2026

📝 Walkthrough

Walkthrough

This pull request updates Tauri CLI and related dependencies from version 2.9.2 to 2.10.0 across GitHub Actions workflows, frontend package.json, and Cargo.toml files. Workflow step descriptions are also updated to reference bug #14413 instead of version-specific text.

Changes

Cohort / File(s) Summary
GitHub Actions Workflows
.github/workflows/android-build.yml, claude.yml, desktop-build.yml, mobile-build.yml, release.yml, testflight-on-comment.yml
Updated Tauri CLI version from 2.9.2 to 2.10.0 in cache keys and installation commands. Workflow step descriptions in android-build.yml and release.yml renamed to reference bug #14413 instead of version-specific workaround text.
Frontend Dependencies
frontend/package.json, frontend/src-tauri/Cargo.toml
Bumped Tauri CLI and related plugin dependencies: tauri-apps/api, tauri-apps/plugin-deep-link, tauri-apps/plugin-dialog, tauri-apps/plugin-fs, tauri-apps/plugin-opener, tauri-build, tauri, and tauri-plugin-* versions updated to newer minor/patch releases.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

🐰 Hops through workflows with cheer,
Version 2.10 is here!
Cache keys and installs aligned,
Dependencies refined,
No logic breaks the stride—
Just smoother sailing, countryside! 🌿

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Upgrade Tauri ecosystem to 2.10.x' accurately and concisely summarizes the main change: upgrading Tauri-related dependencies across the codebase to version 2.10.x.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/upgrade-tauri-2.10

Comment @coderabbitai help to get the list of available commands and usage tips.

@AnthonyRonning
Copy link
Contributor Author

@TestFlight build

@github-actions
Copy link
Contributor

🚀 TestFlight deployment triggered! Check the Actions tab for progress.

@cloudflare-workers-and-pages
Copy link

Deploying maple with  Cloudflare Pages  Cloudflare Pages

Latest commit: 38a4918
Status: ✅  Deploy successful!
Preview URL: https://cfa9fd9d.maple-ca8.pages.dev
Branch Preview URL: https://chore-upgrade-tauri-2-10.maple-ca8.pages.dev

View logs

Copy link
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

Open in Devin Review

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/mobile-build.yml (1)

46-53: ⚠️ Potential issue | 🟠 Major

Pin the installed Tauri CLI version, not just command presence.

The cache restore-keys (lines 51–53) use broad fallback prefixes that match any prior cached cargo-tauri binary, including older versions. The install step (line 121) checks only binary existence with command -v, allowing a previously cached v2.9.0 (or other version) to be reused, skipping the fresh install of the required v2.10.0. This causes version drift in CI.

The proposed fix verifies the actual installed version matches the required version before skipping reinstall:

Proposed fix
       - name: Install Tauri CLI
         run: |
-          if ! command -v cargo-tauri &> /dev/null; then
-            cargo install tauri-cli --version "2.10.0" --locked
+          REQUIRED_TAURI_CLI="2.10.0"
+          INSTALLED_TAURI_CLI="$(cargo-tauri --version 2>/dev/null | awk '{print $2}')"
+          if [ "$INSTALLED_TAURI_CLI" != "$REQUIRED_TAURI_CLI" ]; then
+            cargo install tauri-cli --version "${REQUIRED_TAURI_CLI}" --locked --force
           else
             echo "Tauri CLI already installed"
           fi

This same pattern appears in 5 other workflows: testflight-on-comment.yml, release.yml, desktop-build.yml, claude.yml, android-build.yml.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/mobile-build.yml around lines 46 - 53, The cache
key/restore-keys are too broad and the install step only checks for binary
presence, allowing older cached tauri CLI to be reused; update the cache key to
include the required version (e.g., append the Tauri CLI version string) and
tighten restore-keys accordingly, and change the install guard (the step that
currently uses command -v to skip install) to verify the actual installed
version by running the CLI version command (e.g., cargo tauri --version or the
exact binary used) and compare it to the required version (2.10.0) — if missing
or mismatched, run the install; apply the same key/version-check pattern to the
other workflows mentioned (testflight-on-comment.yml, release.yml,
desktop-build.yml, claude.yml, android-build.yml).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In @.github/workflows/mobile-build.yml:
- Around line 46-53: The cache key/restore-keys are too broad and the install
step only checks for binary presence, allowing older cached tauri CLI to be
reused; update the cache key to include the required version (e.g., append the
Tauri CLI version string) and tighten restore-keys accordingly, and change the
install guard (the step that currently uses command -v to skip install) to
verify the actual installed version by running the CLI version command (e.g.,
cargo tauri --version or the exact binary used) and compare it to the required
version (2.10.0) — if missing or mismatched, run the install; apply the same
key/version-check pattern to the other workflows mentioned
(testflight-on-comment.yml, release.yml, desktop-build.yml, claude.yml,
android-build.yml).

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2af8046 and 38a4918.

⛔ Files ignored due to path filters (2)
  • frontend/bun.lock is excluded by !**/*.lock
  • frontend/src-tauri/Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (8)
  • .github/workflows/android-build.yml
  • .github/workflows/claude.yml
  • .github/workflows/desktop-build.yml
  • .github/workflows/mobile-build.yml
  • .github/workflows/release.yml
  • .github/workflows/testflight-on-comment.yml
  • frontend/package.json
  • frontend/src-tauri/Cargo.toml

@github-actions
Copy link
Contributor

✅ TestFlight deployment completed successfully!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant