Overview - Console

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
2751/merge
151f6880 fix(services): allow keyboard navigation in port modals
by Théo Grandin
Canceled
2751/merge
735558fc format check
by Théo Grandin
Failed
2751/merge
07a37428 linter pass
by Théo Grandin
Failed
2751/merge
67ff628c fix(clusters): derive feature card state from form
by Théo Grandin
Failed
2751/merge
377d5b9a fix(clusters): allow feature card switch deactivation
by Théo Grandin
Failed
2751/merge
038e04e2 fix(shared-ui): remove toggle compatibility fallback
by Théo Grandin
Failed
2751/merge
db995ff4 test(clusters): assert production toggle switch state
by Théo Grandin
Failed
2751/merge
c5295d8c fix(shared-ui): preserve unnamed toggle display value
by Théo Grandin
Failed
2751/merge
7bd9b81a test(shared-ui): update input toggle snapshots
by Théo Grandin
Failed
2751/merge
a0840d38 fix(shared-ui): migrate input toggle to radix switch
by Théo Grandin
Failed
2751/merge
41f2d42b fix(ui): make InputToggle keyboard accessible The InputToggle used a hidden checkbox and onClick-only div handlers, so it was not reachable or operable via the keyboard. On the service port settings form this broke Tab navigation: keyboard users could reach the default fields (application port, protocol) but could not focus or toggle the 'Publicly exposed' switch that gates the advanced fields (e.g. port name). Expose the toggle as a focusable switch (role=switch, aria-checked, tabIndex) with Space/Enter activation and a visible focus outline, while keeping it non-focusable when disabled.
by Claude