Repository navigation
Restore automatic Configurator updates with safe Vega disconnect - #73
Merged
Merged
Conversation
Restore application self-updates removed by the Tauri migration. Check at startup and through the clickable footer version, show release notes and download percentage, and verify signed packages before installation. Allow updates with a connected Vega by pausing status polling and port scans, waiting for current serial requests, and disconnecting before the download. Preserve normal polling and firmware exclusivity. Publish signed updater packages and a manifest with tagged releases; retain manual Debian updates. Verified 88 renderer and 68 Rust tests, lint/format/Clippy, release-contract and production-origin checks, signed Windows builds and the native demo install/restart flow. Read-only COM4 checks covered status, profile/preflight, and 50 reconnect cycles. macOS/Linux update acceptance remains outstanding.
Give the restored updater a new patch version instead of replacing the published 2.0.1 packages. Synchronize the Node, Cargo, and Tauri versions and lockfiles, update the README, and move the updater notes into the dated 2.0.2 changelog entry. Existing 2.0.0/2.0.1 installations need one manual upgrade. Verified the release contract and both 2.0.2/v2.0.2 tag forms, updater manifest tests, native version consistency and current-release checks, formatting, and the complete staged diff. No release tag or release is created.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Tauri migration removed application self-updates. Restore them in 2.0.2
through the native Tauri updater: check automatically at startup, allow a manual check by
clicking the footer version, and install only after confirmation. The update
dialog links to release notes and shows download percentage before signature
verification, installation, and restart.
An update can start while a Vega is connected. Pause status polling and port
scanning, wait for current serial commands to finish, then disconnect the Vega.
Keep the normal 250 ms status polling behavior and prevent concurrent firmware
operations or installation with unsaved edits.
Tagged releases publish signed updater packages and
latest.jsonfor Windows,Linux AppImage, and both macOS architectures. Sign Linux AppImages after the
Wayland patch. Debian packages continue to use manual installation.
Validation
opt-in.
origin checks passed.
passed.
signatures and rejection of altered installer bytes.
startup/manual checks, connected-device disconnection, increasing download
percentage, installation, restart, and the up-to-date result.
connect/disconnect cycles.
Release follow-up
TAURI_SIGNING_PRIVATE_KEYin GitHub Actions,matching the embedded public key. Updater signatures are separate from
Windows and macOS platform signing.
and restart flows still require platform acceptance.