Release Process

Automate Tauri app releases by creating a version tag and pushing it to trigger a GitHub Actions workflow that builds, signs, and publishes macOS artifacts. This CI/CD pipeline ensures consistent builds and updater integration across platforms.

Synchronize version fields across tauri.conf.json, package.json, and Cargo.toml by enforcing synchronization within your release workflow. This ensures consistent versioning across configuration files before tagging and triggering the CI/CD build.

Generate release notes from commit prefixes by applying structured release notes generation during your CI/CD pipeline. This mechanism automatically documents changes based on your commit message conventions when a release is published.

Yes, the release process supports Tauri updater integration for macOS targets. It coordinates end-to-end release workflows that include updater infrastructure configuration and validation to ensure automated application updates.

Validate a Tauri release pipeline end-to-end by configuring updater integration and triggering the workflow with a version tag. This process validates artifact generation, signing, and publishing across macOS targets and updater infrastructure.

You need to synchronize version fields before tagging to enforce consistent versioning across tauri.conf.json, package.json, and Cargo.toml. This prevents release failures and ensures the updater infrastructure references the correct build artifacts.