Release

This page explains the release process whereby installers are added to a Release on the project GitHub page.

Following an important update, increment the Application version (we are using the same version number in Cargo.toml and package.json and tauri.conf.json). The version number will be something like 0.5.12. The npm version patch script will increment patch version in Cargo.toml and package.json and create the tag. You will see the new tag version on the shell. Use this (adjust v.0.5.???) to push to origin. This will trigger a new release.

git add .
git commit -m "<whatever>"
npm version patch  
git push origin <tag>

(e.g., git push origin v0.5.129)

If all goes well, this will add a new release with Mac, Windows, and Debian/Ubuntu installers.

Git tags

Here are some tips for dealing with the tags.

  1. Update the local tags
git fetch --prune --prune-tags origin
  1. Show the available tags
git tag
  1. Show latest tag
git describe --tags --abbrev=0

Note that we have run the following command

npm config set tag-version-prefix v

Manual release

To create an installer locally (for the current OS), enter the following command

npm run tauri build

This will create an installer under src-tauri/target/release/bundle/.