feat(updater): beta update channel + prerelease release pipeline#398
Merged
Conversation
- Release workflow publishes beta.json to a rolling 'updater' release on every release (semver-guarded) so the beta channel always tracks the newest build of either kind; prerelease tags skip the MSI bundle (WiX rejects SemVer prerelease versions) and ship NSIS only - New check_app_update Tauri command rebuilds the updater against the selected channel's manifest endpoint and registers the update in the webview resource table, so the plugin's Update download/install flow works unchanged; channel-to-URL mapping stays in Rust - general.updateChannel setting (auto|stable|beta, default auto: prerelease builds track beta, release builds track stable) with a stable/beta select in General settings; switching re-checks immediately and never downgrades Pre-commit hook ran. Total eslint: 0, total circular: 0
Collaborator
|
Reviewed with fable - LGTM |
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
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.
Summary
Adds a stable/beta update-channel system: users can opt into prerelease builds from Settings, and the release pipeline can ship betas that auto-update along their own channel.
Release pipeline (
release.yaml)vX.Y.Z-beta.N(for the next unreleased X.Y.Z) — same workflow, marked as GitHub prerelease as before.beta.jsonto a rollingupdaterrelease (auto-created on first run, semver-guarded against out-of-order rebuilds). The beta channel therefore always points at the newest build of either kind, so beta users converge back onto stable once it overtakes the last beta. The stable channel keeps using the untouchedreleases/latest/download/latest.jsonalias — zero change for existing installs.Backend
check_app_update(channel)command: rebuilds the updater against the selected channel's manifest endpoint and registers the result in the webview resource table — the plugin's ownUpdateclass (download/install/close) keeps working unchanged. The channel→URL map lives in Rust so page code can never point the updater at arbitrary URLs, preserving the updater plugin's security posture.Frontend
general.updateChannelsetting:auto | stable | beta, defaultauto— prerelease builds track beta, release builds track stable, so a manually installed beta DMG keeps updating along the beta channel without touching any toggle.1.1.25-beta.N < 1.1.25).Test plan
cargo check+cargo clippyclean (no findings in new code)v1.1.25-beta.1tag and verify theupdaterrolling release getsbeta.json, a beta install self-updates tobeta.2, and a stable install stays untouchedCloses #399