fix: upgrade tauri-plugin-updater to v2.10.0 to fix duplicate registry entries (#873)

[parkghost]

Before Submitting This PR

Please confirm you have done the following:

• I have searched existing issues and pull requests (including closed ones) to ensure this isn't a duplicate
• I have read CONTRIBUTING.md

Human Written Description

Issue #873 reports that OTA updates create duplicate Windows registry entries. I traced the root cause to tauri-plugin-updater v2.9.0 only reading the unsuffixed windows-x86_64 key in latest.json (which points to MSI), so NSIS-installed users receive MSI updates and end up with both HKCU and HKLM entries. v2.10.0 adds bundle-specific target resolution that fixes this. I verified the fix locally with end-to-end OTA testing on Windows.

Related Issues/Discussions

All three issues stem from the same root cause: tauri-plugin-updater v2.9.0 cannot distinguish between NSIS and MSI installers, causing NSIS-installed users to receive MSI updates. This creates duplicate registry entries (#873, #159) and requires admin rights that NSIS installs don't normally need (#562).

Community Feedback

Multiple users reported duplicate registry entries in #873, #159.

Testing

Root cause

1. latest.json has windows-x86_64 (unsuffixed, points to MSI) plus windows-x86_64-nsis / windows-x86_64-msi (suffixed)
2. tauri-plugin-updater v2.9.0 only reads the unsuffixed key
3. NSIS-installed users receive MSI update → creates HKLM entry alongside original HKCU entry

What v2.10.0 does

PR tauri-apps/plugins-workspace#2624 adds bundle-specific target resolution:

• Build time: tauri-cli patches __TAURI_BUNDLE_TYPE ("nsis" or "msi") into the binary
• Runtime: updater looks up windows-x86_64-nsis or windows-x86_64-msi first, falls back to windows-x86_64

Local end-to-end verification (2026-02-22)

Built v0.7.7 and v0.7.8 locally with tauri 2.10.2 + tauri-plugin-updater 2.10.0, set up a local OTA server serving both NSIS and MSI artifacts with bundle-specific keys, then ran full OTA update flow through the UI:

Test	Install v0.7.7 via	OTA updater selects	After update	Result
NSIS → NSIS	NSIS setup.exe	windows-x86_64-nsis → NSIS exe	HKCU v0.7.8 only	PASS
MSI → MSI	MSI .msi	windows-x86_64-msi → MSI .msi	HKLM v0.7.8 only	PASS

Note for maintainer: [patch.crates-io] update needed

This PR temporarily points [patch.crates-io] to parkghost/tauri branch handy-2.10.2 (the macOS work_area.position.y fix cherry-picked onto tauri v2.10.2) so CI can build. Before merging, please:

1. Create handy-2.10.2 branch on cjpais/tauri: git checkout -b handy-2.10.2 tauri-v2.10.2 && git cherry-pick 8ba98c7
2. Update [patch.crates-io] in this PR to point back to cjpais/tauri

For affected users (NSIS install that received MSI update)

Handy provides both NSIS (.exe) and MSI (.msi) installers. If you were originally installed via NSIS and received an MSI update through OTA, you now have duplicate registry entries (both HKCU and HKLM).

The simplest fix is to uninstall both entries manually and reinstall:

1. Open Settings → Apps → Installed apps
2. Search for "Handy" — you'll see two entries
3. Uninstall both
4. Re-download and install from the latest release (pick either NSIS or MSI, just use one)

Once the updater is upgraded to v2.10.0, future OTA updates will always deliver the matching installer type, so this issue won't recur.

Screenshots/Videos (if applicable)

AI Assistance

• AI was used (please describe below)

If AI was used:

• Tools used: Claude Code (Claude Opus 4.6)
• How extensively: Assisted with dependency research, root cause analysis, local OTA test setup, and PR drafting

[cjpais]

Looks like we should just be upgrading to tauri 2.10 overall. I will likely be closing this PR and working on this. For now I will leave it open to track. Thank you for the research and testing!