Automatic Updates
Desktop builds include Tauri's updater plugin. On launch, RAV checks the GitHub Releases feed in the background. If a newer, Tauri-signed updater payload is available, the runtime strip shows an update chip.
Update Chip States
- Hidden — no update available
- UPDATE <version> — newer version ready to install
- UPDATING <version> — downloading and installing
- RESTARTING — installed, app relaunching
- UPDATE RETRY — last check or install failed, retryable
How Installation Works
Clicking the update chip downloads the updater artifact for your platform, verifies its Tauri signature with the public key embedded in RAV, installs it, and relaunches the app. On macOS, that archive contains the same Developer ID signed, notarized, and stapled app as the matching DMG. On Windows, the app-owned MCP bridge is shut down first to prevent file locking during update. The NSIS updater also installs the dedicated .riv icon, rewrites the document-icon registry value, and notifies Explorer after every update.
Release Feed
The updater only surfaces a new version after the full multi-platform release completes, all native-signing and artifact-parity checks pass, and the mergedlatest.json feed is published. Draft releases are ignored by thereleases/latest endpoint, so a partially complete release cannot advance installed clients.
Version 2.4.3 is published through the normal update feed for supported macOS and Windows installations.
Two Trust Layers
Apple Developer ID signing and notarization let macOS and Gatekeeper trust the application. Tauri's updater .sig authenticates the downloaded archive before RAV installs it. They are independent checks and every macOS update must pass both.
Retry Behavior
Failed updates no longer wait for a manual click. The app retries automatically on focus return, visibility change, network reconnection, and a short timer.
MCP Repair in 2.4.2
RAV 2.4.2 fixes the packaged MCP lookup regression in 2.4.1. The updater keeps rav-mcp beside the application executable, and the relaunched app now resolves that exact sibling path and refreshes an existing stable MCP launcher symlink automatically.