0.3.240

0.3.240

Changes

• frontend + frontend-crd: 1.6.33 → 1.6.37 (chart/files/component-pins.yaml). Four frontend releases were tagged and published but never pinned here; this bump closes the divergence between git and the live cluster.

What the four frontend releases ship

1.6.34 — fixes two composer defects: a container locked to the first widget dropped into it (silently refusing subsequent drops), and a deleted widget that persisted in the draft and was emitted in the change request despite the author having removed it.

1.6.35 — the Files tab shows the live draft and edits are undoable. Widget kind metadata is now derived from the CRDs at build time (compiled into widgetKinds.generated.ts) rather than read at runtime, reducing coupling.

1.6.36 — closes the composer review and replaces the portal chart's hardcoded seven-kind page-composable RESTAction with a dynamic GET /list?category=widgets&ns= call to snowplow. Per-user RBAC governs what appears in the widget palette.

1.6.37 — bind live data to any kind that accepts a list.

Notes

Do not deploy 1.6.34 in isolation. Remove is a confirmed irreversible delete at that tag; undo does not arrive until 1.6.35. Stopping there is worse than either end of the range.

The frontend image now carries a frozen copy of the CRDs it was built against. This is currently free because helm/frontend-crds/templates/ is byte-identical across all five tags. When those CRD templates change, frontend and frontend-crd must roll as a pair: a kind present on the cluster but absent from the baked table disappears from the palette silently, with no error.

The unit test suite (1891 tests) now runs on every PR but is not yet a required check — it is advisory.