Surface per-component update status on Configuration page and /version #985
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#985
Reference in new issue
Block a user
Part 3/3, point 5 of archie-core-1786751948782-3-837a8fd0's design. Depends on the InstallType/Reference issue landing first -- there's nothing to surface otherwise. Add a /version endpoint and a per-component block on the Configuration page (internal/webui/api_config.go, ui/src/settings/), structured as {install_type, running_version, reference, latest_available, status} per component, where status is an enum (ok / update_available / drift / unknown) rather than a bare color. The actual comparison basis (e.g. running digest vs latest digest) should be visible on hover/expand, modeled on docker version's Client/Server nested-block convention per the original design doc.
Close reason
Fixed: GET /api/version + Configuration-page 'Update status' card, sourced from the InstallType/Reference/RunningVersions plumbing landed in .1/.2. Adversarial review found one real bug (Installed=='' with Available set incorrectly returned update_available instead of unknown) and one test gap (present-but-empty running-version map entry) -- both fixed, tests added, all green. [Closure restored 2026-08-24: originally closed 2026-08-23, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]
Imported from beads
archie-core-1786751948782-3-837a8fd0.3· GitHub #611 · type feature · priority P2 · created 2026-08-23 · closed 2026-08-24