Product Versioning

The Sambee product version has one source of truth. Use this page whenever you change the product version, whether for a prerelease or a stable release.

Product Version Source of Truth

The application version lives in:

• VERSION

When the product version changes:

1. Update VERSION.
2. Run ./scripts/sync-version.
3. Review all resulting metadata changes together.

The sync step updates version-bearing frontend and Companion files so they do not drift away from the root version.

Files That Move with Product Version Changes

The sync workflow updates files such as:

• frontend/package.json
• frontend/package-lock.json
• companion/package.json
• companion/package-lock.json
• companion/src-tauri/Cargo.toml
• companion/src-tauri/tauri.conf.json
• companion/src-tauri/Cargo.lock

Treat those edits as release metadata, not as noise to separate later.

Validation

Run the version sync before validating the affected release surfaces. At minimum, review the generated metadata and run the checks required by the changed subsystem.

Common examples:

./scripts/sync-version
cd backend && pytest -v
cd backend && mypy app
cd frontend && npx tsc --noEmit && npm run lint
cd companion && npx tsc --noEmit && npm run lint

Use Release Checklist for the complete product-release sequence.