Updates: choose a release channel (stable or pre-release) #53

New Issue

2026-10-06T13:08:26Z

twisla commented

2026-10-06 13:08:26 +00:00

Idea

Let the device follow pre-releases as well as stable ones, or stay on stable only (#6, Q173).

Why

#6 reads releases/latest, which Gitea answers with the newest release that isn't a draft or a pre-release. There's no way to try a release candidate without a PC.

What's known

CI publishes every v* tag as a stable release (scripts/release_publish.py); a tag such as v0.12.0-rc1 would need to be marked pre-release there (prerelease: true).
The API lists pre-releases in releases?limit=N with the flag set.
The version comparison ignores git-describe suffixes (lib/ota/src/version_compare.h); -rc1 would need ordering rules.

Questions

A setting with Stable / Pre-releases, or only the Older releases list showing them?
How should v0.12.0-rc1 compare with v0.12.0 and v0.11.0?
Should CI mark a tag as pre-release by its name?

## Idea Let the device follow pre-releases as well as stable ones, or stay on stable only (#6, Q173). ## Why #6 reads `releases/latest`, which Gitea answers with the newest release that isn't a draft or a pre-release. There's no way to try a release candidate without a PC. ## What's known - CI publishes every `v*` tag as a stable release (`scripts/release_publish.py`); a tag such as `v0.12.0-rc1` would need to be marked pre-release there (`prerelease: true`). - The API lists pre-releases in `releases?limit=N` with the flag set. - The version comparison ignores git-describe suffixes (`lib/ota/src/version_compare.h`); `-rc1` would need ordering rules. ## Questions 1. A setting with Stable / Pre-releases, or only the Older releases list showing them? 2. How should `v0.12.0-rc1` compare with `v0.12.0` and `v0.11.0`? 3. Should CI mark a tag as pre-release by its name? ## Related `docs/milestones/R1.md` (Q173), #6, #5.

twisla added this to the R1 Releases milestone 2026-10-06 13:08:26 +00:00

twisla added the

area/gitea labels 2026-10-06 13:08:26 +00:00

twisla referenced this issue

2026-10-06 14:18:20 +00:00