dsh-auth-remote 0.1.3 → 0.1.5

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 CHANGED
@@ -8,6 +8,12 @@ This file records user-visible changes to the released package. Version numbers
8
8
 
9
9
  No changes recorded yet.
10
10
 
11
+ ## 0.1.5 - 2026-10-03
12
+
13
+ - Verify DSH 0.2.1-alpha.1 with the existing authentication implementation and add it to the CLI, installation smoke, and browser CI matrix, retaining all previously tested versions.
14
+ - Declare all verified releases in `dsh.compatibility.dshReleases` and use DSH 0.2.1-alpha.1 as the default development, test, and release runtime; update pinned dependencies and bilingual guides.
15
+ - Wait for the native API key onboarding prompt before interacting with Host settings or the workspace picker, preventing delayed host dialogs from blocking browser verification.
16
+
11
17
  ## 0.1.3 - 2026-09-30
12
18
 
13
19
  - Verify DSH 0.2.0-rc.2 and add it to the CLI, installation smoke, and browser CI matrix, retaining all previously tested versions.
@@ -8,6 +8,12 @@
8
8
 
9
9
  暂无记录。
10
10
 
11
+ ## 0.1.5 - 2026-10-03
12
+
13
+ - 验证现有认证实现可直接支持 DSH 0.2.1-alpha.1,将其加入 CLI、安装冒烟和浏览器 CI 矩阵,并保留之前已测试的所有版本。
14
+ - 在 `dsh.compatibility.dshReleases` 中声明已验证版本,将默认开发、测试和发布运行时升级为 DSH 0.2.1-alpha.1,同步更新锁定依赖与中英文指南。
15
+ - 操作宿主设置或工作区选择器前,等待并完成原生 API Key 引导,避免迟到的宿主弹窗阻塞浏览器验证。
16
+
11
17
  ## 0.1.3 - 2026-09-30
12
18
 
13
19
  - 验证 DSH 0.2.0-rc.2,将其加入 CLI、安装冒烟和浏览器 CI 矩阵,并保留之前已测试的所有版本。
package/README.md CHANGED
@@ -6,17 +6,17 @@ Single-user remote sign-in for DeepSeek Harness (DSH), with password, TOTP, one-
6
6
 
7
7
  ## Requirements
8
8
 
9
- - Linux with `/proc`, Node.js 24 or newer, and a tested DSH runtime: **0.1.7-rc.1**, **0.1.7-rc.2**, **0.2.0-rc.1**, or **0.2.0-rc.2** (default). pnpm 12.5.1 is needed only when building from source.
9
+ - Linux with `/proc`, Node.js 24 or newer, and a tested DSH runtime: **0.1.7-rc.1**, **0.1.7-rc.2**, **0.2.0-rc.1**, **0.2.0-rc.2**, or **0.2.1-alpha.1** (default). pnpm 12.5.1 is needed only when building from source.
10
10
  - DSH's default `~/.dsh` data directory and a `web` profile. The account state belongs to that profile; it is not shared with another profile.
11
11
  - For source browser tests, install Playwright Chromium with `pnpm exec playwright install chromium`. The tests use that managed browser and a dedicated, self-signed TLS fixture.
12
12
 
13
13
  ## DSH compatibility
14
14
 
15
- Plugin 0.1.3 is tested against DSH **0.1.7-rc.1**, **0.1.7-rc.2**, **0.2.0-rc.1**, and **0.2.0-rc.2**. The default supported runtime is **0.2.0-rc.2**. The host peer declaration and runtime version check both use `>=0.1.7-rc.1`, with no upper bound. DSH's loader includes prereleases, so 0.2 and later releases are admitted without a per-version exemption or a plugin update solely to widen the range.
15
+ Plugin 0.1.5 is tested against DSH **0.1.7-rc.1**, **0.1.7-rc.2**, **0.2.0-rc.1**, **0.2.0-rc.2**, and **0.2.1-alpha.1**. The default supported runtime is **0.2.1-alpha.1**. These exact releases are declared in `dsh.compatibility.dshReleases`. The host peer declaration and runtime version check both use `>=0.1.7-rc.1`, with no upper bound. DSH's loader includes prereleases, so 0.2 and later releases are admitted without a per-version exemption or a plugin update solely to widen the range.
16
16
 
17
- Later versions are forward-admitted, not claimed as tested. The plugin still verifies the required WebServer/Connection APIs, shared host package identity, and native authentication exchange. If those contracts change, authentication stays unavailable with a diagnostic; removing the version ceiling cannot guarantee compatibility with unknown API changes. CI runs CLI, installation smoke, and browser regressions on all four tested versions.
17
+ Later versions are forward-admitted, not claimed as tested. The plugin still verifies the required WebServer/Connection APIs, shared host package identity, and native authentication exchange. If those contracts change, authentication stays unavailable with a diagnostic; removing the version ceiling cannot guarantee compatibility with unknown API changes. CI runs CLI, installation smoke, and browser regressions on all five tested versions.
18
18
 
19
- Plugin **0.1.3** makes DSH 0.2.0-rc.2 the default verified runtime. The open-ended compatibility range and theme integration were introduced in **0.1.2**. For source builds, see the [development guide](docs/development.md).
19
+ Plugin **0.1.5** makes DSH 0.2.1-alpha.1 the default verified runtime. The existing **0.1.3** authentication implementation also passes the CLI and browser suites on this runtime. The open-ended compatibility range and theme integration were introduced in **0.1.2**. For source builds, see the [development guide](docs/development.md).
20
20
 
21
21
  ## Install from npm
22
22
 
@@ -24,11 +24,11 @@ With DSH installed, verify its version and install the published plugin into the
24
24
 
25
25
  ```sh
26
26
  dsh --version
27
- dsh plugin --profile web add dsh-auth-remote@0.1.3
27
+ dsh plugin --profile web add dsh-auth-remote@0.1.5
28
28
  dsh plugin --profile web list
29
29
  ```
30
30
 
31
- Check that `dsh --version` prints `0.2.0-rc.2` (or another tested version listed above) and the plugin list includes `dsh-auth-remote@0.1.3`. These commands use DSH's default data directory. For source builds and an isolated development runtime, see the [development guide](docs/development.md).
31
+ Check that `dsh --version` prints `0.2.1-alpha.1` (or another tested version listed above) and the plugin list includes `dsh-auth-remote@0.1.5`. These commands use DSH's default data directory. For source builds and an isolated development runtime, see the [development guide](docs/development.md).
32
32
 
33
33
  ## Configure the web profile
34
34
 
package/README.zh-CN.md CHANGED
@@ -6,17 +6,17 @@ DeepSeek Harness(DSH)的单用户远程登录插件,提供密码、TOTP、
6
6
 
7
7
  ## 前置条件
8
8
 
9
- - Linux(含 `/proc`)、Node.js 24 或更高版本,以及已测试的 DSH **0.1.7-rc.1**、**0.1.7-rc.2**、**0.2.0-rc.1** 或 **0.2.0-rc.2**(默认)运行时。仅从源码构建时需要 pnpm 12.5.1。
9
+ - Linux(含 `/proc`)、Node.js 24 或更高版本,以及已测试的 DSH **0.1.7-rc.1**、**0.1.7-rc.2**、**0.2.0-rc.1**、**0.2.0-rc.2** 或 **0.2.1-alpha.1**(默认)运行时。仅从源码构建时需要 pnpm 12.5.1。
10
10
  - DSH 默认的 `~/.dsh` 数据目录和 `web` profile。账号状态属于该 profile,不与其他 profile 共用。
11
11
  - 源码浏览器测试先执行 `pnpm exec playwright install chromium`。测试使用 Playwright 管理的浏览器和专用自签 TLS 夹具。
12
12
 
13
13
  ## DSH 兼容性
14
14
 
15
- 插件 0.1.3 已测试 DSH **0.1.7-rc.1**、**0.1.7-rc.2**、**0.2.0-rc.1** 和 **0.2.0-rc.2**,默认支持运行时为 **0.2.0-rc.2**。宿主 peer 声明和运行时版本检查统一使用 `>=0.1.7-rc.1`,不设版本上限。DSH 的加载器检查包含预发布版本,因此 0.2 及后续版本无需逐版豁免,也无需仅为放宽版本范围而更新插件。
15
+ 插件 0.1.5 已测试 DSH **0.1.7-rc.1**、**0.1.7-rc.2**、**0.2.0-rc.1**、**0.2.0-rc.2** 和 **0.2.1-alpha.1**,默认支持运行时为 **0.2.1-alpha.1**。这些精确版本均在 `dsh.compatibility.dshReleases` 中声明。宿主 peer 声明和运行时版本检查统一使用 `>=0.1.7-rc.1`,不设版本上限。DSH 的加载器检查包含预发布版本,因此 0.2 及后续版本无需逐版豁免,也无需仅为放宽版本范围而更新插件。
16
16
 
17
- 后续版本属于向前准入,并不宣称已经逐版测试。插件仍检查必需的 WebServer/Connection 接口、宿主包实例一致性和原生认证交换。若这些约定改变,认证入口会保持不可用并给出诊断;取消版本上限不能保证未知接口变更后的兼容性。CI 在上述四个版本上运行 CLI、安装冒烟和浏览器回归。
17
+ 后续版本属于向前准入,并不宣称已经逐版测试。插件仍检查必需的 WebServer/Connection 接口、宿主包实例一致性和原生认证交换。若这些约定改变,认证入口会保持不可用并给出诊断;取消版本上限不能保证未知接口变更后的兼容性。CI 在上述五个版本上运行 CLI、安装冒烟和浏览器回归。
18
18
 
19
- 插件 **0.1.3** 将 DSH 0.2.0-rc.2 设为默认已验证运行时。无版本上限的兼容范围和主题集成从插件 **0.1.2** 开始提供。源码构建参见[开发指南](docs/development.zh-CN.md)。
19
+ 插件 **0.1.5** 将 DSH 0.2.1-alpha.1 设为默认已验证运行时。现有 **0.1.3** 的认证实现也已在该运行时通过 CLI 和浏览器测试。无版本上限的兼容范围和主题集成从插件 **0.1.2** 开始提供。源码构建参见[开发指南](docs/development.zh-CN.md)。
20
20
 
21
21
  ## 从 npm 安装
22
22
 
@@ -24,11 +24,11 @@ DeepSeek Harness(DSH)的单用户远程登录插件,提供密码、TOTP、
24
24
 
25
25
  ```sh
26
26
  dsh --version
27
- dsh plugin --profile web add dsh-auth-remote@0.1.3
27
+ dsh plugin --profile web add dsh-auth-remote@0.1.5
28
28
  dsh plugin --profile web list
29
29
  ```
30
30
 
31
- 确认 `dsh --version` 输出 `0.2.0-rc.2`(或上文列出的其他已测试版本),且插件列表中有 `dsh-auth-remote@0.1.3`。这些命令使用 DSH 默认数据目录。源码构建及隔离开发运行时参见[开发指南](docs/development.zh-CN.md)。
31
+ 确认 `dsh --version` 输出 `0.2.1-alpha.1`(或上文列出的其他已测试版本),且插件列表中有 `dsh-auth-remote@0.1.5`。这些命令使用 DSH 默认数据目录。源码构建及隔离开发运行时参见[开发指南](docs/development.zh-CN.md)。
32
32
 
33
33
  ## 配置 web profile
34
34
 
@@ -2,9 +2,9 @@
2
2
 
3
3
  [简体中文](deployment.zh-CN.md)
4
4
 
5
- This guide describes a new installation with the verified DSH `0.2.0-rc.2` runtime and its default `~/.dsh` data directory. It does not depend on a particular public hostname, proxy network, service manager, or existing account database.
5
+ This guide describes a new installation with the verified DSH `0.2.1-alpha.1` runtime and its default `~/.dsh` data directory. It does not depend on a particular public hostname, proxy network, service manager, or existing account database.
6
6
 
7
- The npm steps below use plugin `0.1.3`. Before upgrading an existing installation, review [compatibility](../README.md#dsh-compatibility); for source builds, see the [development guide](development.md).
7
+ The npm steps below use plugin `0.1.5`. Before upgrading an existing installation, review [compatibility](../README.md#dsh-compatibility); for source builds, see the [development guide](development.md).
8
8
 
9
9
  ## Minimal installation from npm
10
10
 
@@ -12,11 +12,11 @@ Install the published package into the default `web` profile:
12
12
 
13
13
  ```sh
14
14
  dsh --version
15
- dsh plugin --profile web add dsh-auth-remote@0.1.3
15
+ dsh plugin --profile web add dsh-auth-remote@0.1.5
16
16
  dsh plugin --profile web list
17
17
  ```
18
18
 
19
- Verify that `dsh --version` prints `0.2.0-rc.2` and the list includes `dsh-auth-remote@0.1.3`. The bundle supplies an auth listener with `allowedOrigins: []`, which admits only literal loopback hosts. No profile patch is needed for this setup. Start DSH in one terminal:
19
+ Verify that `dsh --version` prints `0.2.1-alpha.1` and the list includes `dsh-auth-remote@0.1.5`. The bundle supplies an auth listener with `allowedOrigins: []`, which admits only literal loopback hosts. No profile patch is needed for this setup. Start DSH in one terminal:
20
20
 
21
21
  ```sh
22
22
  dsh web --no-open --port 13090
@@ -2,9 +2,9 @@
2
2
 
3
3
  [English](deployment.md)
4
4
 
5
- 本指南说明使用已验证的 DSH `0.2.0-rc.2` 和默认的 `~/.dsh` 数据目录进行全新安装,不假定公网域名、代理网络、服务管理器或现有账号数据库。
5
+ 本指南说明使用已验证的 DSH `0.2.1-alpha.1` 和默认的 `~/.dsh` 数据目录进行全新安装,不假定公网域名、代理网络、服务管理器或现有账号数据库。
6
6
 
7
- 下面的 npm 步骤使用插件 `0.1.3`。升级已有安装前,请参阅[兼容说明](../README.zh-CN.md#dsh-兼容性);源码构建参见[开发指南](development.zh-CN.md)。
7
+ 下面的 npm 步骤使用插件 `0.1.5`。升级已有安装前,请参阅[兼容说明](../README.zh-CN.md#dsh-兼容性);源码构建参见[开发指南](development.zh-CN.md)。
8
8
 
9
9
  ## 从 npm 最小化安装
10
10
 
@@ -12,11 +12,11 @@
12
12
 
13
13
  ```sh
14
14
  dsh --version
15
- dsh plugin --profile web add dsh-auth-remote@0.1.3
15
+ dsh plugin --profile web add dsh-auth-remote@0.1.5
16
16
  dsh plugin --profile web list
17
17
  ```
18
18
 
19
- 确认 `dsh --version` 输出 `0.2.0-rc.2`,且列表中有 `dsh-auth-remote@0.1.3`。bundle 提供认证监听,默认 `allowedOrigins: []`,因此只准入字面回环主机。最小安装无需修改 profile 补丁。在一个终端启动 DSH:
19
+ 确认 `dsh --version` 输出 `0.2.1-alpha.1`,且列表中有 `dsh-auth-remote@0.1.5`。bundle 提供认证监听,默认 `allowedOrigins: []`,因此只准入字面回环主机。最小安装无需修改 profile 补丁。在一个终端启动 DSH:
20
20
 
21
21
  ```sh
22
22
  dsh web --no-open --port 13090
@@ -2,7 +2,7 @@
2
2
 
3
3
  [简体中文](development.zh-CN.md)
4
4
 
5
- Development and the full test suite use Linux (`/proc` is required for the profile lock), Node.js 24+, pnpm 12.5.1, and DSH `0.2.0-rc.2`. Browser tests use Playwright-managed Chromium and a Node HTTP/HTTPS forwarder.
5
+ Development and the full test suite use Linux (`/proc` is required for the profile lock), Node.js 24+, pnpm 12.5.1, and DSH `0.2.1-alpha.1`. Browser tests use Playwright-managed Chromium and a Node HTTP/HTTPS forwarder.
6
6
 
7
7
  ## Set up and check a checkout
8
8
 
@@ -14,7 +14,7 @@ pnpm pack:local
14
14
  pnpm smoke
15
15
  ```
16
16
 
17
- `pnpm check` runs type checking, formatting, build, package/deployment/document checks, then unit, integration, CLI, and browser tests. `pnpm pack:local` writes `artifacts/dsh-auth-remote-0.1.3.tgz` after static checks; it does not publish. `pnpm smoke` installs that archive into an isolated DSH home, starts the pinned DSH runtime briefly, checks readiness, anonymous redirection/denial and an online CLI status, then stops it.
17
+ `pnpm check` runs type checking, formatting, build, package/deployment/document checks, then unit, integration, CLI, and browser tests. `pnpm pack:local` writes `artifacts/dsh-auth-remote-0.1.5.tgz` after static checks; it does not publish. `pnpm smoke` installs that archive into an isolated DSH home, starts the pinned DSH runtime briefly, checks readiness, anonymous redirection/denial and an online CLI status, then stops it.
18
18
 
19
19
  ## Use the isolated development profile
20
20
 
@@ -29,7 +29,7 @@ The scripts manage only `.dev/runtime-<version>` and `.dev/dsh-home` under this
29
29
  For direct inspection, use the same isolated home explicitly:
30
30
 
31
31
  ```sh
32
- DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.0-rc.2/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
32
+ DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.1-alpha.1/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
33
33
  ```
34
34
 
35
35
  The development home contains test account data. Keep it private and do not commit or copy it into a deployment profile.
@@ -38,13 +38,13 @@ The development home contains test account data. Keep it private and do not comm
38
38
 
39
39
  `pnpm test:unit` covers the auth state machine, TOTP, backup codes, origin policy, translations, storage durability and lock recovery. `pnpm test:integration` exercises real HTTP/WebSocket sockets, native readiness, cookies, origin decisions and revocation. `pnpm test:cli` builds the real archive and tests interactive and noninteractive commands against isolated profiles and Unix sockets. `pnpm test:browser` boots the selected DSH version with temporary profiles and verifies the login and Security UI, native settings, workspace, upload/preview, SSE, WebSocket and an HTTPS forwarding chain.
40
40
 
41
- Browser network traffic uses a Node HTTP/HTTPS forwarder. The dedicated self-signed certificate and key under `tests/fixtures/tls/` are test fixtures only; they are never packaged or deployment credentials. Chat uses a local model stub. No real third-party authorization or paid model request is exercised. The default browser is Playwright Chromium; `DSH_TEST_BROWSER` can select a local browser executable, and `DSH_TEST_BIN` can select another binary only if it reports the exact selected version (default `0.2.0-rc.2`).
41
+ Browser network traffic uses a Node HTTP/HTTPS forwarder. The dedicated self-signed certificate and key under `tests/fixtures/tls/` are test fixtures only; they are never packaged or deployment credentials. Chat uses a local model stub. No real third-party authorization or paid model request is exercised. The default browser is Playwright Chromium; `DSH_TEST_BROWSER` can select a local browser executable, and `DSH_TEST_BIN` can select another binary only if it reports the exact selected version (default `0.2.1-alpha.1`).
42
42
 
43
43
  The DSH test runtime lives in `.cache/test-runtime/<version>` and is pinned separately from the source dependencies. Host services and React remain external to the client bundle. The [deployment guide](deployment.md) describes profile and backup rules.
44
44
 
45
45
  ## Cross-version verification
46
46
 
47
- The default test target is DSH `0.2.0-rc.2`. Set `DSH_TEST_VERSION` to `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, or `0.2.0-rc.2`; test runtimes live separately under `.cache/test-runtime/<version>` and development runtimes under `.dev/runtime-<version>`. `DSH_TEST_BIN` must report the exact selected version. CI runs CLI, installation smoke, and browser tests for all four versions. Development types and integration tests use the pinned 0.2.0-rc.2 packages.
47
+ The default test target is DSH `0.2.1-alpha.1`. Set `DSH_TEST_VERSION` to `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2`, or `0.2.1-alpha.1`; test runtimes live separately under `.cache/test-runtime/<version>` and development runtimes under `.dev/runtime-<version>`. `DSH_TEST_BIN` must report the exact selected version. CI runs CLI, installation smoke, and browser tests for all five versions. Development types and integration tests use the pinned 0.2.1-alpha.1 packages.
48
48
 
49
49
  ```sh
50
50
  DSH_TEST_VERSION=0.1.7-rc.1 pnpm test:cli
@@ -53,6 +53,8 @@ DSH_TEST_VERSION=0.1.7-rc.2 pnpm test:cli
53
53
  DSH_TEST_VERSION=0.1.7-rc.2 pnpm test:browser
54
54
  DSH_TEST_VERSION=0.2.0-rc.1 pnpm test:cli
55
55
  DSH_TEST_VERSION=0.2.0-rc.1 pnpm test:browser
56
+ DSH_TEST_VERSION=0.2.0-rc.2 pnpm test:cli
57
+ DSH_TEST_VERSION=0.2.0-rc.2 pnpm test:browser
56
58
  pnpm test:cli
57
59
  pnpm test:browser
58
60
  ```
@@ -2,7 +2,7 @@
2
2
 
3
3
  [English](development.md)
4
4
 
5
- 开发和完整测试需要 Linux(profile 锁依赖 `/proc`)、Node.js 24+、pnpm 12.5.1,以及 DSH `0.2.0-rc.2`。浏览器测试使用 Playwright 管理的 Chromium 和 Node HTTP/HTTPS 转发器。
5
+ 开发和完整测试需要 Linux(profile 锁依赖 `/proc`)、Node.js 24+、pnpm 12.5.1,以及 DSH `0.2.1-alpha.1`。浏览器测试使用 Playwright 管理的 Chromium 和 Node HTTP/HTTPS 转发器。
6
6
 
7
7
  ## 准备和检查源码检出
8
8
 
@@ -14,7 +14,7 @@ pnpm pack:local
14
14
  pnpm smoke
15
15
  ```
16
16
 
17
- `pnpm check` 依次执行类型、格式、构建、包/部署/文档检查,以及单元、集成、CLI 和浏览器测试。`pnpm pack:local` 在静态检查后写出 `artifacts/dsh-auth-remote-0.1.3.tgz`,不会发布。`pnpm smoke` 将包安装到隔离 DSH_HOME,短暂启动固定版本的 DSH,验证就绪、匿名重定向/拒绝和在线 CLI 状态,然后停止。
17
+ `pnpm check` 依次执行类型、格式、构建、包/部署/文档检查,以及单元、集成、CLI 和浏览器测试。`pnpm pack:local` 在静态检查后写出 `artifacts/dsh-auth-remote-0.1.5.tgz`,不会发布。`pnpm smoke` 将包安装到隔离 DSH_HOME,短暂启动固定版本的 DSH,验证就绪、匿名重定向/拒绝和在线 CLI 状态,然后停止。
18
18
 
19
19
  ## 使用隔离开发 profile
20
20
 
@@ -29,7 +29,7 @@ pnpm dev:start
29
29
  直接查看状态时显式使用同一隔离 home:
30
30
 
31
31
  ```sh
32
- DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.0-rc.2/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
32
+ DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.1-alpha.1/node_modules/.bin/dsh" plugin --profile web exec dsh-auth-remote status --json
33
33
  ```
34
34
 
35
35
  开发 home 可能含测试账号数据,须保持私有,不要提交或复制到部署 profile。
@@ -38,13 +38,13 @@ DSH_HOME="$PWD/.dev/dsh-home" "$PWD/.dev/runtime-0.2.0-rc.2/node_modules/.bin/ds
38
38
 
39
39
  `pnpm test:unit` 覆盖认证状态机、TOTP、备用码、来源策略、翻译、存储持久性和锁恢复。`pnpm test:integration` 使用真实 HTTP/WebSocket socket 验证原生就绪、Cookie、来源判定与撤销。`pnpm test:cli` 构建真实压缩包,并用隔离 profile/Unix socket 验证交互与非交互命令。`pnpm test:browser` 用临时 profile 启动所选的 DSH 版本,验证登录、安全页、原生设置、工作区、上传/预览、SSE、WebSocket 和 HTTPS 转发链。
40
40
 
41
- 浏览器网络链路使用 Node HTTP/HTTPS 转发器。`tests/fixtures/tls/` 下的专用自签证书与私钥仅为测试夹具,不进入安装包,也不是部署凭证。聊天使用本地模型替身;不执行真实第三方授权或付费模型请求。默认浏览器为 Playwright Chromium;`DSH_TEST_BROWSER` 可选择本地浏览器程序,`DSH_TEST_BIN` 仅在报告所选精确版本(默认 `0.2.0-rc.2`)时可替换 DSH 二进制。
41
+ 浏览器网络链路使用 Node HTTP/HTTPS 转发器。`tests/fixtures/tls/` 下的专用自签证书与私钥仅为测试夹具,不进入安装包,也不是部署凭证。聊天使用本地模型替身;不执行真实第三方授权或付费模型请求。默认浏览器为 Playwright Chromium;`DSH_TEST_BROWSER` 可选择本地浏览器程序,`DSH_TEST_BIN` 仅在报告所选精确版本(默认 `0.2.1-alpha.1`)时可替换 DSH 二进制。
42
42
 
43
43
  DSH 测试运行时位于 `.cache/test-runtime/<version>`,与源码依赖分别固定。宿主服务和 React 不打入客户端 bundle。[部署指南](deployment.zh-CN.md)说明 profile 与备份规则。
44
44
 
45
45
  ## 跨版本验证
46
46
 
47
- 默认测试 DSH `0.2.0-rc.2`;`DSH_TEST_VERSION` 可选择 `0.1.7-rc.1`、`0.1.7-rc.2`、`0.2.0-rc.1` 或 `0.2.0-rc.2`,测试运行时分别位于 `.cache/test-runtime/<version>`,开发运行时位于 `.dev/runtime-<version>`。`DSH_TEST_BIN` 必须报告所选的精确版本。CI 对四个版本分别运行 CLI、安装冒烟和浏览器测试。开发类型和集成测试使用锁定的 0.2.0-rc.2 包。
47
+ 默认测试 DSH `0.2.1-alpha.1`;`DSH_TEST_VERSION` 可选择 `0.1.7-rc.1`、`0.1.7-rc.2`、`0.2.0-rc.1`、`0.2.0-rc.2` 或 `0.2.1-alpha.1`,测试运行时分别位于 `.cache/test-runtime/<version>`,开发运行时位于 `.dev/runtime-<version>`。`DSH_TEST_BIN` 必须报告所选的精确版本。CI 对五个版本分别运行 CLI、安装冒烟和浏览器测试。开发类型和集成测试使用锁定的 0.2.1-alpha.1 包。
48
48
 
49
49
  ```sh
50
50
  DSH_TEST_VERSION=0.1.7-rc.1 pnpm test:cli
@@ -53,6 +53,8 @@ DSH_TEST_VERSION=0.1.7-rc.2 pnpm test:cli
53
53
  DSH_TEST_VERSION=0.1.7-rc.2 pnpm test:browser
54
54
  DSH_TEST_VERSION=0.2.0-rc.1 pnpm test:cli
55
55
  DSH_TEST_VERSION=0.2.0-rc.1 pnpm test:browser
56
+ DSH_TEST_VERSION=0.2.0-rc.2 pnpm test:cli
57
+ DSH_TEST_VERSION=0.2.0-rc.2 pnpm test:browser
56
58
  pnpm test:cli
57
59
  pnpm test:browser
58
60
  ```
package/docs/releasing.md CHANGED
@@ -27,18 +27,18 @@ Use the version that is already on `master`:
27
27
  ```sh
28
28
  git switch master
29
29
  git pull --ff-only origin master
30
- git tag -a v0.1.3 -m "Release v0.1.3"
31
- git push origin v0.1.3
30
+ git tag -a v0.1.5 -m "Release v0.1.5"
31
+ git push origin v0.1.5
32
32
  ```
33
33
 
34
- Replace `0.1.3` in these commands with the intended version. The tag must point to a commit reachable from `master`. A mismatched tag, missing changelog entry, failed test, or mismatched existing npm archive stops the release.
34
+ Replace `0.1.5` in these commands with the intended version. The tag must point to a commit reachable from `master`. A mismatched tag, missing changelog entry, failed test, or mismatched existing npm archive stops the release.
35
35
 
36
36
  After the workflow completes, confirm the run, GitHub Release, and npm version:
37
37
 
38
38
  ```sh
39
39
  gh run list --workflow release.yml --limit 5
40
- gh release view v0.1.3
41
- npm view dsh-auth-remote@0.1.3 version dist.integrity
40
+ gh release view v0.1.5
41
+ npm view dsh-auth-remote@0.1.5 version dist.integrity
42
42
  ```
43
43
 
44
44
  The GitHub Release includes the `.tgz` and `SHA256SUMS`. Download them into the same directory and run `sha256sum -c SHA256SUMS` there to check the release asset. A failed workflow should be inspected in **Actions → Release** before retrying; npm versions are immutable, so the workflow only skips an existing version when its archive bytes match.
@@ -27,18 +27,18 @@ pnpm smoke:packed
27
27
  ```sh
28
28
  git switch master
29
29
  git pull --ff-only origin master
30
- git tag -a v0.1.3 -m "Release v0.1.3"
31
- git push origin v0.1.3
30
+ git tag -a v0.1.5 -m "Release v0.1.5"
31
+ git push origin v0.1.5
32
32
  ```
33
33
 
34
- 执行时把 `0.1.3` 换成目标版本。标签必须指向 `master` 可达的提交。标签版本不匹配、缺少更新日志条目、测试失败,或 npm 现存版本与本次压缩包字节不同,都会阻止发布。
34
+ 执行时把 `0.1.5` 换成目标版本。标签必须指向 `master` 可达的提交。标签版本不匹配、缺少更新日志条目、测试失败,或 npm 现存版本与本次压缩包字节不同,都会阻止发布。
35
35
 
36
36
  工作流结束后检查运行状态、GitHub Release 和 npm 版本:
37
37
 
38
38
  ```sh
39
39
  gh run list --workflow release.yml --limit 5
40
- gh release view v0.1.3
41
- npm view dsh-auth-remote@0.1.3 version dist.integrity
40
+ gh release view v0.1.5
41
+ npm view dsh-auth-remote@0.1.5 version dist.integrity
42
42
  ```
43
43
 
44
44
  GitHub Release 包含 `.tgz` 和 `SHA256SUMS`。把两者下载到同一个目录,在该目录运行 `sha256sum -c SHA256SUMS` 验证附件。工作流失败时先查看 **Actions → Release** 再重试;npm 版本不可覆盖,因此只有现存版本的压缩包字节与本次构建一致时,工作流才会跳过重复发布。
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dsh-auth-remote",
3
- "version": "0.1.3",
3
+ "version": "0.1.5",
4
4
  "description": "Single-user remote authentication for DeepSeek Harness: password, TOTP and revocable sessions.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -51,15 +51,14 @@
51
51
  "@deepseek-ai/schemastery": ">=3.18.4 <4"
52
52
  },
53
53
  "devDependencies": {
54
- "@deepseek-ai/cordis": "4.0.4",
55
- "@deepseek-ai/dsh-client-connection": "0.2.0-rc.2",
56
- "@deepseek-ai/dsh-client-locale": "0.2.0-rc.2",
57
- "@deepseek-ai/dsh-client-ui-settings": "0.2.0-rc.2",
58
- "@deepseek-ai/dsh-client-ui-slots": "0.2.0-rc.2",
59
- "@deepseek-ai/dsh-host-webserver": "0.2.0-rc.2",
60
- "@deepseek-ai/dsh-invariants": "0.2.0-rc.2",
61
- "@deepseek-ai/dsh-scope": "0.2.0-rc.2",
62
- "@deepseek-ai/schemastery": "3.18.4",
54
+ "@deepseek-ai/cordis": "4.0.5-alpha.1",
55
+ "@deepseek-ai/dsh-client-connection": "0.2.1-alpha.1",
56
+ "@deepseek-ai/dsh-client-locale": "0.2.1-alpha.1",
57
+ "@deepseek-ai/dsh-client-ui-settings": "0.2.1-alpha.1",
58
+ "@deepseek-ai/dsh-client-ui-slots": "0.2.1-alpha.1",
59
+ "@deepseek-ai/dsh-host-webserver": "0.2.1-alpha.1",
60
+ "@deepseek-ai/dsh-scope": "0.2.1-alpha.1",
61
+ "@deepseek-ai/schemastery": "3.18.5-alpha.1",
63
62
  "@playwright/test": "1.63.0",
64
63
  "@types/node": "24.13.6",
65
64
  "@types/qrcode": "1.5.6",
@@ -84,6 +83,15 @@
84
83
  ],
85
84
  "platform": "web",
86
85
  "immediately": true
86
+ },
87
+ "compatibility": {
88
+ "dshReleases": {
89
+ "0.1.7-rc.1": "compatible",
90
+ "0.1.7-rc.2": "compatible",
91
+ "0.2.0-rc.1": "compatible",
92
+ "0.2.0-rc.2": "compatible",
93
+ "0.2.1-alpha.1": "compatible"
94
+ }
87
95
  }
88
96
  },
89
97
  "dependencies": {