Releasing
To release, push a tag that starts with v:
git tag -a v0.6.0 -m "Wiring v0.6.0"
git push origin v0.6.0The release workflow builds a universal macOS .dmg and the Windows .msi and .exe installers, then attaches them to a draft GitHub release. Review the draft and publish it. Bump the version in package.json, src-tauri/tauri.conf.json and src-tauri/Cargo.toml before tagging.
The release's notes are the section of CHANGELOG.md for the tagged version: the workflow copies it into the release body, and the app shows those notes before it installs an update. Write them before the tag.
After you publish the release, rebuild the website so its landing page shows the new version.
The workflow signs and notarizes the macOS app and signs the Windows installers once the signing secrets are configured. Until then it builds unsigned. Code signing explains what to buy and which secrets to set. It also shows how to check a setup with a manual run (gh workflow run release.yml), which builds the installers as workflow artifacts without creating a release.
Installed copies update themselves from the latest published release; updates are signed with a separate updater key. Automatic updates explains the key, the secrets and how to check a release.