courtmanr@gmail.com daef38dd3c Stream release metadata so update checks see stable releases (#2282) ...

GitHub's release list is now ~9.6 MB because every 6.4.x release embeds
349 assets (~600 KB of JSON each). The update check buffered the whole
response behind a 1 MiB bound, so the primary path always failed and fell
through to the Atom feed. That feed holds ten entries and each release now
spends three of them, so stable-channel checks on main failed outright
("no suitable release found for channel stable") and 6.4.5 stable would
have shipped relying on it.

Decode the release list and the single-release notes response as a token
stream, keeping only tag, name, body, draft, prerelease, publish time and
the Pulse linux server archives. Memory now tracks what the updater keeps,
so the byte bound rises to 64 MiB while staying typed; the Atom feed stays
as the last resort for that over-limit condition only.

Verified against live GitHub: stable resolves v6.4.1 and rc resolves
v6.4.5-rc.3 through the primary path with no feed fallback.

2026-09-27 22:07:42 +01:00

..

internal

docs(agents): add customer support communication guidance

2026-08-11 16:39:36 +01:00

v6

Stream release metadata so update checks see stable releases (#2282)

2026-09-27 22:07:42 +01:00

control_plane.json

fix(release): map 6.4.5 reliability checkpoints to release line

2026-09-11 00:23:11 +01:00

control_plane.schema.json

Map legacy stable releases in control plane

2026-04-11 13:23:07 +01:00