From 5eb34a48a32adfde77f4da29dd4dd24459277f70 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 30 Oct 2026 14:33:44 +0000 Subject: [PATCH] Version Packages --- .changeset/hyperbook-tokens-first.md | 5 ----- .changeset/studio-workbench-typography.md | 5 ----- packages/bitflow-core/CHANGELOG.md | 6 ++++++ packages/bitflow-core/package.json | 2 +- platforms/vscode/CHANGELOG.md | 19 +++++++++++++++++++ platforms/vscode/package.json | 2 +- 6 files changed, 27 insertions(+), 12 deletions(-) delete mode 100644 .changeset/hyperbook-tokens-first.md delete mode 100644 .changeset/studio-workbench-typography.md diff --git a/.changeset/hyperbook-tokens-first.md b/.changeset/hyperbook-tokens-first.md deleted file mode 100644 index 8b0adbda..00000000 --- a/.changeset/hyperbook-tokens-first.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@bitflow/core": minor ---- - -bitflow now reads four of Hyperbook's design tokens where the host declares them — `--color-brand`, `--color-background`, `--color-text`, `--color-text-deactivated` — with bitflow's own palette as the fallback. A flow on a Hyperbook page (and the editor in a frame of Hyperbook Cloud) follows the book's brand, background and text in both themes without a mapping stylesheet, the way learningmap does. A host that declares the bitflow tokens itself still wins outright; and a Hyperbook still owes the container a `color-scheme`, without which the `light-dark()` feedback colours stay light in a dark book. diff --git a/.changeset/studio-workbench-typography.md b/.changeset/studio-workbench-typography.md deleted file mode 100644 index bb766837..00000000 --- a/.changeset/studio-workbench-typography.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"bitflow-studio": patch ---- - -Bitflow Studio takes its fonts and colour scheme from the workbench. A webview is its own document, so nothing of VS Code's typography reached the editor by inheritance: the canvas sat in the browser default serif and stayed light in a dark workbench. The editor now reads `--vscode-font-family` and `--vscode-editor-font-family`, and a dark workbench sets `color-scheme: dark`, which is what the `light-dark()` theme resolves against. diff --git a/packages/bitflow-core/CHANGELOG.md b/packages/bitflow-core/CHANGELOG.md index 569c6bef..7c11932e 100644 --- a/packages/bitflow-core/CHANGELOG.md +++ b/packages/bitflow-core/CHANGELOG.md @@ -1,5 +1,11 @@ # @bitflow/core +## 0.9.0 + +### Minor Changes + +- [`d6dce81`](https://github.com/openpatch/bitflow/commit/d6dce81cebd4050ec5c009b678857f40741d9b55) Thanks [@mikebarkmin](https://github.com/mikebarkmin)! - bitflow now reads four of Hyperbook's design tokens where the host declares them — `--color-brand`, `--color-background`, `--color-text`, `--color-text-deactivated` — with bitflow's own palette as the fallback. A flow on a Hyperbook page (and the editor in a frame of Hyperbook Cloud) follows the book's brand, background and text in both themes without a mapping stylesheet, the way learningmap does. A host that declares the bitflow tokens itself still wins outright; and a Hyperbook still owes the container a `color-scheme`, without which the `light-dark()` feedback colours stay light in a dark book. + ## 0.8.0 ### Minor Changes diff --git a/packages/bitflow-core/package.json b/packages/bitflow-core/package.json index 4fd3b364..e090bdad 100644 --- a/packages/bitflow-core/package.json +++ b/packages/bitflow-core/package.json @@ -1,6 +1,6 @@ { "name": "@bitflow/core", - "version": "0.8.0", + "version": "0.9.0", "author": "Mike Barkmin", "description": "Schema, flow engine, attempt runtime and bit registry for bitflow. Pure TypeScript, no UI.", "homepage": "https://github.com/openpatch/bitflow#readme", diff --git a/platforms/vscode/CHANGELOG.md b/platforms/vscode/CHANGELOG.md index 8191c70c..58ca821f 100644 --- a/platforms/vscode/CHANGELOG.md +++ b/platforms/vscode/CHANGELOG.md @@ -1,5 +1,24 @@ # bitflow-studio +## 0.1.3 + +### Patch Changes + +- [`d6dce81`](https://github.com/openpatch/bitflow/commit/d6dce81cebd4050ec5c009b678857f40741d9b55) Thanks [@mikebarkmin](https://github.com/mikebarkmin)! - Bitflow Studio takes its fonts and colour scheme from the workbench. A webview is its own document, so nothing of VS Code's typography reached the editor by inheritance: the canvas sat in the browser default serif and stayed light in a dark workbench. The editor now reads `--vscode-font-family` and `--vscode-editor-font-family`, and a dark workbench sets `color-scheme: dark`, which is what the `light-dark()` theme resolves against. +- Updated dependencies [[`d6dce81`](https://github.com/openpatch/bitflow/commit/d6dce81cebd4050ec5c009b678857f40741d9b55)]: + - @bitflow/core@0.9.0 + - @bitflow/bitflow@0.0.0 + - @bitflow/element@0.0.0 + - @bitflow/end-tries@0.0.0 + - @bitflow/input-markdown@0.0.0 + - @bitflow/start-simple@0.0.0 + - @bitflow/task-choice@0.0.0 + - @bitflow/task-fill-in-the-blank@0.0.0 + - @bitflow/task-highlighting@0.0.0 + - @bitflow/task-input@0.0.0 + - @bitflow/task-yes-no@0.0.0 + - @bitflow/title-simple@0.0.0 + ## 0.1.2 ### Patch Changes diff --git a/platforms/vscode/package.json b/platforms/vscode/package.json index e7b54e7c..242f6db6 100644 --- a/platforms/vscode/package.json +++ b/platforms/vscode/package.json @@ -2,7 +2,7 @@ "name": "bitflow-studio", "displayName": "Bitflow Studio", "description": "Visual editor for .bitflow files \u2014 build and preview assessments", - "version": "0.1.2", + "version": "0.1.3", "publisher": "openpatch", "author": "Mike Barkmin", "license": "MIT",