Skip to content

v0.3.10 — CA row reads /status itself

Choose a tag to compare

@chimneyQ chimneyQ released this 18 Oct 15:44
· 3 commits to main since this release

0.3.10

Fixed: the CA row said "file not found" while the file was there, and the button looked dead.

The row took its bundle from the settings-form snapshot (props.useToolkitCard). That model carries Config fields only — it never holds the status payload — so bundle was always {} and present was always false. The server was correct the whole time: /status returned present: true, bytes: 842639 while the badge said otherwise, and the click sent no request at all, because the row believed there was nothing to replace.

Fix: the row now fetches /status itself on mount and again after every export attempt, so the badge reflects the real file. A checking… state covers the first paint instead of flashing "missing".

New assertion: the row must call fetch(STATUS_PATH and must not read state.data…caBundle, so it cannot drift back onto the form snapshot.

Verified against the running routes: GET /status → present:true; POST export-ca with no force → 409 exists; with force:true → 200, 842140 bytes, 500 certificates.

Gates: offline 100 (1 new), client 27, packaging 20, release 34.

Full Changelog: v0.3.9...v0.3.10