Skip to content

The open alternative to Salesforce, designed for AI.

fix: republish twenty-ui as MIT (1.0.0-alpha.2) to resolve stale AGPL artifacts (#25738)

Dhananjay Maurya5e7cbb4a4606
diff --git a/packages/create-twenty-app/src/constants/template/package.json b/packages/create-twenty-app/src/constants/template/package.json
index 9d4ae159191..e56d6598ac9 100644
--- a/packages/create-twenty-app/src/constants/template/package.json
+++ b/packages/create-twenty-app/src/constants/template/package.json
@@ -28,7 +28,7 @@
"react-dom": "^19.0.0",
"twenty-client-sdk": "TO-BE-GENERATED",
"twenty-sdk": "TO-BE-GENERATED",
- "twenty-ui": "1.0.0-alpha.1",
+ "twenty-ui": "1.0.0-alpha.2",
"typescript": "^5.9.3",
"vite-tsconfig-paths": "^4.2.1",
"vitest": "^4.0.0"
diff --git a/packages/twenty-codex-plugin/references/concepts/how-apps-work.md b/packages/twenty-codex-plugin/references/concepts/how-apps-work.md
index a3333b9d6a5..4646f120054 100644
--- a/packages/twenty-codex-plugin/references/concepts/how-apps-work.md
+++ b/packages/twenty-codex-plugin/references/concepts/how-apps-work.md
@@ -21,7 +21,7 @@ A Twenty app depends on two SDK packages:
`twenty-sdk/front-component` provides runtime APIs available inside front components: `navigate`, `enqueueSnackbar`, `openSidePanelPage`, `useSelectedRecordIds`, `getApplicationVariable`, and others.
-Twenty UI components (`Button`, `Chip`, `Tag`, `Status`, `H2Title`, `ThemeProvider`, icons, `themeCssVariables`) live in the `twenty-ui` package. Install `[email protected]` from npm and import from its subpaths (`twenty-ui/input`, `twenty-ui/data-display`, `twenty-ui/icon`, `twenty-ui/typography`, `twenty-ui/theme-constants`, and others).
+Twenty UI components (`Button`, `Chip`, `Tag`, `Status`, `H2Title`, `ThemeProvider`, icons, `themeCssVariables`) live in the `twenty-ui` package. Install `[email protected]` from npm and import from its subpaths (`twenty-ui/input`, `twenty-ui/data-display`, `twenty-ui/icon`, `twenty-ui/typography`, `twenty-ui/theme-constants`, and others).
`twenty-client-sdk/core` provides `CoreApiClient` for querying and mutating workspace records (companies, people, custom objects). `twenty-client-sdk/metadata` provides access to workspace metadata (object definitions, field definitions).
diff --git a/packages/twenty-codex-plugin/references/develop-app/front-components.md b/packages/twenty-codex-plugin/references/develop-app/front-components.md
index 30caaf9e97f..10406383c37 100644
--- a/packages/twenty-codex-plugin/references/develop-app/front-components.md
+++ b/packages/twenty-codex-plugin/references/develop-app/front-components.md
@@ -33,7 +33,7 @@ Keep imports narrow:
- Use `twenty-sdk/front-component` for front component hooks and host APIs.
- Use `twenty-client-sdk/core` or `twenty-client-sdk/metadata` for data access.
-- Install `[email protected]` from npm and import Twenty UI components, icons, and theme tokens from its subpaths (`twenty-ui/input`, `twenty-ui/data-display`, `twenty-ui/icon`, `twenty-ui/typography`, `twenty-ui/theme-constants`, and others) before adding external UI libraries.
+- Install `[email protected]` from npm and import Twenty UI components, icons, and theme tokens from its subpaths (`twenty-ui/input`, `twenty-ui/data-display`, `twenty-ui/icon`, `twenty-ui/typography`, `twenty-ui/theme-constants`, and others) before adding external UI libraries.
The front component renderer provides a Twenty `ThemeProvider` around the remote root. For isolated examples or local story-style verification, wrapping the component in `ThemeProvider` from `twenty-ui/theme-constants` is also acceptable.
diff --git a/packages/twenty-codex-plugin/scripts/validators/cross-doc-contracts.js b/packages/twenty-codex-plugin/scripts/validators/cross-doc-contracts.js
index 47c540a829d..b10c3312956 100644
--- a/packages/twenty-codex-plugin/scripts/validators/cross-doc-contracts.js
+++ b/packages/twenty-codex-plugin/scripts/validators/cross-doc-contracts.js
@@ -82,7 +82,7 @@ const assertFrontComponentGuidance = (fail) => {
'defineFrontComponent',
'Use `twenty-sdk/front-component`',
'Use `twenty-client-sdk/core` or `twenty-client-sdk/metadata`',
'import Twenty UI components, icons, and theme tokens from its subpaths',
'ThemeProvider',
'showcase/twenty-ui-example.front-component.tsx',
diff --git a/packages/twenty-docs/developers/extend/apps/getting-started/project-structure.mdx b/packages/twenty-docs/developers/extend/apps/getting-started/project-structure.mdx
index 681169670cd..86b5bf16fd3 100644
--- a/packages/twenty-docs/developers/extend/apps/getting-started/project-structure.mdx
+++ b/packages/twenty-docs/developers/extend/apps/getting-started/project-structure.mdx
@@ -67,7 +67,7 @@ Both Twenty SDK packages belong under `devDependencies`, not `dependencies`:
"devDependencies": {
"twenty-client-sdk": "2.20.0",
"twenty-sdk": "2.20.0",
- "twenty-ui": "1.0.0-alpha.1"
+ "twenty-ui": "1.0.0-alpha.2"
}
}
```
diff --git a/packages/twenty-docs/developers/extend/apps/layout/front-components.mdx b/packages/twenty-docs/developers/extend/apps/layout/front-components.mdx
index 69d6bed5163..315742c9a3d 100644
--- a/packages/twenty-docs/developers/extend/apps/layout/front-components.mdx
+++ b/packages/twenty-docs/developers/extend/apps/layout/front-components.mdx
@@ -690,14 +690,14 @@ Front components support multiple styling approaches. You can use:
## Using Twenty UI components
-Twenty ships its component library as the [`twenty-ui`](https://www.npmjs.com/package/twenty-ui/v/1.0.0-alpha.1) package. Front components can use it for buttons, tags, status pills, chips, avatars, icons, typography, and theme tokens that automatically match the workspace's light and dark theme.
+Twenty ships its component library as the [`twenty-ui`](https://www.npmjs.com/package/twenty-ui/v/1.0.0-alpha.2) package. Front components can use it for buttons, tags, status pills, chips, avatars, icons, typography, and theme tokens that automatically match the workspace's light and dark theme.
### Installation
Add the package to your app, pinned to the version your Twenty instance ships:
```bash
```
`twenty-ui` is bundled into your front component at build time, so it only needs to be a dependency of your app — there is nothing to configure at runtime.
diff --git a/packages/twenty-ui/package.json b/packages/twenty-ui/package.json
index 5b0d12971ba..a58723e3b75 100644
--- a/packages/twenty-ui/package.json
+++ b/packages/twenty-ui/package.json
@@ -1,6 +1,6 @@
{
"name": "twenty-ui",
- "version": "1.0.0-alpha.1",
+ "version": "1.0.0-alpha.2",
"description": "Twenty's shared React UI component library.",
"license": "MIT",
"repository": {
@@ -88,6 +88,7 @@
},
"files": [
"dist",
+ "LICENSE",
"!dist/individual",
"!dist/individual/**",
"!dist/**/*.map"