@lightdash/cli 1.150.0 → 1.150.1

package/dist/vendor/template/references/themes.md

@@ -6,9 +6,11 @@ When `/app/src/design/` exists in the workspace, the organization has supplied b
 
 Directory layout (any subdirectory may be empty):
 
-- `/app/src/design/css/` — stylesheets. Inspect the style sheets and decide: If they are general colors and global styles **Import them** from your main entry point (`src/main.jsx`) before any of your own styles, so cascade order lets your CSS override theme defaults only where intentional. If they are component-specific (e.g. a `.fancy-button` class), **Reference them** in your JSX (`<button className="fancy-button">`) and use them as the basis for any custom components you build. You can build styles that typically match if the specific ones you are looking for are not there. 
-- `/app/src/design/fonts/` — web fonts. **Reference them via `@font-face` in your own CSS** and use the resulting `font-family` everywhere you'd otherwise pick a font. Do not link to external font CDNs (Google Fonts, Bunny, etc.) when fonts are present here.
-- `/app/src/design/images/` — logos and brand imagery. Import as ES modules (`import logo from './design/images/logo.png'`) so Vite hashes the URL. Use them in place of any generic logo/illustration you'd otherwise invent. Try to guess from the file names or context: is it a logo (use in the header), a pattern (use as a background), or a product screenshot (reference for UI details)? 
+<!-- Keep Apple system-font fallback values aligned with the canonical constants in packages/backend/src/services/OrganizationDesignService/restrictedAppleFonts.ts. -->
+
+- `/app/src/design/css/` — stylesheets. Inspect the style sheets and decide: If they are general colors and global styles **Import them** from your main entry point (`src/main.jsx`) before any of your own styles, so cascade order lets your CSS override theme defaults only where intentional. If they are component-specific (e.g. a `.fancy-button` class), **Reference them** in your JSX (`<button className="fancy-button">`) and use them as the basis for any custom components you build. You can build styles that typically match if the specific ones you are looking for are not there.
+- `/app/src/design/fonts/` — accepted web fonts. Reference files that are present via `@font-face` in your own CSS and use the resulting `font-family` consistently. Restricted Apple system-font files are omitted before generation; never recreate, download, or embed a missing SF-family or New York font. Preserve that appearance with a system stack instead: use `system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif` for SF Pro/Compact, `ui-monospace, "SFMono-Regular", Menlo, Monaco, Consolas, monospace` for SF Mono, or `ui-serif, Georgia, serif` for New York. Do not link to external font CDNs (Google Fonts, Bunny, etc.) when fonts are present here.
+- `/app/src/design/images/` — logos and brand imagery. Import as ES modules (`import logo from './design/images/logo.png'`) so Vite hashes the URL. Use them in place of any generic logo/illustration you'd otherwise invent. Try to guess from the file names or context: is it a logo (use in the header), a pattern (use as a background), or a product screenshot (reference for UI details)?
 
 **Images are IMPORTANT and frequently more telling than the CSS or instruction files** — they carry intent the other assets can't express. Decide how to use them in this order:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lightdash/cli",
-  "version": "1.150.0",
+  "version": "1.150.1",
   "description": "Lightdash CLI tool",
   "license": "MIT",
   "repository": {
@@ -42,8 +42,8 @@
     "unique-names-generator": "4.7.1",
     "uuid": "11.1.1",
     "yaml": "2.8.3",
-    "@lightdash/common": "1.150.0",
-    "@lightdash/warehouses": "1.150.0"
+    "@lightdash/common": "1.150.1",
+    "@lightdash/warehouses": "1.150.1"
   },
   "devDependencies": {
     "@types/inquirer": "8.2.4",