dsh-bailinghub 0.1.0 → 0.1.1
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/CHANGELOG.md +6 -0
- package/README.md +3 -3
- package/{README.zh-CN.md → docs/README.zh-CN.md} +3 -3
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.1 - 2026-08-18
|
|
4
|
+
|
|
5
|
+
- Make the project contract accept future SemVer releases while keeping package and lock versions aligned.
|
|
6
|
+
- Keep the npm landing page English-first and retain the Chinese guide under `docs/`.
|
|
7
|
+
- Document the exact release-update surface, focused compatibility smoke, and patch-release recovery path.
|
|
8
|
+
|
|
3
9
|
## 0.1.0 - 2026-08-18
|
|
4
10
|
|
|
5
11
|
- Add an installable DeepSeek Harness bundle for BailingHub.
|
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# BailingHub for DeepSeek Harness
|
|
2
2
|
|
|
3
|
-
[简体中文](README.zh-CN.md) | English
|
|
3
|
+
[简体中文](docs/README.zh-CN.md) | English
|
|
4
4
|
|
|
5
5
|
Run governed tasks from DeepSeek Harness against a business route already connected to
|
|
6
6
|
BailingHub, then track the same job and read its available result. You can do this from the
|
|
@@ -36,7 +36,7 @@ Prerequisites:
|
|
|
36
36
|
|
|
37
37
|
```bash
|
|
38
38
|
npm install --global pnpm @deepseek-ai/dsh@0.1.0-rc.7
|
|
39
|
-
dsh plugin --profile web add dsh-bailinghub@0.1.
|
|
39
|
+
dsh plugin --profile web add dsh-bailinghub@0.1.1
|
|
40
40
|
```
|
|
41
41
|
|
|
42
42
|
Configure the process that starts Harness:
|
|
@@ -73,7 +73,7 @@ bounded wait times out.
|
|
|
73
73
|
|
|
74
74
|
Using the local Harness UI removes the need to open a business backend's embedded chat UI;
|
|
75
75
|
it does **not** turn the Harness login or local user into a trusted business identity.
|
|
76
|
-
|
|
76
|
+
The current `0.1.x` bundle deliberately does not accept an acting subject as tool input. A route or
|
|
77
77
|
downstream business system must still resolve trusted identity and perform final
|
|
78
78
|
authorization. If the selected action requires identity that the configured path cannot
|
|
79
79
|
establish, it should remain unavailable or be rejected.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# BailingHub for DeepSeek Harness
|
|
2
2
|
|
|
3
|
-
[English](README.md) | 简体中文
|
|
3
|
+
[English](../README.md) | 简体中文
|
|
4
4
|
|
|
5
5
|
在电脑上的 DeepSeek Harness 里，通过 BailingHub 向已经接入的业务 route 发起受控任务，
|
|
6
6
|
并在同一会话中持续查看状态和可用结果，不必再进入每个业务后台里的嵌入聊天入口。
|
|
@@ -32,7 +32,7 @@ BailingHub 仍位于模型与业务系统之间。中枢地址、Client Token
|
|
|
32
32
|
|
|
33
33
|
```bash
|
|
34
34
|
npm install --global pnpm @deepseek-ai/dsh@0.1.0-rc.7
|
|
35
|
-
dsh plugin --profile web add dsh-bailinghub@0.1.
|
|
35
|
+
dsh plugin --profile web add dsh-bailinghub@0.1.1
|
|
36
36
|
```
|
|
37
37
|
|
|
38
38
|
在启动 Harness 的终端或进程环境中配置：
|
|
@@ -67,7 +67,7 @@ dsh web
|
|
|
67
67
|
## 身份与权限边界
|
|
68
68
|
|
|
69
69
|
使用本机 Harness 界面，省掉的是“必须打开业务后台聊天入口”这一步；它不代表 Harness
|
|
70
|
-
|
|
70
|
+
登录态或本机用户自动成为可信业务身份。当前 `0.1.x` Bundle 有意不接受模型传入行动主体。route 或
|
|
71
71
|
下游业务系统仍需解析可信主体并执行最终授权；如果目标动作必须具备业务身份，而当前接入
|
|
72
72
|
路径无法建立该身份，该动作就应保持不可用或被拒绝。
|
|
73
73
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-bailinghub",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"description": "Use DeepSeek Harness to submit and follow governed business tasks through BailingHub.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -30,7 +30,7 @@
|
|
|
30
30
|
],
|
|
31
31
|
"files": [
|
|
32
32
|
"cordis.patch.yml",
|
|
33
|
-
"README.zh-CN.md",
|
|
33
|
+
"docs/README.zh-CN.md",
|
|
34
34
|
"SECURITY.md",
|
|
35
35
|
"PRIVACY.md",
|
|
36
36
|
"CHANGELOG.md",
|