Two GitHub Actions workflows handle builds and releases automatically.
- Trigger: Every push to
main - What it does: Builds for Windows, Linux, macOS (both Intel + Apple Silicon)
- Where: Artifacts appear on the Actions tab β click a run β scroll down to "Artifacts"
- Artifacts expire after 30 days
- Trigger: Push a
v*tag (e.g.v0.1.0,v1.2.3) - What it does: Builds + creates a draft GitHub Release
- Draft means: It's not public until YOU review and publish it
Edit src-tauri/tauri.conf.json and update the version:
{
"version": "0.2.0"
}Also update package.json if you want them to match:
{
"version": "0.2.0"
}git add .
git commit -m "bump version to 0.2.0"
git pushgit tag v0.2.0
git push origin v0.2.0Go to your repo β Actions tab β watch the release workflow run.
Go to Releases β you'll see a draft release with auto-generated release notes.
- Review the notes (edit if needed)
- Attach any extra files if you want
- Click Publish release
That's it.
- Go to your repo β Actions tab
- Click the latest successful "Build" run
- Scroll down to Artifacts
- Download the platform you need
The .github/release.yml file controls how release notes are auto-generated.
Use these labels on PRs to categorize them:
| Label | Category |
|---|---|
feature, enhancement |
Features |
bug, bugfix, fix |
Bug Fixes |
breaking-change |
Breaking Changes |
improvement, refactor, performance |
Improvements |
dependencies |
Dependencies |
PRs without a label go into "Other Changes".
# See current tags
git tag
# Delete a local tag (if you made a mistake)
git tag -d v0.2.0
# Delete a remote tag
git push origin --delete v0.2.0
# Check what version is set
cat src-tauri/tauri.conf.json | grep version