MyStatus tracking for:Make your own task.
MyStatus Release Ledger
A ledger of all supported platforms. A register: one row per change. Required data structures (v1): A data row leads with key-value lines, one per line, ending at the first blank line. Everything after the blank line is prose. Readers take the keys they want and ignore the rest. A row that doesn't parse is prose, and that's fine — entries older than this contract are prose by definition. Keys this ledger promises: Platform: iOS | Android | Web Build: <whole number> Ride-along keys writers may add (readers ignore what they don't want): Verdict: ok | update_available | unsupported Anything else you need. One platform per data row. A change touching two platforms posts two rows, the later linking the earlier. Schema rule: adding keys is free. A breaking change (a renamed key, a changed meaning) closes this ledger with a link card to its successor task, whose first entry links back here.
A register: one row per change.
Tracked by tom.ortega
Updates
LivePlatform: iOS Build: 1 Verdict: ok Same change, second platform. The prose lives in the original entry; this row exists so a reader who wants data gets data.
Platform: Android Build: 5 Verdict: ok Re-registration of the Aug 25 change in the v1 data format — the first build carrying the client support check. The original prose entry remains the narrative record; this row is its machine-readable twin.
MyStatus — Android build 5, iOS build 1 These are the first builds carrying a client support check. At launch and on return to the foreground, each app asks the server whether its own build is still supported and renders whatever comes back: nothing, a dismissible notice, or a full-screen "update to continue". What that means for anything reading this ledger: - The verdict is a per-build lookup, not a version comparison. There is no minimum version to compute, and a build with no entry here is supported by definition. - Three verdicts: ok, update_available, unsupported. A client that sees a fourth treats it as ok. - Every notice and every block links back to a change record on this task, so there is always a written reason at a permanent address. - Nothing has been retired. This entry opens the record; it deprecates nothing. Android builds 2, 3 and 4 are registered here too. They predate the check and cannot ask, so no notice can ever reach them — the rows exist so the registry is complete, not because they can be warned.