mirror of
https://github.com/twentyhq/twenty.git
synced 2026-09-17 00:22:48 -04:00
Raphaël Bosi
8997a6d864
Changes confined to `packages/twenty-ui/**` could skip consumer CI, allowing sandbox regressions to reach main. Add that path to the renderer, SDK, and website workflows, which directly depend on the workspace UI package. Frontend and UI CI already cover the path. The Base UI 1.8 upgrade in #25615 introduced an `Element.matches(':disabled')` call that the renderer sandbox does not support ([CI failure](https://github.com/twentyhq/twenty/actions/runs/34342034359/job/102435795459?pr=25655)). Temporarily use the existing known-failure gallery checks with separate expectations for each runtime: React must fail exactly `CardPicker`, `Radio`, and `RadioGroup`; Preact must fail only `CardPicker`, while its radio controls render successfully. Unexpected failures and partial or complete fixes still fail the assertions, prompting an expectation update when sandbox support lands. Validation: - Checked eight workflow filters against UI source, stylesheet, and package-manifest changes, plus an unrelated documentation change. Renderer, SDK, and website filters match UI changes; email, server, create-app, and both example-app workflows keep their existing filters. The five reverted workflow files match the base branch exactly. - Actionlint reports no new diagnostics; existing local-action metadata errors remain. Two workflows also have pre-existing Prettier failures. The story formatting and `git diff --check` pass. - Replayed the current React and Preact input story tests in Chromium against the saved CI Storybook build. The original Preact expectation reproduces the linked CI failure; both stories pass with the runtime-specific expectations. Confirmed that Preact renders all three radio controls and that failure reports remain stable after waiting. Changed-story lint and formatting pass. The full suite was not rerun locally.