Journey event  ·  14 Sep 2026

master does not typecheck — MediaStorageCard uses a badge tone that does not exist

FIXED 2026-09-12 in 9e7fb49 (merged 226083b, pushed; not yet deployed). Both StatusChip tone="teal" uses in MediaStorageCard (the SAVING HERE chip at :41 and the done-job tone at :

  state copied from the tracker, never improved

  event date 2026-09-14

Event date 2026-09-14
Version found
Version fixed
Expected kit firmware
Release file
SHA-256
Served count
Source https://app.notion.com/3d92b4cda3708129b414f1dd07949856

FIXED 2026-09-12 in 9e7fb49 (merged 226083b, pushed; not yet deployed). Both StatusChip tone=”teal” uses in MediaStorageCard (the SAVING HERE chip at :41 and the done-job tone at :77) changed to “ok”, the closest valid positive tone in the union – a judgement call on intent, since “teal” suggests a distinct accent that does not exist. npx tsc –noEmit is now clean across the tree, which it was not at the start of the day. ORIGINAL: two errors, Type ‘”teal”‘ is not assignable to type ‘”warn” | “ok” | “bad” | “muted” | undefined’, introduced by 0e6a893. They shipped unnoticed because the build script is a bare ‘vite build’ with no tsc step. STILL OPEN and the more important half: nothing runs a typecheck before or during a build, so the next one will ship just as silently. Worth adding tsc –noEmit to the build script or to CI – that part of this row is not fixed.

All events  ·  DSC  ·  CannaLib  ·  Site  ·  Firmware releases

Empty rows are honest

A blank cell means the tracker has no value for it. Nothing on this page is filled in to look complete.