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.
The #1 Open-Source CRM
Website · 
Documentation · 
Roadmap · 
Discord · 
Figma
Why Twenty
Twenty gives technical teams the building blocks for a custom CRM that meets complex business needs and quickly adapts as the business evolves. Twenty is the CRM you build, ship, and version like the rest of your stack.
Learn more about why we built Twenty
Installation
Cloud
The fastest way to get started. Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date.
Build an app
Scaffold a new app with the Twenty CLI:
npx create-twenty-app my-app
Define objects, fields, and views as code:
import { defineObject, FieldType } from 'twenty-sdk/define';
export default defineObject({
nameSingular: 'deal',
namePlural: 'deals',
labelSingular: 'Deal',
labelPlural: 'Deals',
fields: [
{ name: 'name', label: 'Name', type: FieldType.TEXT },
{ name: 'amount', label: 'Amount', type: FieldType.CURRENCY },
{ name: 'closeDate', label: 'Close Date', type: FieldType.DATE_TIME },
],
});
Then ship it to your workspace:
npx twenty app:publish --private
See the app development guide for objects, views, agents, and logic functions.
Self-hosting
Run Twenty on your own infrastructure with Docker Compose, or contribute locally via the local setup guide.
Everything you need
Twenty gives you the building blocks of a modern CRM (objects, views, workflows, and agents) and lets you extend them as code. Here's a tour of what's in the box.
Want to go deeper? Read the 
User Guide for product walkthroughs, or the Documentation for developer reference.
|
|
|
|
|
|
Learn more about version control in docStack
TypeScript
Nx
NestJS, with BullMQ, 
PostgreSQL, 
Redis
React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
Star the repo · Discord · 
Feature requests · Releases · 
X · 
LinkedIn · 
Crowdin · 
Contribute