Repository navigation
feat(updates): opt in to test versions (alpha/beta) from Settings - #103
Conversation
- New BetaUpdates setting (off by default), in desktop and console Settings. - The update check offers pre-releases when opted in or when a pre-release is already installed (UpdateChannel, tested); turning it off never downgrades. - Turning it on shows a warning; strings in pt-BR, en-US and es-ES. Co-Authored-By: Claude Opus 5.5 <[email protected]>
There was a problem hiding this comment.
ℹ️ Minor changelog convention suggestion inline.
Reviewed changes This review covers the opt-in prerelease update flow, its settings UI and persistence, localization, and tests.
- Update channel Stable builds can see prereleases when opted in; prerelease builds continue receiving prereleases.
- Settings Adds the saved option to desktop and console settings, with a warning when enabled.
- Localization and tests Adds the strings in all three catalogs and tests the channel-selection rule.
Note: 1 inline comment(s) dropped because they did not anchor to lines inside the PR diff:
CHANGELOG.en-US.md:30(RIGHT) — line 30 (RIGHT) is not inside a diff hunk
GPT Luna | 𝕏
|
One minor changelog convention note: please add
|
Co-Authored-By: Claude Opus 5.5 <[email protected]>
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes This review covers the newly added 1.5.1 release notes in both changelog languages.
- 1.5.1 changelog Added notes explaining that 1.5.1 users can opt into 1.6 test versions from Settings.
GPT Luna | 𝕏

Summary
UpdateChannel, unit-tested): pre-releases are offered when the user opted in or a pre-release is already installed. Turning it off never downgrades; a test build moves to the next stable one when it ships.The same change goes to a 1.5.1 built from
v1.5.0, so stable users can opt into the 1.6 tests.🤖 Generated with Claude Code