dsh-fonttune 0.3.1 → 0.3.2

package/CHANGELOG.en.md

@@ -2,6 +2,11 @@
 
 All notable changes to **dsh-fonttune** are documented here. Chinese version: [CHANGELOG.md](CHANGELOG.md).
 
+## [0.3.2] - 2026-09-28
+
+### Changed
+- **DSH 0.2.0-rc.1 is supported**: releases now also run on the 0.2 line, and the compatibility table names the host line each release needs.
+
 ## [0.3.1] - 2026-09-28
 
 ### Fixed

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 **dsh-fonttune** 的重要变更都记录在这里。英文版见 [CHANGELOG.en.md](CHANGELOG.en.md)。
 
+## [0.3.2] - 2026-09-28
+
+### 变更
+- **支持的 DSH 版本增加 0.2.0-rc.1**：这一版起在 0.2 线上同样可用；安装前可据兼容表判断某个版本需要哪条宿主线。
+
 ## [0.3.1] - 2026-09-28
 
 ### 修复

package/README.en.md

@@ -22,11 +22,12 @@
 
 ## Compatibility
 
-**One package serves three host lines** — 0.1.5-rc.3 (the floor), 0.1.7-alpha.1 / alpha.2 and 0.1.7-rc.1 / rc.2 — and the install is the same on any of them: all three were verified for "the settings card opens, the stylesheet really reaches the page, and a change made in the card is written through".
+**One package serves four host lines** — 0.1.5-rc.3 (the floor), 0.1.7-alpha.1 / alpha.2, 0.1.7-rc.1 / rc.2 and 0.2.0-rc.1 — and the install is the same on any of them: all three were verified for "the settings card opens, the stylesheet really reaches the page, and a change made in the card is written through".
 
 | Plugin version | Supported DSH versions |
 | --- | --- |
-| **0.3.1** (latest) | 0.1.5-rc.3, 0.1.7-alpha.1 / alpha.2, 0.1.7-rc.1 / rc.2 |
+| **0.3.2** (latest) | 0.1.5-rc.3, 0.1.7-alpha.1 / alpha.2, 0.1.7-rc.1 / rc.2, 0.2.0-rc.1 |
+| 0.3.1 | 0.1.5-rc.3, 0.1.7-alpha.1 / alpha.2, 0.1.7-rc.1 / rc.2 |
 | 0.3.0 | 0.1.5-rc.3, 0.1.7-alpha.1 / alpha.2, 0.1.7-rc.1 / rc.2 |
 | 0.2.7 | 0.1.5-rc.3, 0.1.7-alpha.1 / alpha.2, 0.1.7-rc.1 / rc.2 |
 | 0.2.6 | 0.1.5-rc.3, 0.1.7-alpha.1 / alpha.2, 0.1.7-rc.1 |
@@ -37,7 +38,7 @@
 | 0.2.1 | 0.1.5-rc.2 |
 | 0.2.0 | 0.1.5-rc.2 |
 
-`engines.dsh` is declared as **`>=0.1.5-rc.3 <0.1.7-0 || >=0.1.7-alpha.1 <0.2.0-0`** (a prerelease needs its own branch: node-semver admits one only when some comparator in the range sits on that version's exact `major.minor.patch` tuple and carries a prerelease tag of its own, so a plain `>=0.1.5-rc.3` never matches `0.1.7-alpha.1`). Every difference between the lines is settled at runtime rather than by version number:
+`engines.dsh` is declared as **`>=0.1.5-rc.3 <0.1.7-0 || >=0.1.7-alpha.1 <0.3.0-0`** (a prerelease needs its own branch: node-semver admits one only when some comparator in the range sits on that version's exact `major.minor.patch` tuple and carries a prerelease tag of its own, so a plain `>=0.1.5-rc.3` never matches `0.1.7-alpha.1`). Every difference between the lines is settled at runtime rather than by version number:
 
 - **The settings service**: up to 0.1.5-rc.x it is `settingsScope.bind({namespace})` (by namespace); 0.1.7-alpha.x and 0.1.7-rc.x use `configForms.get(<profile entry id>)` (by entry id, which the installing profile decides — so the plugin claims the form whose served schema names its own fields). Both expose the same `getSnapshot`/`subscribe`/`set`/`unset` face, so one implementation covers them.
 - **The loader row id IS the settings key**: from 0.1.7-rc.1 on, settings are stored per entry id, and the first start imports the removed `settings.yaml` by matching section names against it — so the row id this package ships equals its settings namespace (`dsh-fonttune`). That same id also lets the package be installed through the profile's `dsh.profile.bundles`: the plugin manager then shows it as running while the configuration page stays reachable.

package/README.md

@@ -22,11 +22,12 @@
 
 ## 兼容性
 
-**一份包同时支持三条宿主线**——0.1.5-rc.3（下限）、0.1.7-alpha.1 / alpha.2、0.1.7-rc.1 / rc.2：安装方式与宿主线无关，三条线都验证过「设置卡片可用、样式真的作用到页面、卡片上的改动写得进去」。
+**一份包同时支持四条宿主线**——0.1.5-rc.3（下限）、0.1.7-alpha.1 / alpha.2、0.1.7-rc.1 / rc.2、0.2.0-rc.1：安装方式与宿主线无关，三条线都验证过「设置卡片可用、样式真的作用到页面、卡片上的改动写得进去」。
 
 | 插件版本 | 支持的 DSH 版本 |
 | --- | --- |
-| **0.3.1**（最新） | 0.1.5-rc.3、0.1.7-alpha.1 / alpha.2、0.1.7-rc.1 / rc.2 |
+| **0.3.2**（最新） | 0.1.5-rc.3、0.1.7-alpha.1 / alpha.2、0.1.7-rc.1 / rc.2、0.2.0-rc.1 |
+| 0.3.1 | 0.1.5-rc.3、0.1.7-alpha.1 / alpha.2、0.1.7-rc.1 / rc.2 |
 | 0.3.0 | 0.1.5-rc.3、0.1.7-alpha.1 / alpha.2、0.1.7-rc.1 / rc.2 |
 | 0.2.7 | 0.1.5-rc.3、0.1.7-alpha.1 / alpha.2、0.1.7-rc.1 / rc.2 |
 | 0.2.6 | 0.1.5-rc.3、0.1.7-alpha.1 / alpha.2、0.1.7-rc.1 |
@@ -37,7 +38,7 @@
 | 0.2.1 | 0.1.5-rc.2 |
 | 0.2.0 | 0.1.5-rc.2 |
 
-`engines.dsh` 声明为 **`>=0.1.5-rc.3 <0.1.7-0 || >=0.1.7-alpha.1 <0.2.0-0`**（预发布版本必须显式留分支：node-semver 只在一个范围的某个比较符与该版本落在同一个 `major.minor.patch` 元组、且自身带预发布标签时才放行，写成 `>=0.1.5-rc.3` 匹配不到 `0.1.7-alpha.1`）。三条线的差别**全部在运行时二选一，不看版本号**：
+`engines.dsh` 声明为 **`>=0.1.5-rc.3 <0.1.7-0 || >=0.1.7-alpha.1 <0.3.0-0`**（预发布版本必须显式留分支：node-semver 只在一个范围的某个比较符与该版本落在同一个 `major.minor.patch` 元组、且自身带预发布标签时才放行，写成 `>=0.1.5-rc.3` 匹配不到 `0.1.7-alpha.1`）。三条线的差别**全部在运行时二选一，不看版本号**：
 
 - **设置服务**：0.1.5-rc.x 是 `settingsScope.bind({namespace})`（按命名空间）；0.1.7-alpha.x 与 0.1.7-rc.x 换成了 `configForms.get(<profile 条目 id>)`（按条目 id，id 由安装方的 profile 决定，所以插件靠「宿主服务的那份 schema 里有没有本插件自己的字段」来认领）。两者都是 `getSnapshot/subscribe/set/unset` 同一张脸，插件只写一套。
 - **loader 行 id 就是设置键**：0.1.7-rc.1 起设置按入口 id 存档，首次启动还会按**同名**把旧的 `settings.yaml` 搬过去——本包自带的 loader 行 id 因此与设置命名空间一致（`dsh-fonttune`）。同名的行 id 也让这个包可以写进 profile 的 `dsh.profile.bundles` 安装：插件管理页会把它显示为运行中，配置页照旧可达。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-fonttune",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Font plugin for the DeepSeek Harness Web GUI: the conversation gets its own font, size, line height and weight, the interface font and weight follow it, code keeps its own axis with ligature control, and whole setups save as presets.",
   "type": "module",
   "main": "lib/index.js",
@@ -19,7 +19,7 @@
     "LICENSE"
   ],
   "engines": {
-    "dsh": ">=0.1.5-rc.3 <0.1.7-0 || >=0.1.7-alpha.1 <0.2.0-0"
+    "dsh": ">=0.1.5-rc.3 <0.1.7-0 || >=0.1.7-alpha.1 <0.3.0-0"
   },
   "dsh": {
     "bundle": {
@@ -34,7 +34,8 @@
         "0.1.7-alpha.1": "compatible",
         "0.1.7-alpha.2": "compatible",
         "0.1.7-rc.1": "compatible",
-        "0.1.7-rc.2": "compatible"
+        "0.1.7-rc.2": "compatible",
+        "0.2.0-rc.1": "compatible"
       }
     }
   },