Skip to content

fix(updater): the Beta channel offers the highest version, not the first release by date (#1493) - #1691

Merged
ZhuchkaTriplesix merged 1 commit into
devfrom
fix/updater-beta-picks-highest-semver
Oct 17, 2026
Merged

ZhuchkaTriplesix merged 1 commit into
devfrom
fix/updater-beta-picks-highest-semver

Conversation

@ZhuchkaTriplesix

Copy link
Copy Markdown
Member

Closes #1493. Part of the Beta channel epic #1499.

GitHubReleasesClient.fetchLatest(channel: dev) (Preferences: Beta / Early Access) returned the first non-draft entry of /releases, which the API orders by creation date. After 0.5.0-beta.2, a hotfix 0.4.20 published from main became the first entry, so a user on 0.4.19 was offered the hotfix and never the newer beta.

  • pickNewestRelease(releases) returns the release with the highest UpdateVersion (compareTo: a stable release outranks its own beta, beta.10 above beta.2). Drafts and tags that do not parse are skipped; an empty or all-unusable list is still No published releases found.
  • The Stable channel is unchanged (releases/latest). Only the first page of the list is read, as before.

Tests: the order cases from the issue (hotfix after beta, beta then stable, beta.10 vs beta.2, leading v, drafts and non-version tags, empty list) and fetchLatest through a mock HTTP client.

@github-actions github-actions Bot added bug Something isn't working P2 Medium priority / Parity & Refactoring labels Oct 17, 2026
@ZhuchkaTriplesix
ZhuchkaTriplesix merged commit ec184ce into dev Oct 17, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working P2 Medium priority / Parity & Refactoring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant