Admin: Client releases (fleet versions)
How platform admins set latest and min_supported per OS — and the safe order with CDN uploads.
Before you start
- Platform admin access on Hub (admin.flytype.ru / Admin Console).
- New build already uploaded to the download CDN when raising min_supported.
Steps
- 1
Open Admin → Client releases. Each platform (Mac, Windows, iOS, Android) has latest, min_supported, and optional download URL.
- 2
latest is advisory: clients on Remind/Insist show a soft update prompt. It does not hard-block older builds by itself.
- 3
min_supported is the hard floor: any client below this version gets a hard-block with a download link. Users cannot dismiss it.
- 4
Safe raise order: (1) upload/notarize the build to CDN or store, (2) set download_url if needed, (3) bump latest, (4) only then raise min_supported after canary users are healthy.
- 5
Rollback: lower min_supported (and latest if needed) in Admin. Env defaults still apply when DB overrides are empty — prefer Admin overrides for production.
- 6
Soft check TTL: Remind ~6h / Insist ~12h between soft prompts. Hard-block ignores TTL.
Common mistakes
- Never raise min_supported before the installer/APK/DMG is reachable — you will lock out the fleet.
- End-user update policy (Manual/Remind/Insist) is separate — see App updates and min supported version.
- Support: if someone is hard-blocked after a bad release, lower min_supported first, then fix CDN.