Release artifacts, platform support boundaries, local build requirements, and the OS-specific behavior that affects install, packaging, or runtime.
- Windows-first rollout notes
- macOS and Linux staging expectations
- Local build prerequisites
- Platform-specific runtime behavior
Applies to
WindowsmacOSLinux
Covers
PlatformsSetupBuildTroubleshooting
Platform setup and environment notes
Current public rollout
The current public rollout is intentionally staged:
- Windows is the first verified target
- macOS requires a proper macOS host and signing or notarization path
- Linux packaging remains staged behind the public release flow
Desktop support model
Across supported desktop platforms:
- secrets are stored in the platform secret store
- operational commands stay in the desktop backend
- local data remains on the device
- website analytics do not change desktop runtime behavior
Local build prerequisites
You need:
- Node.js 20+
- Rust toolchain
- Tauri platform prerequisites for the target OS
Typical examples:
- Windows: WebView2 and MSVC build tooling
- macOS: Xcode command line tools
- Linux: WebKitGTK and tray-related dependencies required by Tauri