Chore/updater-devmode#1080
Conversation
There was a problem hiding this comment.
Pull request overview
This PR aims to reduce updater-related noise during development builds of the Tauri app.
Changes:
- Skip the updater check entirely in Rust when compiled with
debug_assertions. - Change the committed Tauri app version in
tauri.conf.jsonto0.0.0.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
src-tauri/tauri.conf.json |
Changes the app’s configured version to 0.0.0 (intended for dev-mode behavior). |
src-tauri/src/commands/updater.rs |
Adds a debug-build early return to avoid performing updater checks during development. |
| "productName": "HardwareVisualizer", | ||
| "mainBinaryName": "hardware-visualizer", | ||
| "version": "1.5.0", | ||
| "version": "0.0.0", |
There was a problem hiding this comment.
Setting the Tauri app version to 0.0.0 is likely to break the repo’s release/versioning workflows and produce incorrect app version metadata in non-tagged builds. The repo has a PR-time version check workflow that reads src-tauri/tauri.conf.json (.github/workflows/check-version.yml), and release builds patch this field via .github/scripts/update-tauri-config.ts; keeping 0.0.0 in the committed config will make that check fail and can also confuse update/version comparisons. Prefer keeping the real next version in tauri.conf.json (and relying on the new debug-only updater skip), or gate a dev-only version override via build tooling rather than committing 0.0.0.
No description provided.