From c28a410f9d3f3e1b6ea667a6c63bbfbf5519d245 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
<41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 27 Aug 2026 14:03:11 +0000
Subject: [PATCH] chore: release
---
.changeset/scheme-not-schema.md | 20 --------------------
CHANGELOG.md | 21 +++++++++++++++++++++
package.json | 2 +-
3 files changed, 22 insertions(+), 21 deletions(-)
delete mode 100644 .changeset/scheme-not-schema.md
diff --git a/.changeset/scheme-not-schema.md b/.changeset/scheme-not-schema.md
deleted file mode 100644
index caa577f5e..000000000
--- a/.changeset/scheme-not-schema.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-'@cube-dev/ui-kit': minor
----
-
-**Breaking:** reverted the `schema` term back to `scheme`, and renamed the `` attribute to match. `schema` was the wrong word — the platform calls this a color _scheme_ (`prefers-color-scheme`, the `color-scheme` property, ``), and in Cube's own vocabulary "schema" means the data model, so a `useSchema()` that returns `'light' | 'dark'` sits next to Cloud's `useSchema()` for SQL Runner as a pure homonym. This undoes the rename shipped in 0.170.0 ([#1362](https://github.com/cube-js/cube-ui-kit/pull/1362)) and fixes the older misspelling it was propagating.
-
-The API, back to `scheme`:
-
-- `renderColorTokens()` / `renderPaletteTokens()` / `RenderPaletteOptions`: the `schema` option is `scheme` again — `renderColorTokens({ scheme: 'dark' })`.
-- `` / ``: the `schema` prop is `scheme` again.
-- `useSchema()`, `resolveSchema()`, `subscribeSchema()` and `ColorSchema` — added in 0.170.0 — are now `useScheme()`, `resolveScheme()`, `subscribeScheme()` and `ColorScheme`. `useHighContrast()` and `resolveHighContrast()` are unchanged.
-- The probe's `tokenOptions.schema` is `tokenOptions.scheme` again, and the `pnpm probe` CLI flag `--schema` is `--scheme` (`--scheme hc` still means light + high contrast).
-
-The DOM opt-in, renamed for the first time:
-
-- `` is now ``, and the tasty state is `@root(scheme=…)` — so `@dark` compiles to `:root[data-scheme="dark"]`. `data-contrast` is unchanged.
-
-No aliases, on either half. An alias for the attribute was measured and rejected: teaching the `@dark` state to accept both spellings takes a four-variant palette style map from 21 rules / 3.6 KB to 52 rules / 10.3 KB, because every arm has to be expanded against both attributes — a permanent 2.9× on the kit's most-used state to save a one-line edit. An app that wants a transition window can write both attributes itself; the kit reads only `data-scheme`.
-
-To migrate, rename the option, the prop, the four hooks and the attribute at your call sites. Apps that set the attribute from JS need the one write updated (`document.documentElement.setAttribute('data-scheme', …)`), and any hand-written CSS selecting `[data-schema]` needs the same rename.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 632931ec3..de7b611a4 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,26 @@
# @cube-dev/ui-kit
+## 0.172.0
+
+### Minor Changes
+
+- [#1372](https://github.com/cube-js/cube-ui-kit/pull/1372) [`7f1f7227`](https://github.com/cube-js/cube-ui-kit/commit/7f1f722749ac0cdc154d2c1abe70a6ee40c11022) Thanks [@tenphi](https://github.com/tenphi)! - **Breaking:** reverted the `schema` term back to `scheme`, and renamed the `` attribute to match. `schema` was the wrong word — the platform calls this a color _scheme_ (`prefers-color-scheme`, the `color-scheme` property, ``), and in Cube's own vocabulary "schema" means the data model, so a `useSchema()` that returns `'light' | 'dark'` sits next to Cloud's `useSchema()` for SQL Runner as a pure homonym. This undoes the rename shipped in 0.170.0 ([#1362](https://github.com/cube-js/cube-ui-kit/pull/1362)) and fixes the older misspelling it was propagating.
+
+ The API, back to `scheme`:
+
+ - `renderColorTokens()` / `renderPaletteTokens()` / `RenderPaletteOptions`: the `schema` option is `scheme` again — `renderColorTokens({ scheme: 'dark' })`.
+ - `` / ``: the `schema` prop is `scheme` again.
+ - `useSchema()`, `resolveSchema()`, `subscribeSchema()` and `ColorSchema` — added in 0.170.0 — are now `useScheme()`, `resolveScheme()`, `subscribeScheme()` and `ColorScheme`. `useHighContrast()` and `resolveHighContrast()` are unchanged.
+ - The probe's `tokenOptions.schema` is `tokenOptions.scheme` again, and the `pnpm probe` CLI flag `--schema` is `--scheme` (`--scheme hc` still means light + high contrast).
+
+ The DOM opt-in, renamed for the first time:
+
+ - `` is now ``, and the tasty state is `@root(scheme=…)` — so `@dark` compiles to `:root[data-scheme="dark"]`. `data-contrast` is unchanged.
+
+ No aliases, on either half. An alias for the attribute was measured and rejected: teaching the `@dark` state to accept both spellings takes a four-variant palette style map from 21 rules / 3.6 KB to 52 rules / 10.3 KB, because every arm has to be expanded against both attributes — a permanent 2.9× on the kit's most-used state to save a one-line edit. An app that wants a transition window can write both attributes itself; the kit reads only `data-scheme`.
+
+ To migrate, rename the option, the prop, the four hooks and the attribute at your call sites. Apps that set the attribute from JS need the one write updated (`document.documentElement.setAttribute('data-scheme', …)`), and any hand-written CSS selecting `[data-schema]` needs the same rename.
+
## 0.171.0
### Minor Changes
diff --git a/package.json b/package.json
index 34a67b451..f2bc0a2db 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
{
"name": "@cube-dev/ui-kit",
- "version": "0.171.0",
+ "version": "0.172.0",
"type": "module",
"description": "UIKit for Cube Projects",
"repository": {