dsh-auth-remote 0.1.2 → 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,19 @@ 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
+
17
+ ## 0.1.3 - 2026-09-30
18
+
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.
20
+ - Use DSH 0.2.0-rc.2 as the default development, test, and release verification runtime; update pinned development dependencies and English/Chinese setup guides.
21
+ - Match the chat completion status used by both older DSH runtimes and 0.2.0-rc.2 in the HTTPS forwarding regression.
22
+ - Coordinate session-monitor redirects with security changes so a successful update retains its sign-in message and newly issued backup codes remain visible until acknowledged. Pending-operation protection expires after 30 seconds.
23
+
11
24
  ## 0.1.2 - 2026-09-29
12
25
 
13
26
  - Align login and security settings with DSH typography, neutral colors, controls, and light/dark themes.
@@ -8,6 +8,19 @@
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
+
17
+ ## 0.1.3 - 2026-09-30
18
+
19
+ - 验证 DSH 0.2.0-rc.2,将其加入 CLI、安装冒烟和浏览器 CI 矩阵,并保留之前已测试的所有版本。
20
+ - 默认开发、测试和发布验证运行时升级为 DSH 0.2.0-rc.2,同步更新锁定开发依赖及中英文安装指南。
21
+ - HTTPS 转发回归兼容旧版 DSH 与 0.2.0-rc.2 的聊天完成状态文案。
22
+ - 协调会话监控与安全变更的登录跳转,保留成功更新提示,并让新生成的备用码在确认保存前保持可见;操作等待期间的保护最多持续 30 秒。
23
+
11
24
  ## 0.1.2 - 2026-09-29
12
25
 
13
26
  - 登录页和安全设置对齐 DSH 的字体、灰阶、控件与浅色/深色主题。
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**, or **0.2.0-rc.1**. 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.2 is tested against DSH **0.1.7-rc.1**, **0.1.7-rc.2**, and **0.2.0-rc.1**. 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 and browser regressions on all three 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
- These compatibility and theme changes are available starting with plugin **0.1.2**. Upgrade older plugin installations to 0.1.2 or newer when using DSH 0.2.0-rc.1. 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.2
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.1` (or another tested version listed above) and the plugin list includes `dsh-auth-remote@0.1.2`. 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** 运行时。仅从源码构建时需要 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.2 已测试 DSH **0.1.7-rc.1**、**0.1.7-rc.2** 和 **0.2.0-rc.1**。宿主 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.2** 开始提供。使用 DSH 0.2.0-rc.1 时,请将旧插件升级到 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.2
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.1`(或上文列出的其他已测试版本),且插件列表中有 `dsh-auth-remote@0.1.2`。这些命令使用 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
 
package/dist/client.js CHANGED
@@ -2165,7 +2165,42 @@ function assertRemoteHostCapability(ctx) {
2165
2165
  var import_react = require("react");
2166
2166
  var import_qrcode = __toESM(require_browser(), 1);
2167
2167
 
2168
+ // src/client/settings/navigation.ts
2169
+ var LoginNavigation = class {
2170
+ constructor(assign) {
2171
+ this.assign = assign;
2172
+ }
2173
+ assign;
2174
+ holds = 0;
2175
+ expired = false;
2176
+ navigating = false;
2177
+ hold(timeoutMs) {
2178
+ this.holds++;
2179
+ let active = true;
2180
+ let timer;
2181
+ const release = () => {
2182
+ if (!active) return;
2183
+ active = false;
2184
+ clearTimeout(timer);
2185
+ this.holds--;
2186
+ if (this.holds === 0 && this.expired) this.go("expired");
2187
+ };
2188
+ if (timeoutMs !== void 0) timer = setTimeout(release, timeoutMs);
2189
+ return release;
2190
+ }
2191
+ go(reason) {
2192
+ if (this.navigating) return;
2193
+ if (reason === "expired" && this.holds > 0) {
2194
+ this.expired = true;
2195
+ return;
2196
+ }
2197
+ this.navigating = true;
2198
+ this.assign(reason);
2199
+ }
2200
+ };
2201
+
2168
2202
  // src/client/settings/api.ts
2203
+ var loginNavigation = new LoginNavigation((reason) => location.assign(loginLocation(reason)));
2169
2204
  var SettingsFailure = class extends Error {
2170
2205
  constructor(status, code, retryAfter) {
2171
2206
  super(code);
@@ -2185,8 +2220,11 @@ function loginLocation(reason = "expired") {
2185
2220
  target.searchParams.set("reason", reason);
2186
2221
  return target.pathname + target.search;
2187
2222
  }
2223
+ function holdLoginRedirect(timeoutMs) {
2224
+ return loginNavigation.hold(timeoutMs);
2225
+ }
2188
2226
  function goToLogin(reason = "expired") {
2189
- location.assign(loginLocation(reason));
2227
+ loginNavigation.go(reason);
2190
2228
  }
2191
2229
  async function authRequest(path, body) {
2192
2230
  const response = await fetch(path, {
@@ -2244,7 +2282,10 @@ var draft = {
2244
2282
  message: null,
2245
2283
  fields: {}
2246
2284
  };
2285
+ var releaseBackupCodesRedirect;
2247
2286
  function resetDraft() {
2287
+ releaseBackupCodesRedirect?.();
2288
+ releaseBackupCodesRedirect = void 0;
2248
2289
  draft = { panel: null, binding: null, backupCodes: null, message: null, fields: {} };
2249
2290
  }
2250
2291
  function TextField(props) {
@@ -2327,6 +2368,7 @@ function SecuritySection({
2327
2368
  }, []);
2328
2369
  async function submit(operation, done) {
2329
2370
  if (busy) return;
2371
+ const release = holdLoginRedirect(3e4);
2330
2372
  setBusy(true);
2331
2373
  setMessage(null);
2332
2374
  try {
@@ -2335,6 +2377,7 @@ function SecuritySection({
2335
2377
  if (isUnauthorized(error)) goToLogin();
2336
2378
  else setMessage(settingsError(error));
2337
2379
  } finally {
2380
+ release();
2338
2381
  setBusy(false);
2339
2382
  }
2340
2383
  }
@@ -2358,8 +2401,8 @@ function SecuritySection({
2358
2401
  {
2359
2402
  className: "auth-remote-button",
2360
2403
  onClick: () => {
2361
- resetDraft();
2362
2404
  goToLogin("updated");
2405
+ resetDraft();
2363
2406
  },
2364
2407
  children: t("settingsBackupSaved")
2365
2408
  }
@@ -2592,7 +2635,14 @@ function SecuritySection({
2592
2635
  challenge: binding.challenge,
2593
2636
  code: data.get("code")
2594
2637
  }),
2595
- (result) => setBackupCodes(result.backupCodes)
2638
+ (result) => {
2639
+ if (!sectionRef.current?.isConnected) {
2640
+ goToLogin("updated");
2641
+ return;
2642
+ }
2643
+ releaseBackupCodesRedirect ??= holdLoginRedirect();
2644
+ setBackupCodes(result.backupCodes);
2645
+ }
2596
2646
  );
2597
2647
  },
2598
2648
  children: [