[pull] master from cube-js:master

CHANGELOG.md

@@ -3,6 +3,16 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [1.6.42](https://github.com/cube-js/cube/compare/v1.6.41...v1.6.42) (2026-05-01)
+
+### Bug Fixes
+
+- **client-core:** make CJS consumers work for main entry and /format subpath ([#10796](https://github.com/cube-js/cube/issues/10796)) ([1b40ddc](https://github.com/cube-js/cube/commit/1b40ddcbc84f67c0c2d35d130dd715a19a5e72d8)), closes [#5917](https://github.com/cube-js/cube/issues/5917) [#9562](https://github.com/cube-js/cube/issues/9562)
+
+### Features
+
+- **client-core:** extend numeric formatting options with precision a… ([#10800](https://github.com/cube-js/cube/issues/10800)) ([dd50d32](https://github.com/cube-js/cube/commit/dd50d32af37fc8d4610618e50f449f080a2c4a11))
+
 ## [1.6.41](https://github.com/cube-js/cube/compare/v1.6.40...v1.6.41) (2026-05-01)
 
 ### Bug Fixes

docs-mintlify/admin/customization/chart-palettes.mdx

@@ -0,0 +1,66 @@
+---
+title: Chart palettes
+description: Create custom color palettes so charts across your account stay consistent and on-brand.
+---
+
+Chart palettes control the colors used in chart visualizations across [workbooks][ref-workbooks] and [dashboards][ref-dashboards]. Cube ships with a set of built-in palettes, and you can also define your own custom palettes — for example, to match your company brand — and reuse them on any chart in the account.
+
+Custom palettes are managed centrally and are available across every deployment in the account.
+
+[ref-workbooks]: /workbooks
+[ref-dashboards]: /workbooks/dashboards
+
+## Requirements
+
+Custom chart palettes are managed under the **Manage chart palettes** permission. The built-in **Admin** [role][ref-roles] has this permission by default; for other users, grant the **Manage chart palettes** global permission via a [custom role][ref-custom-roles].
+
+[ref-roles]: /admin/users-and-permissions/roles-and-permissions
+[ref-custom-roles]: /admin/users-and-permissions/custom-roles
+
+## Browse palettes
+
+Go to **Admin → Customization → Chart Palettes** to see every palette available in your account. The list combines:
+
+- **Built-in palettes** shipped with Cube — these can be used in charts but cannot be edited or deleted.
+- **Custom palettes** created in your account — these can be edited, renamed, and deleted.
+
+Each row shows the palette name and a preview of its colors.
+
+## Create a custom palette
+
+1. Go to **Admin → Customization → Chart Palettes**.
+2. Click **Add palette**.
+3. Give the palette a **Name** and provide its colors as a comma-separated list of hex codes (for example, `#1F77B4, #FF7F0E, #2CA02C`).
+4. Click **Save**.
+
+The new palette appears in the list immediately and becomes selectable in the chart styling controls.
+
+## Edit a custom palette
+
+1. Go to **Admin → Customization → Chart Palettes**.
+2. Click the row action on the palette you want to change and select **Edit**.
+3. Update the name or colors and click **Save**.
+
+Existing charts that use the palette pick up the new colors automatically.
+
+## Delete a custom palette
+
+1. Go to **Admin → Customization → Chart Palettes**.
+2. Click the row action on the palette you want to remove and select **Delete**.
+
+Charts that were using the deleted palette fall back to the built-in **Default** palette.
+
+## Apply a palette to a chart
+
+Palettes are applied per chart from the chart's styling controls:
+
+1. Open a workbook and select a chart.
+2. Open the **Style** panel for the chart.
+3. Use the **Palette** dropdown to pick a built-in or custom palette.
+
+The dropdown shows palettes that match the chart's color encoding:
+
+- **Discrete** palettes appear when the color encoding is categorical (for example, color by `status` or `category`).
+- **Continuous** palettes appear when the color encoding is quantitative or temporal (for example, color by `total_sale_price` or `created_at`).
+
+If no palette is explicitly selected, charts use the built-in **Default** palette.

docs-mintlify/admin/customization/dashboard-themes.mdx

@@ -0,0 +1,97 @@
+---
+title: Dashboard themes
+description: Style dashboards with reusable themes that control backgrounds, widget cards, borders, titles, and text.
+---
+
+Dashboard themes control the look and feel of [dashboards][ref-dashboards] — including the dashboard background, widget cards, borders, titles, and text. Cube ships with a built-in theme, and you can also create your own custom themes and reuse them across dashboards in the account.
+
+Themes are designed and saved from the dashboard builder, then managed centrally in the admin area.
+
+[ref-dashboards]: /workbooks/dashboards
+
+## Requirements
+
+Custom dashboard themes are managed under the **Manage dashboard themes** permission. The built-in **Admin** [role][ref-roles] has this permission by default; for other users, grant the **Manage dashboard themes** global permission via a [custom role][ref-custom-roles].
+
+[ref-roles]: /admin/users-and-permissions/roles-and-permissions
+[ref-custom-roles]: /admin/users-and-permissions/custom-roles
+
+## What you can theme
+
+A theme defines styles for the following parts of a dashboard:
+
+| Section        | Properties                                                |
+| -------------- | --------------------------------------------------------- |
+| **Dashboard**  | Background color, padding                                 |
+| **Widgets**    | Card background color, padding                            |
+| **Borders**    | Color, width, style, corner radius                        |
+| **Titles**     | Color, font size, font weight, font family                |
+| **Text**       | Color, secondary color, font family, code font family     |
+
+The built-in **Cube** theme provides Cube's default look and is always available. It can be selected on dashboards but cannot be edited, renamed, or deleted.
+
+## Browse themes
+
+Go to **Admin → Customization → Dashboard Themes** to see every theme available in your account. The list combines the built-in **Cube** theme and any custom themes saved from dashboards.
+
+For each custom theme you can:
+
+- **Rename** the theme.
+- **Delete** the theme.
+
+Themes are created from the dashboard builder rather than from this page — see [Create a custom theme](#create-a-custom-theme) below.
+
+## Create a custom theme
+
+Custom themes are saved from the dashboard builder's **Styling** tab.
+
+<Steps>
+  <Step title="Open a dashboard">
+    Open a dashboard in a workbook and switch to the dashboard builder.
+  </Step>
+  <Step title="Open dashboard options">
+    Click the dashboard options button and switch to the **Styling** tab.
+  </Step>
+  <Step title="Edit styling">
+    Adjust the dashboard background, widget card styles, borders, titles, and text until the dashboard looks the way you want.
+  </Step>
+  <Step title="Save as new theme">
+    Click **Save as new**, give the theme a name, and confirm.
+  </Step>
+</Steps>
+
+The new theme appears in the **Admin → Customization → Dashboard Themes** list and becomes selectable in the **Styling** tab on every other dashboard in the account.
+
+## Apply a theme to a dashboard
+
+1. Open the dashboard in the dashboard builder.
+2. Open dashboard options and switch to the **Styling** tab.
+3. Pick a theme from the theme picker.
+
+You can also tweak any styling properties on top of the selected theme — those changes are stored as overrides on the dashboard and do not modify the underlying theme.
+
+## Update a saved theme
+
+After tweaking styling on a dashboard that uses a custom theme, you can push those changes back into the theme so every other dashboard using it picks them up.
+
+1. From the dashboard's **Styling** tab, make your changes.
+2. Click **Save** to write the current effective styles back into the theme.
+
+<Warning>
+
+Saving a theme updates **every dashboard** that uses it. Already-published dashboard snapshots keep their previous styling until they are re-published.
+
+</Warning>
+
+## Delete a custom theme
+
+1. Go to **Admin → Customization → Dashboard Themes**.
+2. Click the row action on the theme you want to remove and select **Delete**.
+
+Dashboards that were using the deleted theme revert to the built-in **Cube** theme.
+
+## Theme scope
+
+- **Themes** are defined once and shared across all deployments in the account.
+- **Theme assignment** is per dashboard — different dashboards in the same workbook can use different themes.
+- New dashboards use the built-in **Cube** theme until you assign a custom theme.

docs-mintlify/admin/sso/google-workspace.mdx

@@ -106,15 +106,53 @@ SAML integration in Google into Cube Cloud.
 
 3. Enable **Auto-provision new users** if you want users to be automatically
    created in Cube on their first login via this SAML provider. New users
-   are assigned the Viewer role by default. Enable this if you are not using
-   SCIM provisioning.
+   are assigned the Viewer role by default — see
+   [Default role for new users](#default-role-for-new-users) to choose a
+   different role. Enable this if you are not using SCIM provisioning.
 
 4. Scroll down and click **Save SAML Settings** to save the changes.
 
+## Default role for new users
+
+By default, users auto-provisioned via SAML receive the **Viewer** role.
+To assign a different role, expand the **Advanced** section of the SAML
+configuration form and pick from **Default role for new users**:
+
+- **Developer**, **Explorer**, or **Viewer** — Cube Cloud's [default
+  roles][ref-roles].
+- Any [custom role][ref-custom-roles] defined in your account, listed
+  below the divider.
+
+The selected role applies **only when a user is first created**. Existing
+users are not modified on subsequent SSO logins. It is applied **in
+addition to** any roles your identity provider sends via the role
+attribute (subject to the `rolesMap`).
+
+<Info>
+
+Admin status is not assignable through this picker — Admin is controlled
+separately. To grant admin permissions, update the user's role manually
+under [Admin → Users][ref-manage-users].
+
+</Info>
+
+<Warning>
+
+If the selected role is later renamed or deleted, new users will fall
+back to the **Viewer** role until you pick a valid role here. The Viewer
+fallback applies whenever the configured default cannot be resolved —
+whether that's because no default is set or the configured role no longer
+exists.
+
+</Warning>
+
 ## Test SAML authentication
 
 To start using SAML authentication, use the
 [single sign-on URL provided by Cube Cloud](#enable-saml-in-cube-cloud)
 (typically `<YOUR_CUBE_CLOUD_URL>/sso/saml`) to log in to Cube Cloud.
 
 [google-docs-create-saml-app]: https://support.google.com/a/answer/6087519?hl=en
+[ref-roles]: /admin/users-and-permissions/roles-and-permissions
+[ref-custom-roles]: /admin/users-and-permissions/custom-roles
+[ref-manage-users]: /admin/users-and-permissions/manage-users

docs-mintlify/admin/sso/microsoft-entra-id/saml.mdx

@@ -83,9 +83,47 @@ values from the Entra **Single sign-on** page:
 In both options, also configure the following setting:
 
 - **Auto-provision new users** — When enabled, users are automatically
-  created in Cube on their first login via this SAML provider and assigned
-  the Viewer role by default. Enable this if you want to provision users
-  only when they first access Cube and you are not using SCIM provisioning.
+  created in Cube on their first login via this SAML provider. Enable this
+  if you want to provision users only when they first access Cube and you
+  are not using SCIM provisioning. New users receive the Viewer role by
+  default; see [Default role for new users](#default-role-for-new-users)
+  to choose a different role.
+
+## Default role for new users
+
+Auto-provisioned users — both via SAML and via [SCIM][ref-scim] — receive
+the **Viewer** role by default. To assign a different role, expand the
+**Advanced** section of the SAML configuration form and pick from
+**Default role for new users**:
+
+- **Developer**, **Explorer**, or **Viewer** — Cube's [default
+  roles][ref-roles].
+- Any [custom role][ref-custom-roles] defined in your account, listed
+  below the divider.
+
+The selected role applies **only when a user is first created** during
+provisioning. Existing users are not modified on subsequent SSO logins or
+SCIM updates. It is applied **in addition to** any roles your identity
+provider sends via the [role attribute](#configure-attribute-mappings)
+(subject to the `rolesMap`).
+
+<Info>
+
+Admin status is not assignable through this picker — Admin is controlled
+separately. To grant admin permissions, update the user's role manually
+under [Admin → Users][ref-manage-users].
+
+</Info>
+
+<Warning>
+
+If the selected role is later renamed or deleted, new users will fall
+back to the **Viewer** role until you pick a valid role here. The Viewer
+fallback applies whenever the configured default cannot be resolved —
+whether that's because no default is set or the configured role no longer
+exists.
+
+</Warning>
 
 ## Configure attribute mappings
 
@@ -122,3 +160,7 @@ users or groups in Entra before testing.
    Entra for authentication and then back to Cube.
 
 [ext-ms-entra-id]: https://www.microsoft.com/en-us/security/business/identity-access/microsoft-entra-id
+[ref-scim]: /admin/sso/microsoft-entra-id/scim
+[ref-roles]: /admin/users-and-permissions/roles-and-permissions
+[ref-custom-roles]: /admin/users-and-permissions/custom-roles
+[ref-manage-users]: /admin/users-and-permissions/manage-users

docs-mintlify/admin/sso/microsoft-entra-id/scim.mdx

@@ -73,9 +73,14 @@ Cube:
 
 <Info>
 
-Users provisioned via SCIM will receive the Explorer role.
-To grant admin permissions, update the user's role manually in
-Cube under **Team & Security**.
+Users provisioned via SCIM receive the **Viewer** role by default. To
+choose a different default role (including [custom roles][ref-custom-roles]),
+see [Default role for new users][ref-saml-default-role] on the SAML setup
+page — the setting is shared between SAML and SCIM.
+
+Admin permissions cannot be assigned through this setting. To grant admin
+permissions, update the user's role manually in Cube under **Admin →
+Users**.
 
 </Info>
 
@@ -120,4 +125,6 @@ The next time the Entra application syncs, the attribute values will be
 provisioned as [user attributes][ref-user-attributes] in Cube.
 
 [ref-saml]: /admin/sso/microsoft-entra-id/saml
+[ref-saml-default-role]: /admin/sso/microsoft-entra-id/saml#default-role-for-new-users
+[ref-custom-roles]: /admin/users-and-permissions/custom-roles
 [ref-user-attributes]: /admin/users-and-permissions/user-attributes

docs-mintlify/admin/sso/okta/saml.mdx

@@ -85,9 +85,46 @@ identity provider details:
   Sign-On URL** value from Okta.
 - **Certificate** — Paste the **X.509 Certificate** from Okta.
 - **Auto-provision new users** — When enabled, users are automatically
-  created in Cube on their first login via this SAML provider and assigned
-  the Viewer role by default. Enable this if you want to provision users
-  only when they first access Cube and you are not using SCIM provisioning.
+  created in Cube on their first login via this SAML provider. Enable this
+  if you want to provision users only when they first access Cube and you
+  are not using SCIM provisioning. New users receive the Viewer role by
+  default; see [Default role for new users](#default-role-for-new-users)
+  to choose a different role.
+
+## Default role for new users
+
+Auto-provisioned users — both via SAML and via [SCIM][ref-scim] — receive
+the **Viewer** role by default. To assign a different role, expand the
+**Advanced** section of the SAML configuration form and pick from
+**Default role for new users**:
+
+- **Developer**, **Explorer**, or **Viewer** — Cube's [default
+  roles][ref-roles].
+- Any [custom role][ref-custom-roles] defined in your account, listed
+  below the divider.
+
+The selected role applies **only when a user is first created** during
+provisioning. Existing users are not modified on subsequent SSO logins or
+SCIM updates. It is applied **in addition to** any roles your identity
+provider sends via the role attribute (subject to the `rolesMap`).
+
+<Info>
+
+Admin status is not assignable through this picker — Admin is controlled
+separately. To grant admin permissions, update the user's role manually
+under [Admin → Users][ref-manage-users].
+
+</Info>
+
+<Warning>
+
+If the selected role is later renamed or deleted, new users will fall
+back to the **Viewer** role until you pick a valid role here. The Viewer
+fallback applies whenever the configured default cannot be resolved —
+whether that's because no default is set or the configured role no longer
+exists.
+
+</Warning>
 
 ## Test SAML authentication
 
@@ -100,3 +137,7 @@ identity provider details:
 
 [okta-docs-create-saml-app]:
   https://help.okta.com/en-us/Content/Topics/Apps/Apps_App_Integration_Wizard_SAML.htm
+[ref-scim]: /admin/sso/okta/scim
+[ref-roles]: /admin/users-and-permissions/roles-and-permissions
+[ref-custom-roles]: /admin/users-and-permissions/custom-roles
+[ref-manage-users]: /admin/users-and-permissions/manage-users