Tauri Release and Distribution

Treat release automation and signing as security-sensitive production code. Inspect existing Tauri config, manifests, CI, updater configuration, branch policy, artifact naming, and target platforms before editing.

Define Release Invariants

• One release version is synchronized across frontend, Rust, and Tauri manifests.
• Every supported target produces an expected, identifiable artifact.
• Signing keys remain outside source control and logs.
• Updater metadata and signatures match uploaded artifacts.
• A failed platform build cannot silently produce a partial public release.
• Release reruns are idempotent or explicitly guarded.

Separate Signing Concerns