Quick reference for creating a new release.
Windows (PowerShell):
.\bump-version.ps1 0.2.0Linux/Mac:
./bump-version.sh 0.2.0Add your changes under a new version section:
## [0.2.0] - 2025-10-06
### Added
- New feature X
### Changed
- Improved Y
### Fixed
- Fixed bug Z# Review changes
git diff
# Commit
git add .
git commit -m "chore: bump version to 0.2.0"
# Tag
git tag v0.2.0
# Push (this triggers the build)
git push origin main
git push origin v0.2.0- Go to: https://github.com/t21dev/porter-app/actions
- Wait for "Release" workflow to complete (~10-15 min)
- Builds Windows, macOS, and Linux automatically
- Go to: https://github.com/t21dev/porter-app/releases
- Find the draft release
- Click "Edit"
- Review auto-generated notes from CHANGELOG
- Add screenshots if needed
- Click "Publish release"
Before tagging:
- Version bumped in all 3 files (package.json, Cargo.toml, tauri.conf.json)
- CHANGELOG.md updated with changes
- All tests passing locally
- Build works locally (
npm run tauri:build) - No pending commits
- On main branch
Must update these 3 files:
package.json→ Line 3src-tauri/Cargo.toml→ Line 3src-tauri/tauri.conf.json→ Line 4
./bump-version.ps1 0.1.1./bump-version.ps1 0.2.0./bump-version.ps1 1.0.0./bump-version.ps1 0.2.0-betaThe workflow automatically:
- ✅ Extracts changelog for the version
- ✅ Builds Windows (MSI, NSIS)
- ✅ Builds macOS (DMG, App)
- ✅ Builds Linux (AppImage, DEB)
- ✅ Creates draft release
- ✅ Attaches all installers
- ✅ Includes changelog in release notes
After release, users can download:
Windows:
Porter_0.2.0_x64_en-US.msi(recommended)Porter_0.2.0_x64-setup.exe
macOS:
Porter_0.2.0_x64.dmgPorter.app.tar.gz
Linux:
Porter_0.2.0_amd64.AppImagePorter_0.2.0_amd64.deb
git tag -d v0.2.0 # Delete local
git push origin :refs/tags/v0.2.0 # Delete remote- Check GitHub Actions logs
- Re-run workflow from Actions tab
- Or delete tag and re-push
- Can edit release notes manually on GitHub
- Or delete tag, update changelog, re-tag
See docs/version-management.md for complete details.