@max-null/dsh-skill-mcp-center 0.5.1 → 0.5.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.
- package/README.md +1 -1
- package/package.json +9 -9
- package/release-notes.md +22 -0
package/README.md
CHANGED
|
@@ -10,7 +10,7 @@ Skill 与 MCP 管理中心：在设置里管理 skills 与 MCP 服务器，右
|
|
|
10
10
|
|
|
11
11
|
## Features / 功能
|
|
12
12
|
|
|
13
|
-
- **Skill management / Skill 管理** — browse every skill by
|
|
13
|
+
- **Skill management / Skill 管理** — browse every skill grouped by source (Global / Workspace / Built-in DSH official, plus one group per plugin that ships skills), toggle model invocation via the `disable-model-invocation` frontmatter (disk-backed skills only). Covers skills shipped **inside plugin packages** (e.g. `@max-null/dsh-skills`), not just the user-level roots — the host-level skill filesystem is disabled in web-app, so a plugin's own `skills/` directory would otherwise be invisible while its skills are loaded and in effect.
|
|
14
14
|
- **MCP management / MCP 管理** — add / edit / remove `mcp-client` servers, enable/disable without deleting config, all **hot-applied** through `ctx.loader` (no restart).
|
|
15
15
|
- **Live status / 实时状态** — a sidebar "MCP" tab (via `dsh-better-sidebar`) showing per-server connection state; **click a server row to expand its tools' names and descriptions** (collapsed by default — a server can expose dozens of them). Names come from `tools.schemas()`; the redundant `mcp__<server>__` prefix is hidden while the full name stays on hover. Polled while visible and following the session.
|
|
16
16
|
- **Skin-compatible / 皮肤兼容** — every color uses `var(--dsw-*)` tokens.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@max-null/dsh-skill-mcp-center",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.2",
|
|
4
4
|
"description": "Skill & MCP management center for DeepSeek Harness — manage skills and MCP servers in Settings, live MCP status in the sidebar",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"publishConfig": {
|
|
@@ -67,18 +67,18 @@
|
|
|
67
67
|
"peerDependencies": {
|
|
68
68
|
"@deepseek-ai/cordis": "^4.0.1",
|
|
69
69
|
"@deepseek-ai/cordis-plugin-loader": "^1.0.2",
|
|
70
|
-
"@deepseek-ai/dsh-client-connection": "
|
|
71
|
-
"@deepseek-ai/dsh-host-apiproxy": "
|
|
72
|
-
"@deepseek-ai/dsh-skill": "
|
|
73
|
-
"@deepseek-ai/dsh-tools": "
|
|
70
|
+
"@deepseek-ai/dsh-client-connection": ">=0.1.1-rc.1 <0.3.0",
|
|
71
|
+
"@deepseek-ai/dsh-host-apiproxy": ">=0.1.1-rc.1 <0.3.0",
|
|
72
|
+
"@deepseek-ai/dsh-skill": ">=0.1.1-rc.1 <0.3.0",
|
|
73
|
+
"@deepseek-ai/dsh-tools": ">=0.1.1-rc.1 <0.3.0"
|
|
74
74
|
},
|
|
75
75
|
"devDependencies": {
|
|
76
76
|
"@deepseek-ai/cordis": "^4.0.1",
|
|
77
77
|
"@deepseek-ai/cordis-plugin-loader": "^1.0.2",
|
|
78
|
-
"@deepseek-ai/dsh-client-connection": "
|
|
79
|
-
"@deepseek-ai/dsh-host-apiproxy": "
|
|
80
|
-
"@deepseek-ai/dsh-skill": "
|
|
81
|
-
"@deepseek-ai/dsh-tools": "
|
|
78
|
+
"@deepseek-ai/dsh-client-connection": ">=0.1.1-rc.1 <0.3.0",
|
|
79
|
+
"@deepseek-ai/dsh-host-apiproxy": ">=0.1.1-rc.1 <0.3.0",
|
|
80
|
+
"@deepseek-ai/dsh-skill": ">=0.1.1-rc.1 <0.3.0",
|
|
81
|
+
"@deepseek-ai/dsh-tools": ">=0.1.1-rc.1 <0.3.0",
|
|
82
82
|
"@types/js-yaml": "^4.0.9",
|
|
83
83
|
"@types/node": "^26.2.0",
|
|
84
84
|
"@types/react": "~18.3.1",
|
package/release-notes.md
CHANGED
|
@@ -1,5 +1,27 @@
|
|
|
1
1
|
# Release Notes — @max-null/dsh-skill-mcp-center
|
|
2
2
|
|
|
3
|
+
## 0.5.2 (2026-09-29)
|
|
4
|
+
|
|
5
|
+
### 变更
|
|
6
|
+
|
|
7
|
+
- 放宽 `@deepseek-ai/dsh-*` 的版本范围：`peerDependencies` 与 `devDependencies` 中的
|
|
8
|
+
`dsh-client-connection`、`dsh-host-apiproxy`、`dsh-skill`、`dsh-tools` 由 `^0.1.1-rc.1`
|
|
9
|
+
改为 `>=0.1.1-rc.1 <0.3.0` —— 保留下限、只放宽上界，旧内核（0.1.7-rc.2）仍然满足。
|
|
10
|
+
|
|
11
|
+
### 为什么
|
|
12
|
+
|
|
13
|
+
- 内核侧逐个检查插件 `peerDependencies` 里的每个 `@deepseek-ai/*` 声明，判据是标准 semver：
|
|
14
|
+
`semver.satisfies(runtimeVersion, requirement, { includePrerelease: true })`。
|
|
15
|
+
- `^0.1.1-rc.1` 展开为 `>=0.1.1-rc.1 <0.2.0-0`，对 `0.2.0-rc.1` 判 **false**；判定失败的插件
|
|
16
|
+
会被**静默跳过**——不进 fiber graph，也不出现在「did not activate」列表里，用户侧的表现
|
|
17
|
+
是「插件装了却毫无反应」，没有任何日志可查。
|
|
18
|
+
- `>=0.1.1-rc.1 <0.3.0` 在 semver 7.7.4 下对 `0.1.7-rc.2` 与 `0.2.0-rc.1` 均判 true（已实测）。
|
|
19
|
+
|
|
20
|
+
### 兼容性
|
|
21
|
+
|
|
22
|
+
- 无运行时行为变更：端点集合、请求体、响应信封与代码路径均未改，只是依赖声明放宽。
|
|
23
|
+
- 面板端与宿主端仍需同版本（传输策略见 0.5.1）。
|
|
24
|
+
|
|
3
25
|
## 0.5.1 (2026-09-17)
|
|
4
26
|
|
|
5
27
|
### 修复
|