dsh-unitverse 1.1.1 → 1.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/CHANGELOG.en.md +14 -0
  2. package/CHANGELOG.md +14 -0
  3. package/README.en.md +46 -13
  4. package/README.md +46 -13
  5. package/package.json +6 -6
package/CHANGELOG.en.md CHANGED
@@ -2,6 +2,20 @@
2
2
 
3
3
  This project follows [Semantic Versioning](https://semver.org/). Chinese version: [CHANGELOG.md](CHANGELOG.md).
4
4
 
5
+ ## [1.1.2] - 2026-09-14
6
+
7
+ ### Fixed
8
+
9
+ - **The community market classified the plugin as incompatible with the current DSH**: `package.json` declared the four client packages with `^0.1.0-rc.6` (i.e. `>=0.1.0-rc.6 <0.2.0`), but the DSH release line has moved to **0.2.x** — the Desktop app on this machine ships `0.2.0-rc.2`, including `dsh-client-locale` / `dsh-client-ui-conversation` / `dsh-client-ui-slots` at `0.2.0-rc.2`. By the market's own logic (dshmarket's `discovery-compatibility.js` plus `crossesImplicitCeiling` in `compatibility.js`), a host past the implicit `^0.1.x` ceiling counts as "the declared line is behind us", so the verdict was **incompatible**: once listed, 0.2.x users installing or updating would be told the plugin "declares DSH ^0.1.0-rc.6 while you are running 0.2.0-rc.2" and offered "no version declaring compatibility with the current DSH".
10
+ - Fix: the four client ranges and `@deepseek-ai/dsh-tools` now read **`^0.1.0-rc.6 || ^0.2.0-rc.1`**. Re-running the same derivation returns **compatible** for hosts `0.1.0-rc.6`, `0.1.1-rc.2` and `0.2.0-rc.2`.
11
+ - Also fixed `@deepseek-ai/dsh-tools: "*"`: a bare `*` does not match a prerelease under strict semver (here it resolved to `0.1.0-rc.8`), which the profile health check reported as `peer range @deepseek-ai/dsh-tools@* does not match resolved 0.1.0-rc.8`. Five plugins on this machine share that pattern.
12
+ - The READMEs (both languages) now state the requirement as "0.1.0-rc.6+ or 0.2.x" instead of "0.1.0-rc.6+", matching the new declarations.
13
+
14
+ ### Release
15
+
16
+ - npm: `dsh-unitverse@1.1.2`
17
+ - GitHub: https://github.com/runcat-tommy/dsh-unitverse
18
+
5
19
  ## [1.1.1] - 2026-09-10
6
20
 
7
21
  ### Added
package/CHANGELOG.md CHANGED
@@ -2,6 +2,20 @@
2
2
 
3
3
  本项目遵循[语义化版本](https://semver.org/lang/zh-CN/)。英文版见 [CHANGELOG.en.md](CHANGELOG.en.md)。
4
4
 
5
+ ## [1.1.2] - 2026-09-14
6
+
7
+ ### 修复
8
+
9
+ - **社区市场会把本插件判为「不兼容当前 DSH」**：`package.json` 里 4 个 client 包的 peer 范围原本只写 `^0.1.0-rc.6`（即 `>=0.1.0-rc.6 <0.2.0`），而 DSH 主线已推进到 **0.2.x**——本机桌面端实测为 `0.2.0-rc.2`，其 `dsh-client-locale` / `dsh-client-ui-conversation` / `dsh-client-ui-slots` 同为 `0.2.0-rc.2`。按市场自身的判定逻辑（dshmarket `discovery-compatibility.js` 与 `compatibility.js` 的 `crossesImplicitCeiling`），宿主越过 `^0.1.x` 的隐式上限即视为「声明的产品线已被落在身后」，判定为 **incompatible**：上架后 0.2.x 用户安装/更新时会看到「声明需要 DSH ^0.1.0-rc.6，而你现在运行的是 0.2.0-rc.2」，并得到「没有找到声明兼容当前 DSH 的版本」。
10
+ - 修复：4 个 client 包与 `@deepseek-ai/dsh-tools` 的范围改为 **`^0.1.0-rc.6 || ^0.2.0-rc.1`**。用同一判定函数实测：`0.1.0-rc.6` / `0.1.1-rc.2` / `0.2.0-rc.2` 三种宿主全部判定为 **compatible**。
11
+ - 顺带修掉 `@deepseek-ai/dsh-tools: "*"`：裸 `*` 在严格 semver 下**不匹配预发布版**（本机解析到 `0.1.0-rc.8`），profile 体检会报 `peer range @deepseek-ai/dsh-tools@* does not match resolved 0.1.0-rc.8` 警告——本机共 5 个插件都有此写法。
12
+ - README（中英）中「需 0.1.0-rc.6+ 的 Web GUI」的表述更新为「0.1.0-rc.6+ 或 0.2.x」，与新的声明范围一致。
13
+
14
+ ### 发布
15
+
16
+ - npm：`dsh-unitverse@1.1.2`
17
+ - GitHub：https://github.com/runcat-tommy/dsh-unitverse
18
+
5
19
  ## [1.1.1] - 2026-09-10
6
20
 
7
21
  ### 新增
package/README.en.md CHANGED
@@ -33,7 +33,7 @@ Chinese UI — all copy, category names and unit names in Chinese:
33
33
  in the session view bar; the panel is split into ten independent category
34
34
  modules (units are never mixed), and all copy — **unit names included** —
35
35
  follows the DSH zh/en UI language (since v0.1.0, requires the DSH Web GUI,
36
- 0.1.0-rc.6+)
36
+ 0.1.0-rc.6+ or 0.2.x)
37
37
 
38
38
  ## Supported categories and units
39
39
 
@@ -55,27 +55,60 @@ Chinese name** as aliases — e.g. `ft`, `foot`, `feet` and `英尺` are the sam
55
55
 
56
56
  ## Installation
57
57
 
58
- Install it as a DSH bundle — published on npm as `dsh-unitverse`; a local checkout, a tarball or GitHub work too:
58
+ `dsh-unitverse` is published on npm and can also be installed from GitHub, a local
59
+ directory or a tarball. **Pick any one of the four options below** — replace
60
+ `<profile-name>` with your profile (e.g. `web`).
61
+
62
+ ### Option 1: From npm (recommended)
63
+
64
+ The simplest route, with clear version semantics; works with any profile:
59
65
 
60
66
  ```bash
61
- # From npm (recommended)
62
67
  dsh plugin --profile <profile-name> add dsh-unitverse
68
+ ```
63
69
 
64
- # From a local checkout
65
- dsh plugin --profile <profile-name> add ./dsh-unitverse
70
+ ### Option 2: From GitHub
71
+
72
+ Use this to follow the repository source directly (the build artifacts in `lib/`
73
+ are committed):
66
74
 
67
- # Or from GitHub (build artifacts are committed, so no allowBuilds needed)
75
+ ```bash
68
76
  dsh plugin --profile <profile-name> add github:runcat-tommy/dsh-unitverse
69
77
  ```
70
78
 
71
- `package.json` declares `dsh.bundle`, so `dsh plugin add` registers the plugin
72
- row from `cordis.patch.yml` automatically.
79
+ > Because the runtime artifacts are committed, this route needs **no**
80
+ > `--allow-build` approval.
81
+
82
+ ### Option 3: From a local directory
83
+
84
+ Handy when you want to test local edits immediately, or keep the profile linked
85
+ to your checkout:
86
+
87
+ ```bash
88
+ dsh plugin --profile <profile-name> add ./dsh-unitverse
89
+ ```
90
+
91
+ ### Option 4: From a tarball
92
+
93
+ For offline / air-gapped environments, or to pin an already-packed artifact:
94
+
95
+ ```bash
96
+ npm pack # produces dsh-unitverse-<version>.tgz
97
+ dsh plugin --profile <profile-name> add ./dsh-unitverse-<version>.tgz
98
+ ```
73
99
 
74
- > The package also ships a browser half: the `dsh.client` declaration plus
75
- > `lib/client.js` behind the `exports["./client"]` entry. Installed into a
76
- > profile that runs the Web GUI, a "Unit Converter" tab appears in the session
77
- > view bar (see **Web converter view** below). In CLI-only profiles the client
78
- > part is simply never loaded and the tool keeps working.
100
+ ### After installing
101
+
102
+ - **No manual config edits**: `package.json` declares `dsh.bundle`, so `dsh plugin add`
103
+ registers the plugin in the profile's bundle list and activates the plugin row
104
+ defined in `cordis.patch.yml`.
105
+ - **Restart DSH** for it to take effect: once the GUI process (`dsh web` etc.)
106
+ restarts, the model can call the `convert` tool.
107
+ - **Web UI**: the package also ships a browser half — the `dsh.client` declaration
108
+ plus `lib/client.js` behind the `exports["./client"]` entry. In a profile that runs
109
+ the Web GUI, a "Unit Converter" tab appears in the session view tab bar (see
110
+ **Web converter view** below); in CLI-only profiles the client part is simply never
111
+ loaded and the tool keeps working.
79
112
 
80
113
  ## Web converter view (v0.1.0+)
81
114
 
package/README.md CHANGED
@@ -33,7 +33,7 @@ Chinese UI — all copy, category names and unit names in Chinese:
33
33
  in the session view bar; the panel is split into ten independent category
34
34
  modules (units are never mixed), and all copy — **unit names included** —
35
35
  follows the DSH zh/en UI language (since v0.1.0, requires the DSH Web GUI,
36
- 0.1.0-rc.6+)
36
+ 0.1.0-rc.6+ or 0.2.x)
37
37
 
38
38
  ## Supported categories and units
39
39
 
@@ -55,27 +55,60 @@ Chinese name** as aliases — e.g. `ft`, `foot`, `feet` and `英尺` are the sam
55
55
 
56
56
  ## Installation
57
57
 
58
- Install it as a DSH bundle — published on npm as `dsh-unitverse`; a local checkout, a tarball or GitHub work too:
58
+ `dsh-unitverse` is published on npm and can also be installed from GitHub, a local
59
+ directory or a tarball. **Pick any one of the four options below** — replace
60
+ `<profile-name>` with your profile (e.g. `web`).
61
+
62
+ ### Option 1: From npm (recommended)
63
+
64
+ The simplest route, with clear version semantics; works with any profile:
59
65
 
60
66
  ```bash
61
- # From npm (recommended)
62
67
  dsh plugin --profile <profile-name> add dsh-unitverse
68
+ ```
63
69
 
64
- # From a local checkout
65
- dsh plugin --profile <profile-name> add ./dsh-unitverse
70
+ ### Option 2: From GitHub
71
+
72
+ Use this to follow the repository source directly (the build artifacts in `lib/`
73
+ are committed):
66
74
 
67
- # Or from GitHub (build artifacts are committed, so no allowBuilds needed)
75
+ ```bash
68
76
  dsh plugin --profile <profile-name> add github:runcat-tommy/dsh-unitverse
69
77
  ```
70
78
 
71
- `package.json` declares `dsh.bundle`, so `dsh plugin add` registers the plugin
72
- row from `cordis.patch.yml` automatically.
79
+ > Because the runtime artifacts are committed, this route needs **no**
80
+ > `--allow-build` approval.
81
+
82
+ ### Option 3: From a local directory
83
+
84
+ Handy when you want to test local edits immediately, or keep the profile linked
85
+ to your checkout:
86
+
87
+ ```bash
88
+ dsh plugin --profile <profile-name> add ./dsh-unitverse
89
+ ```
90
+
91
+ ### Option 4: From a tarball
92
+
93
+ For offline / air-gapped environments, or to pin an already-packed artifact:
94
+
95
+ ```bash
96
+ npm pack # produces dsh-unitverse-<version>.tgz
97
+ dsh plugin --profile <profile-name> add ./dsh-unitverse-<version>.tgz
98
+ ```
73
99
 
74
- > The package also ships a browser half: the `dsh.client` declaration plus
75
- > `lib/client.js` behind the `exports["./client"]` entry. Installed into a
76
- > profile that runs the Web GUI, a "Unit Converter" tab appears in the session
77
- > view bar (see **Web converter view** below). In CLI-only profiles the client
78
- > part is simply never loaded and the tool keeps working.
100
+ ### After installing
101
+
102
+ - **No manual config edits**: `package.json` declares `dsh.bundle`, so `dsh plugin add`
103
+ registers the plugin in the profile's bundle list and activates the plugin row
104
+ defined in `cordis.patch.yml`.
105
+ - **Restart DSH** for it to take effect: once the GUI process (`dsh web` etc.)
106
+ restarts, the model can call the `convert` tool.
107
+ - **Web UI**: the package also ships a browser half — the `dsh.client` declaration
108
+ plus `lib/client.js` behind the `exports["./client"]` entry. In a profile that runs
109
+ the Web GUI, a "Unit Converter" tab appears in the session view tab bar (see
110
+ **Web converter view** below); in CLI-only profiles the client part is simply never
111
+ loaded and the tool keeps working.
79
112
 
80
113
  ## Web converter view (v0.1.0+)
81
114
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dsh-unitverse",
3
- "version": "1.1.1",
3
+ "version": "1.1.2",
4
4
  "description": "DSH plugin: universal unit conversion across length, area, volume, time, angle, speed, temperature, pressure, energy and power, with Chinese/English aliases. 单位换算 DSH 插件（长度/面积/体积/时间/角度/速度/温度/压力/热量/功率，支持中英文单位名）。",
5
5
  "keywords": [
6
6
  "dsh",
@@ -78,11 +78,11 @@
78
78
  },
79
79
  "peerDependencies": {
80
80
  "@deepseek-ai/cordis": "*",
81
- "@deepseek-ai/dsh-client-locale": "^0.1.0-rc.6",
82
- "@deepseek-ai/dsh-client-runtime": "^0.1.0-rc.6",
83
- "@deepseek-ai/dsh-client-ui-conversation": "^0.1.0-rc.6",
84
- "@deepseek-ai/dsh-client-ui-slots": "^0.1.0-rc.6",
85
- "@deepseek-ai/dsh-tools": "*",
81
+ "@deepseek-ai/dsh-client-locale": "^0.1.0-rc.6 || ^0.2.0-rc.1",
82
+ "@deepseek-ai/dsh-client-runtime": "^0.1.0-rc.6 || ^0.2.0-rc.1",
83
+ "@deepseek-ai/dsh-client-ui-conversation": "^0.1.0-rc.6 || ^0.2.0-rc.1",
84
+ "@deepseek-ai/dsh-client-ui-slots": "^0.1.0-rc.6 || ^0.2.0-rc.1",
85
+ "@deepseek-ai/dsh-tools": "^0.1.0-rc.6 || ^0.2.0-rc.1",
86
86
  "react": "^18.2.0",
87
87
  "react-dom": "^18.2.0"
88
88
  },