dsh-auth-remote 0.1.10 → 0.2.0
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 +21 -0
- package/CHANGELOG.zh-CN.md +21 -0
- package/CONTRIBUTING.md +3 -1
- package/CONTRIBUTING.zh-CN.md +3 -1
- package/README.md +44 -24
- package/README.zh-CN.md +30 -10
- package/cordis.patch.yml +2 -2
- package/dist/index.js +68 -0
- package/dist/index.js.map +4 -4
- package/dist/types/index.d.ts.map +1 -1
- package/dist/types/shared/dsh-support.d.ts +38 -0
- package/dist/types/shared/dsh-support.d.ts.map +1 -0
- package/docs/deployment.md +22 -20
- package/docs/deployment.zh-CN.md +22 -20
- package/docs/development.md +63 -9
- package/docs/development.zh-CN.md +63 -9
- package/docs/legacy-compatibility.md +78 -68
- package/docs/legacy-compatibility.zh-CN.md +66 -56
- package/docs/releasing.md +40 -10
- package/docs/releasing.zh-CN.md +40 -10
- package/docs/support-history.md +97 -0
- package/docs/support-history.zh-CN.md +97 -0
- package/docs/support-policy.md +87 -0
- package/docs/support-policy.zh-CN.md +87 -0
- package/examples/web-profile-auth-remote.patch.yml +2 -1
- package/package.json +22 -15
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,27 @@ This file records user-visible changes to the released package. Version numbers
|
|
|
6
6
|
|
|
7
7
|
## Unreleased
|
|
8
8
|
|
|
9
|
+
## 0.2.0 - 2026-10-19
|
|
10
|
+
|
|
11
|
+
- Regenerate stable Cordis/Schemastery lockfile resolutions and peer snapshots for clean frozen installs; shorten managed verification profiles and test real Unix socket binding at the default CI checkout length.
|
|
12
|
+
|
|
13
|
+
- Synchronize current normal/legacy dates, two-way history navigation, adaptation evidence and frozen-artifact operating guides without retiring any supported DSH version.
|
|
14
|
+
|
|
15
|
+
- Add manually maintained bilingual, bidirectional support history with exact historical evidence, archive availability and clear separation of published releases from the RC candidate.
|
|
16
|
+
|
|
17
|
+
- Add conservative ordinary/full CI planning: keep every-release CLI/smoke, fixed browser capability suites for six low-risk paths, full verification for all other changes and weekly Monday UTC checks.
|
|
18
|
+
|
|
19
|
+
- Build one release artifact, verify its producer identity across all declared CLI/smoke and complete-browser targets through a shared workflow, and gate publication on the same successful artifact.
|
|
20
|
+
|
|
21
|
+
- Add fixed-archive CLI/browser/smoke consumption with SHA-256 and package checks, restored dist, explicit suites, strict test counts and an isolated ephemeral-port smoke profile.
|
|
22
|
+
|
|
23
|
+
- Require independent profile-level native-listener disable for protected remote deployments; verify real Loader bundle skipping and plugin runtime refusal on both RC targets without listener fallback.
|
|
24
|
+
|
|
25
|
+
- Emit process-scoped startup maintenance warnings for legacy or unverified DSH versions, preserving warning history through HMR. Keep technical admission independent of dates and record no actual retirement.
|
|
26
|
+
- Verify the native DSH `0.2.1-rc.2` Search/Fetch settings over the protected remote Host, including three namespaces, test-credential redaction, persistence and session refusal, without invoking paid providers.
|
|
27
|
+
- Add candidate targets DSH `0.2.1-rc.1` and `0.2.1-rc.2`, pin development/default verification to `0.2.1-rc.2` with stable Cordis and Schemastery, and retain all eleven release targets. Correct account branches and four real host-release round trips; assert visible focus and switch thumbs on older themes. These additions do not change published `0.1.10` history.
|
|
28
|
+
- Publish bilingual support-lifecycle rules with explicit legacy dates, continued verification until actual retirement, independent technical admission and exact-version release evidence requirements.
|
|
29
|
+
|
|
9
30
|
## 0.1.10 - 2026-10-19
|
|
10
31
|
|
|
11
32
|
- Add DSH `0.2.1-alpha.4` and `0.2.1-alpha.5` support, pin development/default tests to `0.2.1-alpha.5`, and extend CLI, full browser and installation-smoke verification to all nine supported releases. Retain the remote callback and HMR isolation adaptations, exercise native host-release refresh on `0.2.1-alpha.4` and `0.2.1-alpha.5`, and declare `engines.dsh >=0.1.7-rc.1`.
|
package/CHANGELOG.zh-CN.md
CHANGED
|
@@ -6,6 +6,27 @@
|
|
|
6
6
|
|
|
7
7
|
## 未发布
|
|
8
8
|
|
|
9
|
+
## 0.2.0 - 2026-10-19
|
|
10
|
+
|
|
11
|
+
- 重新生成稳定 Cordis/Schemastery 的锁文件解析及 peer 快照,保障干净 frozen 安装;缩短受管理验证 profile,并实测默认 CI 检出路径长度下的 Unix socket 绑定。
|
|
12
|
+
|
|
13
|
+
- 同步当前正常/legacy 日期、双向历史入口、适配证据与固定归档操作指南,不退役任何仍支持的 DSH 版本。
|
|
14
|
+
|
|
15
|
+
- 新增人工维护的双语双向支持历史,区分精确历史证据、归档可获取性、已发布版本与 RC 候选。
|
|
16
|
+
|
|
17
|
+
- 新增保守普通/全量 CI 计划:全版本保留 CLI/smoke,仅六个低风险路径使用固定 browser 能力专项,其余变更及 UTC 周一定时检查全量。
|
|
18
|
+
|
|
19
|
+
- 发布仅构建一份制品,经共用工作流对全部声明版本执行 CLI/smoke 与完整 browser 并核对 producer 身份,全部成功后才发布同一归档。
|
|
20
|
+
|
|
21
|
+
- 新增固定归档 CLI/browser/smoke 消费入口,校验 SHA-256 与包身份、恢复 dist、明确 suite 和严格用例数量,smoke 使用独立临时端口 profile。
|
|
22
|
+
|
|
23
|
+
- 受保护远程部署明确要求在 profile 级独立禁用原生监听;两个 RC 实测真实 Loader 跳过 bundle 及插件自身运行拒绝均无监听回退。
|
|
24
|
+
|
|
25
|
+
- 对 legacy 或未验证 DSH 版本输出进程级启动维护提示,HMR 保留提示记录;技术准入与日期独立,本轮不登记任何实际退役。
|
|
26
|
+
- 验证 DSH `0.2.1-rc.2` 原生 Search/Fetch 设置经受保护远程 Host 的三命名空间、测试凭据脱敏、持久化及会话拒绝链路,不调用付费提供者。
|
|
27
|
+
- 新增 DSH `0.2.1-rc.1`、`0.2.1-rc.2` 候选目标,开发/默认验证固定 `0.2.1-rc.2` 并使用稳定 Cordis、Schemastery,保留全部十一版。修正账号分支和四组真实宿主版本往返切换,断言旧主题的焦点环与开关滑块可见;不扩写已发布 `0.1.10` 的历史。
|
|
28
|
+
- 发布双语支持生命周期规范,明确 legacy 日期、实际退役前持续验证、独立技术准入和精确版本发布证据要求。
|
|
29
|
+
|
|
9
30
|
## 0.1.10 - 2026-10-19
|
|
10
31
|
|
|
11
32
|
- 新增 DSH `0.2.1-alpha.4`、`0.2.1-alpha.5` 支持,开发与默认测试固定到 `0.2.1-alpha.5`,CLI、完整浏览器及安装 smoke 覆盖全部九个支持版本;保留远程回调与 HMR 隔离适配,覆盖 `0.2.1-alpha.4`、`0.2.1-alpha.5` 的原生宿主版本刷新回归,并声明 `engines.dsh >=0.1.7-rc.1`。
|
package/CONTRIBUTING.md
CHANGED
|
@@ -14,10 +14,12 @@ pnpm exec playwright install chromium
|
|
|
14
14
|
pnpm check
|
|
15
15
|
```
|
|
16
16
|
|
|
17
|
-
The [development guide](docs/development.md) explains the isolated DSH runtime and the full test boundaries. Run `pnpm pack:local` when a change affects packaging, and `pnpm smoke` when it affects installation or startup. Tests use temporary profiles;
|
|
17
|
+
The [development guide](docs/development.md) explains the isolated DSH runtime and the full test boundaries. Run `pnpm pack:local` when a change affects packaging, and `pnpm smoke` when it affects installation or startup. Tests use temporary profiles; ordinary development/smoke wrappers manage the checkout’s .dev profile. Final verification uses the fixed-archive consumer’s new marked home. Keep real account files and credentials out of the repository.
|
|
18
18
|
|
|
19
19
|
Before changing supported versions, consult the [legacy compatibility inventory](docs/legacy-compatibility.md). Review manifest peers and compatibility declarations, runtime admission, test targets, CI matrices, and user claims together. Retire runtime adaptations in the same change only when none of their applicable DSH versions remain supported; retire old plugin configuration under its own migration policy. Keep shared security checks. Update both inventory languages, both matrix views and affected entries with complete version numbers whenever compatibility code changes.
|
|
20
20
|
|
|
21
|
+
Keep the [support policy](docs/support-policy.md), both directions of [support history](docs/support-history.md), README and inventory synchronized in both languages for support changes. Use the [fixed-archive consumer](docs/development.md#consume-a-fixed-archive) for same-package verification; packaging wrappers are for preparing a new candidate.
|
|
22
|
+
|
|
21
23
|
## Open a pull request
|
|
22
24
|
|
|
23
25
|
Create a focused branch from `master`. Include the reason for the change, its user-facing effect, tests run, and any migration or deployment steps. Update English and Chinese guides together when behavior changes. Add a short entry to the Unreleased section of both changelogs. Keep generated `dist/`, `artifacts/`, runtime data, secrets, and local profiles out of commits.
|
package/CONTRIBUTING.zh-CN.md
CHANGED
|
@@ -16,7 +16,9 @@ pnpm exec playwright install chromium
|
|
|
16
16
|
pnpm check
|
|
17
17
|
```
|
|
18
18
|
|
|
19
|
-
[开发指南](docs/development.zh-CN.md)说明隔离的 DSH 运行时与完整测试范围。改动打包时执行 `pnpm pack:local`;改动安装或启动时再执行 `pnpm smoke`。测试使用临时 profile
|
|
19
|
+
[开发指南](docs/development.zh-CN.md)说明隔离的 DSH 运行时与完整测试范围。改动打包时执行 `pnpm pack:local`;改动安装或启动时再执行 `pnpm smoke`。测试使用临时 profile;普通开发/smoke 包装命令管理当前 checkout 的 .dev profile,最终验证使用固定归档运行器新建的带标记 home。真实账号文件与凭据不得进入仓库。
|
|
20
|
+
|
|
21
|
+
支持变更须同时维护[支持规范](docs/support-policy.zh-CN.md)、[双向支持历史](docs/support-history.zh-CN.md)、README 与兼容库存的两种语言。同包验证使用[固定归档运行器](docs/development.zh-CN.md#消费固定归档),打包包装命令只用于准备新候选。
|
|
20
22
|
|
|
21
23
|
## 提交 Pull Request
|
|
22
24
|
|
package/README.md
CHANGED
|
@@ -6,29 +6,49 @@ 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 DSH
|
|
9
|
+
- Linux with `/proc`, Node.js 24 or newer, and one of the exact DSH targets below. Plugin `0.2.0` adds **0.2.1-rc.1** and **0.2.1-rc.2**, with **0.2.1-rc.2** as its development 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
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
|
20
|
-
|
|
|
21
|
-
| 0.
|
|
22
|
-
| 0.
|
|
23
|
-
| 0.2.
|
|
24
|
-
| 0.2.
|
|
25
|
-
| 0.2.1-alpha.
|
|
26
|
-
| 0.2.1-alpha.
|
|
27
|
-
| 0.2.1-alpha.
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
15
|
+
Plugin **`0.2.0`** declares eleven exact targets in `dsh.compatibility.dshReleases`; final same-archive verification is recorded separately. This does not extend the published npm `0.1.10` history, whose nine declarations stop at `0.2.1-alpha.5`. `engines.dsh`, the host peer declaration and runtime version check all retain `>=0.1.7-rc.1`, with no upper bound, including prereleases. The [support policy](docs/support-policy.md) records six legacy dates and the continued support commitment until an explicit retirement release.
|
|
16
|
+
|
|
17
|
+
Find your version in the historical [DSH → plugin](docs/support-history.md#by-dsh) or [plugin → DSH](docs/support-history.md#by-plugin) tables. They separate published declarations, historical test reports, candidate verification and actual archive availability.
|
|
18
|
+
|
|
19
|
+
| Exact supported DSH release | Maintenance | Legacy since | Window | Earliest eligible retirement |
|
|
20
|
+
| --------------------------- | ----------------------------------- | ------------ | ------- | ---------------------------- |
|
|
21
|
+
| `0.1.7-rc.1` | Legacy; supported | 2026-10-19 | 14 days | 2026-11-02 |
|
|
22
|
+
| `0.1.7-rc.2` | Legacy; supported | 2026-10-19 | 14 days | 2026-11-02 |
|
|
23
|
+
| `0.2.0-rc.1` | Legacy; supported | 2026-10-19 | 21 days | 2026-11-09 |
|
|
24
|
+
| `0.2.0-rc.2` | Legacy; supported | 2026-10-19 | 21 days | 2026-11-09 |
|
|
25
|
+
| `0.2.1-alpha.1` | Legacy; supported | 2026-10-19 | 21 days | 2026-11-09 |
|
|
26
|
+
| `0.2.1-alpha.2` | Legacy; supported | 2026-10-19 | 21 days | 2026-11-09 |
|
|
27
|
+
| `0.2.1-alpha.3` | Normal support | — | — | Not announced |
|
|
28
|
+
| `0.2.1-alpha.4` | Normal support | — | — | Not announced |
|
|
29
|
+
| `0.2.1-alpha.5` | Normal support | — | — | Not announced |
|
|
30
|
+
| `0.2.1-rc.1` | Normal support | — | — | Not announced |
|
|
31
|
+
| `0.2.1-rc.2` | Normal support; development default | — | — | Not announced |
|
|
32
|
+
|
|
33
|
+
Dates use `Asia/Shanghai` at 00:00. Eligibility is not actual retirement: all eleven remain supported, and no date automatically stops the plugin or removes CI. The general window is 14 days; the four 21-day exceptions are explicit capability-boundary announcements. Associated alphas follow the entire RC line unless independently announced. Migrate toward DSH `0.2.1-rc.2` with plugin `0.2.0`; consult the exact-version distribution record before installing.
|
|
34
|
+
|
|
35
|
+
| DSH releases | Concrete IPv4 HTTP | Native public URL CLI, Web prompt and `DSH_WEB_URL` | Native IPv6 / HTTPS |
|
|
36
|
+
| ------------- | ------------------------ | --------------------------------------------------------------------------------- | ---------------------------------- |
|
|
37
|
+
| 0.1.7-rc.1 | Yes | No `--public-url`; native model-side URL remains `http://127.0.0.1:<actual-port>` | Unsupported |
|
|
38
|
+
| 0.1.7-rc.2 | Yes | No `--public-url`; native model-side URL remains `http://127.0.0.1:<actual-port>` | Unsupported |
|
|
39
|
+
| 0.2.0-rc.1 | Yes | No `--public-url`; native model-side URL remains `http://127.0.0.1:<actual-port>` | Unsupported |
|
|
40
|
+
| 0.2.0-rc.2 | Yes | No `--public-url`; native model-side URL remains `http://127.0.0.1:<actual-port>` | Unsupported |
|
|
41
|
+
| 0.2.1-alpha.1 | Yes | Yes; uses the plugin's final public root | Unsupported |
|
|
42
|
+
| 0.2.1-alpha.2 | Yes | Yes; uses the plugin's final public root | Yes, through the official listener |
|
|
43
|
+
| 0.2.1-alpha.3 | Yes | Yes; final public root in runtime context and `DSH_WEB_URL` | Yes, through the official listener |
|
|
44
|
+
| 0.2.1-alpha.4 | Yes | Yes; final public root in runtime context and `DSH_WEB_URL` | Yes, through the official listener |
|
|
45
|
+
| 0.2.1-alpha.5 | Yes | Yes; final public root in runtime context and `DSH_WEB_URL` | Yes, through the official listener |
|
|
46
|
+
| 0.2.1-rc.1 | Yes | Native public root in runtime context and `DSH_WEB_URL` | Yes, through the official listener |
|
|
47
|
+
| 0.2.1-rc.2 | Yes; development default | Native public root in runtime context and `DSH_WEB_URL` | Yes, through the official listener |
|
|
48
|
+
|
|
49
|
+
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. Missing capabilities leave authentication unavailable with a diagnostic. CI keeps CLI/smoke on all eleven versions; full plans and every release run all eleven complete browser targets. Ordinary low-risk plans use the [fixed browser selection](docs/development.md#ordinary-and-full-ci-plans).
|
|
50
|
+
|
|
51
|
+
The plugin's single-entry configuration covers all eleven supported releases. Native IPv6/TLS is available on DSH `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2`; an external HTTPS proxy can serve HTTP listeners. For source builds, see the [development guide](docs/development.md).
|
|
32
52
|
|
|
33
53
|
The [compatibility inventory](docs/legacy-compatibility.md) provides feature-to-version and version-to-feature matrices, code/test references and migration or retirement conditions.
|
|
34
54
|
|
|
@@ -38,17 +58,17 @@ With DSH installed, verify its version and install the published plugin into the
|
|
|
38
58
|
|
|
39
59
|
```sh
|
|
40
60
|
dsh --version
|
|
41
|
-
dsh plugin --profile web add dsh-auth-remote@0.
|
|
61
|
+
dsh plugin --profile web add dsh-auth-remote@0.2.0
|
|
42
62
|
dsh plugin --profile web list
|
|
43
63
|
```
|
|
44
64
|
|
|
45
|
-
Check that `dsh --version` prints `0.2.1-
|
|
65
|
+
Check that `dsh --version` prints `0.2.1-rc.2` and the plugin list includes `dsh-auth-remote@0.2.0`. These commands use DSH's default data directory. For source builds and an isolated development runtime, see the [development guide](docs/development.md).
|
|
46
66
|
|
|
47
67
|
## Configure the web profile
|
|
48
68
|
|
|
49
69
|
The minimal setup needs no profile patch. Start with `dsh web --no-open --port 13090` and use the printed `http://127.0.0.1:13090/` root. Without an explicit `publicUrl`, the plugin derives one root from the actual listener protocol, address and bound port, including `--port 0`. Unauthenticated navigation redirects to sign-in. Check `/auth-remote/ready` before relying on the service. Startup prints the listener and one distinct public root, without a native `?token=` URL.
|
|
50
70
|
|
|
51
|
-
For a public HTTPS entry, use the [deployment guide](docs/deployment.md) and [profile example](examples/web-profile-auth-remote.patch.yml), with top-level `publicUrl: https://dsh.example.com/`, `host` and `port`. DSH `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5` also support concrete IPv6 and paired top-level `tlsCert`/`tlsKey`. The URL must be an HTTP(S) root, with no credentials, child path, query or fragment. One public origin plus literal loopback is admitted. Setting a URL does not configure proxy routing or TLS.
|
|
71
|
+
For a public HTTPS entry, use the [deployment guide](docs/deployment.md) and [profile example](examples/web-profile-auth-remote.patch.yml), with top-level `publicUrl: https://dsh.example.com/`, `host` and `port`. DSH `0.2.1-alpha.2`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1`, `0.2.1-rc.2` also support concrete IPv6 and paired top-level `tlsCert`/`tlsKey`. The URL must be an HTTP(S) root, with no credentials, child path, query or fragment. One public origin plus literal loopback is admitted. Setting a URL does not configure proxy routing or TLS.
|
|
52
72
|
|
|
53
73
|
The plugin automatically declares its finalized native bridge authority in Connection's `trustedHosts`, so downstream plugins can recognize a concrete listener without an extra `--trusted-host`. If a downstream route needs the original public Host, add its path to `preserveOriginPaths`; the final public authority is then declared as well. Explicit CLI trusted hosts are retained, while the outer public-origin and sign-in checks still apply. CLI host/port and public URL override file values; TLS overrides as one complete pair. See the [migration and path rules](docs/deployment.md#configuration-priority-and-path-bases) before upgrading `allowedOrigins`: zero or one item is migrated in memory with a warning, multiple items and any explicit coexistence with `publicUrl` fail.
|
|
54
74
|
|
|
@@ -66,7 +86,7 @@ Enter one username and a password of 12–256 Unicode characters. The password i
|
|
|
66
86
|
|
|
67
87
|
Open the direct loopback URL for the minimal installation. After configuring a public origin, open `https://dsh.example.com/auth-remote/login`. Security settings inside DSH can change the password, bind or disable TOTP when policy permits, and revoke sessions. Password or factor changes revoke existing sessions. Sessions have a fixed default lifetime of 168 hours and survive service restarts.
|
|
68
88
|
|
|
69
|
-
On DSH `0.2.1-alpha.3`, `0.2.1-alpha.4` and `0.2.1-
|
|
89
|
+
On DSH `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1` and `0.2.1-rc.2`, open the sidebar account menu, then **Settings → Security & sign-in**. 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.2` expose Settings directly in the sidebar.
|
|
70
90
|
|
|
71
91
|
The sign-in page references DSH's PWA manifest. The manifest and favicons are readable before sign-in; business pages and APIs still require authentication. See the [public resource rules](docs/deployment.md#source-and-bridge-contract).
|
|
72
92
|
|
|
@@ -85,13 +105,13 @@ Security & sign-in shows the plugin username, TOTP status, this session’s sign
|
|
|
85
105
|
|
|
86
106
|
## Sign in to an official DeepSeek account
|
|
87
107
|
|
|
88
|
-
Manual callbacks are forward-admitted from `>=0.2.1-alpha.3` using SemVer with prereleases included, and require native capabilities plus `manualAccountLogin: true`. Full feature verification targets **0.2.1-alpha.3**, **0.2.1-alpha.4** and **0.2.1-
|
|
108
|
+
Manual callbacks are forward-admitted from `>=0.2.1-alpha.3` using SemVer with prereleases included, and require native capabilities plus `manualAccountLogin: true`. Full feature verification targets **0.2.1-alpha.3**, **0.2.1-alpha.4**, **0.2.1-alpha.5**, **0.2.1-rc.1** and **0.2.1-rc.2**; future releases need exact regression before being called verified. In its account menu, **Sign in** first opens an instruction dialog; it does not start authorization immediately. Click **Open sign-in page** to open the official page in a new tab. After approval, that tab may show a connection error or 404 at a loopback address. Copy its entire address, including `code` and `state`, paste it into **Full callback address**, and click **Confirm sign-in**. Keep the original DSH page open throughout. If the popup is blocked, use the dialog's authorization link.
|
|
89
109
|
|
|
90
110
|
In **Settings → Security & sign-in → Sign-in preferences**, the remote DeepSeek sign-in switch defaults to on. Native Settings saves it to the current profile override; new authorizations on this page use the accepted value immediately and restarts preserve it. Failed saves show an error. Turning it off restores native entries for new attempts, preserves admitted manual attempts and existing official-account credentials, and does not establish native public-callback support. Other open pages need no active synchronization; a stale page starting authorization receives disabled feedback and advice to refresh.
|
|
91
111
|
|
|
92
112
|
This manual handoff needs no local listener, SSH tunnel or browser extension. The loopback address is an authorization return address; its page does not need to load. The plugin parses the pasted URL and delivers the callback inside DSH, retaining native state validation, PKCE exchange and credential storage. It never fetches the pasted address. Pending authorization belongs to the initiating remote session, lasts at most ten minutes and is cancelled when dismissed or the session is revoked. Expired or failed authorization must be restarted. 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.2` retain their existing UI and API-key setup.
|
|
93
113
|
|
|
94
|
-
On DSH `0.2.1-alpha.3`, `0.2.1-alpha.4` and `0.2.1-
|
|
114
|
+
On DSH `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5`, `0.2.1-rc.1` and `0.2.1-rc.2`, the dialog also offers **Use API key** before authorization begins. It opens the native credential editor and continues setup until the key is saved or the user chooses to defer. The same option is available from the account menu. During active authorization, the secondary button cancels that attempt instead.
|
|
95
115
|
|
|
96
116
|
## Put a proxy in front
|
|
97
117
|
|
package/README.zh-CN.md
CHANGED
|
@@ -6,13 +6,31 @@ DeepSeek Harness(DSH)的单用户远程登录插件,提供密码、TOTP、
|
|
|
6
6
|
|
|
7
7
|
## 前置条件
|
|
8
8
|
|
|
9
|
-
- Linux(含 `/proc`)、Node.js 24
|
|
9
|
+
- Linux(含 `/proc`)、Node.js 24 或更高版本,以及下表某个精确 DSH 目标。插件 `0.2.0` 新增 **0.2.1-rc.1**、**0.2.1-rc.2**,开发默认 **0.2.1-rc.2**。仅从源码构建时需要 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
|
-
`dsh.compatibility.dshReleases`
|
|
15
|
+
插件 **`0.2.0`** 在 `dsh.compatibility.dshReleases` 声明十一个精确目标,最终同包验证结果另记执行记录。这不扩写已发布 npm `0.1.10` 的历史,其九版声明最后为 `0.2.1-alpha.5`。`engines.dsh`、宿主 peer 声明和运行时检查仍使用 `>=0.1.7-rc.1`,不设上限且包含预发布。[支持规范](docs/support-policy.zh-CN.md)记录六版 legacy 日期与明确实际退役发布前继续支持的承诺。
|
|
16
|
+
|
|
17
|
+
按历史 [DSH → 插件](docs/support-history.zh-CN.md#by-dsh)或[插件 → DSH](docs/support-history.zh-CN.md#by-plugin)表查询自己的版本。表中区分已发布声明、历史测试报告、候选实测与实际归档可获取性。
|
|
18
|
+
|
|
19
|
+
| 精确支持的 DSH 版本 | 维护状态 | Legacy 起算 | 窗口 | 最早退役资格日 |
|
|
20
|
+
| ------------------- | ------------------ | ----------- | ----- | -------------- |
|
|
21
|
+
| `0.1.7-rc.1` | Legacy;继续支持 | 2026-10-19 | 14 日 | 2026-11-02 |
|
|
22
|
+
| `0.1.7-rc.2` | Legacy;继续支持 | 2026-10-19 | 14 日 | 2026-11-02 |
|
|
23
|
+
| `0.2.0-rc.1` | Legacy;继续支持 | 2026-10-19 | 21 日 | 2026-11-09 |
|
|
24
|
+
| `0.2.0-rc.2` | Legacy;继续支持 | 2026-10-19 | 21 日 | 2026-11-09 |
|
|
25
|
+
| `0.2.1-alpha.1` | Legacy;继续支持 | 2026-10-19 | 21 日 | 2026-11-09 |
|
|
26
|
+
| `0.2.1-alpha.2` | Legacy;继续支持 | 2026-10-19 | 21 日 | 2026-11-09 |
|
|
27
|
+
| `0.2.1-alpha.3` | 正常支持 | — | — | 未公告 |
|
|
28
|
+
| `0.2.1-alpha.4` | 正常支持 | — | — | 未公告 |
|
|
29
|
+
| `0.2.1-alpha.5` | 正常支持 | — | — | 未公告 |
|
|
30
|
+
| `0.2.1-rc.1` | 正常支持 | — | — | 未公告 |
|
|
31
|
+
| `0.2.1-rc.2` | 正常支持;开发默认 | — | — | 未公告 |
|
|
32
|
+
|
|
33
|
+
日期按 `Asia/Shanghai` 当日 00:00 计算。资格日不等于实际退役:十一版继续支持,没有日期自动停用插件或删除 CI。通用窗口为 14 日,四个 21 日例外属于明确的能力边界公告。关联 Alpha 跟随整条 RC 线,独立公告除外。迁移目标为 DSH `0.2.1-rc.2` 与插件 `0.2.0`,安装前核对精确版本的分发记录。
|
|
16
34
|
|
|
17
35
|
| DSH 版本 | 具体 IPv4 HTTP | 原生公开 URL CLI、Web 提示与 `DSH_WEB_URL` | 原生 IPv6 / HTTPS |
|
|
18
36
|
| ------------- | -------------- | -------------------------------------------------------------------- | ----------------- |
|
|
@@ -25,10 +43,12 @@ DeepSeek Harness(DSH)的单用户远程登录插件,提供密码、TOTP、
|
|
|
25
43
|
| 0.2.1-alpha.3 | 支持 | 支持;最终公开根地址写入运行时上下文与 `DSH_WEB_URL` | 通过官方监听支持 |
|
|
26
44
|
| 0.2.1-alpha.4 | 支持 | 支持;最终公开根地址写入运行时上下文与 `DSH_WEB_URL` | 通过官方监听支持 |
|
|
27
45
|
| 0.2.1-alpha.5 | 支持 | 支持;最终公开根地址写入运行时上下文与 `DSH_WEB_URL` | 通过官方监听支持 |
|
|
46
|
+
| 0.2.1-rc.1 | 支持 | 原生公开根地址写入运行时上下文与 `DSH_WEB_URL` | 通过官方监听支持 |
|
|
47
|
+
| 0.2.1-rc.2 | 支持;开发默认 | 原生公开根地址写入运行时上下文与 `DSH_WEB_URL` | 通过官方监听支持 |
|
|
28
48
|
|
|
29
|
-
后续版本属于向前准入,并不宣称已经逐版测试。插件仍检查必需的 WebServer/Connection 接口、宿主包实例一致性和原生认证交换。缺少能力时认证入口保持不可用并给出诊断。CI
|
|
49
|
+
后续版本属于向前准入,并不宣称已经逐版测试。插件仍检查必需的 WebServer/Connection 接口、宿主包实例一致性和原生认证交换。缺少能力时认证入口保持不可用并给出诊断。CI 对十一版保留 CLI/smoke;全量计划与每次发布运行十一版完整 browser,普通低风险计划使用[固定 browser 选择](docs/development.zh-CN.md#普通与全量-ci-计划)。
|
|
30
50
|
|
|
31
|
-
|
|
51
|
+
十一版支持目标均使用插件的单入口配置。原生 IPv6/TLS 在 DSH `0.2.1-alpha.2`、`0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2` 可用;HTTP 监听可由外部 HTTPS 代理提供入口。源码构建参见[开发指南](docs/development.zh-CN.md)。
|
|
32
52
|
|
|
33
53
|
[兼容维护清单](docs/legacy-compatibility.zh-CN.md)提供功能到版本、版本到功能的双向矩阵,并关联实现、测试与迁移退役条件。
|
|
34
54
|
|
|
@@ -38,17 +58,17 @@ DeepSeek Harness(DSH)的单用户远程登录插件,提供密码、TOTP、
|
|
|
38
58
|
|
|
39
59
|
```sh
|
|
40
60
|
dsh --version
|
|
41
|
-
dsh plugin --profile web add dsh-auth-remote@0.
|
|
61
|
+
dsh plugin --profile web add dsh-auth-remote@0.2.0
|
|
42
62
|
dsh plugin --profile web list
|
|
43
63
|
```
|
|
44
64
|
|
|
45
|
-
确认 `dsh --version` 输出 `0.2.1-
|
|
65
|
+
确认 `dsh --version` 输出 `0.2.1-rc.2`,且插件列表中有 `dsh-auth-remote@0.2.0`。这些命令使用 DSH 默认数据目录。源码构建及隔离开发运行时参见[开发指南](docs/development.zh-CN.md)。
|
|
46
66
|
|
|
47
67
|
## 配置 web profile
|
|
48
68
|
|
|
49
69
|
最小安装无需修改 profile 补丁。用 `dsh web --no-open --port 13090` 启动,使用终端打印的 `http://127.0.0.1:13090/` 根地址。未显式设置 `publicUrl` 时,插件根据监听的实际协议、地址和绑定端口生成唯一根地址,包含 `--port 0` 的实际结果。未登录导航跳转登录页;使用服务前检查 `/auth-remote/ready`。启动输出包含监听地址和一个不同的公开根地址,不含原生 `?token=` URL。
|
|
50
70
|
|
|
51
|
-
公网 HTTPS 入口请使用[部署指南](docs/deployment.zh-CN.md)和 [profile 示例](examples/web-profile-auth-remote.patch.yml),设置顶层 `publicUrl: https://dsh.example.com/`、`host`、`port`。DSH `0.2.1-alpha.2`、`0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5` 还支持具体 IPv6 和成对的顶层 `tlsCert`/`tlsKey`。URL 必须是 HTTP(S) 根地址,不能带凭据、子路径、查询或片段。准入范围是唯一公开来源加字面回环。配置 URL 不会配置代理路由或 TLS。
|
|
71
|
+
公网 HTTPS 入口请使用[部署指南](docs/deployment.zh-CN.md)和 [profile 示例](examples/web-profile-auth-remote.patch.yml),设置顶层 `publicUrl: https://dsh.example.com/`、`host`、`port`。DSH `0.2.1-alpha.2`、`0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2` 还支持具体 IPv6 和成对的顶层 `tlsCert`/`tlsKey`。URL 必须是 HTTP(S) 根地址,不能带凭据、子路径、查询或片段。准入范围是唯一公开来源加字面回环。配置 URL 不会配置代理路由或 TLS。
|
|
52
72
|
|
|
53
73
|
插件自动将定稿的原生桥接 authority 登记到 Connection 的 `trustedHosts`,下游插件无需额外 `--trusted-host` 即可识别具体监听地址。下游路由若需要原始公网 Host,可把路径加入 `preserveOriginPaths`,此时也自动登记最终公开 authority。显式 CLI trusted hosts 继续保留,外层公开来源与登录校验仍然生效。CLI 的 host/port 和公开 URL 覆盖文件值;TLS 按完整一对覆盖。升级 `allowedOrigins` 前阅读[迁移和路径规则](docs/deployment.zh-CN.md#配置优先级与路径基准):零项或单项在内存迁移并告警,多项及任意显式新旧字段共存报错。
|
|
54
74
|
|
|
@@ -66,7 +86,7 @@ dsh plugin --profile web exec dsh-auth-remote init --lang zh
|
|
|
66
86
|
|
|
67
87
|
最小化安装时访问本机回环地址;配置公网入口后访问 `https://dsh.example.com/auth-remote/login`。DSH 内的安全设置可以修改密码、绑定 TOTP、在策略允许时关闭 TOTP,以及撤销会话。密码或第二因素变更会撤销已有会话。会话默认固定有效 168 小时,服务重启后仍保留。
|
|
68
88
|
|
|
69
|
-
DSH `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.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.2` 从侧栏直接打开设置。
|
|
89
|
+
DSH `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2` 从侧栏账号菜单进入 **设置 → 安全与登录**;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.2` 从侧栏直接打开设置。
|
|
70
90
|
|
|
71
91
|
登录页引用 DSH 的 PWA manifest,manifest 与 favicon 在登录前即可读取;业务页面和 API 仍需认证。具体范围见[公开资源规则](docs/deployment.zh-CN.md#来源与桥接契约)。
|
|
72
92
|
|
|
@@ -85,13 +105,13 @@ dsh plugin --profile web exec dsh-auth-remote revoke-sessions --lang zh
|
|
|
85
105
|
|
|
86
106
|
## 登录 DeepSeek 官方账号
|
|
87
107
|
|
|
88
|
-
手动回填按 SemVer(包含预发布)从 `>=0.2.1-alpha.3` 前向准入,还须具备必要原生 API 且 `manualAccountLogin: true`。完整功能实测目标为 **0.2.1-alpha.3**、**0.2.1-alpha.4**、**0.2.1-alpha.5**;未来版本须精确回归后才宣称已验证。账号菜单中的“登录”先打开步骤说明弹窗,不会立即发起授权。点击“打开登录页”,在新标签页完成官方登录;授权后该标签页可能在回环地址显示连接失败或 404。复制地址栏中的完整 URL(包含 `code` 和 `state`),粘贴到“完整回调地址”,再点击“确认登录”。整个过程中保留原 DSH 页面;弹窗被浏览器拦截时,可使用弹窗内的授权链接。
|
|
108
|
+
手动回填按 SemVer(包含预发布)从 `>=0.2.1-alpha.3` 前向准入,还须具备必要原生 API 且 `manualAccountLogin: true`。完整功能实测目标为 **0.2.1-alpha.3**、**0.2.1-alpha.4**、**0.2.1-alpha.5**、**0.2.1-rc.1**、**0.2.1-rc.2**;未来版本须精确回归后才宣称已验证。账号菜单中的“登录”先打开步骤说明弹窗,不会立即发起授权。点击“打开登录页”,在新标签页完成官方登录;授权后该标签页可能在回环地址显示连接失败或 404。复制地址栏中的完整 URL(包含 `code` 和 `state`),粘贴到“完整回调地址”,再点击“确认登录”。整个过程中保留原 DSH 页面;弹窗被浏览器拦截时,可使用弹窗内的授权链接。
|
|
89
109
|
|
|
90
110
|
在 **设置 → 安全与登录 → 登录配置** 中切换“远程 DeepSeek 账号登录”,默认开启。保存通过原生 Settings 写入当前 profile override,当前页新授权立即采用最新值,重启后保留;保存失败会显示错误。关闭只恢复新授权的原生入口,不取消已接纳的手动授权、不退出已有官方账号,也不承诺原生公网回调可用。其他已打开页面无需主动同步;旧页新建授权会提示关闭并建议刷新。
|
|
91
111
|
|
|
92
112
|
手动回填无需本地监听器、SSH 隧道或浏览器扩展。回环地址用于承载授权结果,页面无需正常打开。插件只解析粘贴的 URL,在 DSH 内部分发回调,保留原生 state 校验、PKCE 兑换与凭据存储,不会请求粘贴的地址。待完成授权绑定发起操作的远程会话,最长有效期为十分钟;关闭弹窗或撤销该会话会取消待完成授权。过期或失败后须重新开始。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.2` 保留原有界面与 API Key 设置。
|
|
93
113
|
|
|
94
|
-
DSH `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5` 的弹窗在授权开始前也提供“使用 API Key”,点击后进入原生凭据编辑器,直到保存密钥或用户选择“稍后配置”才结束引导;账号菜单中也保留同一入口。授权进行中时,次要按钮用于取消本次授权。
|
|
114
|
+
DSH `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`、`0.2.1-rc.1`、`0.2.1-rc.2` 的弹窗在授权开始前也提供“使用 API Key”,点击后进入原生凭据编辑器,直到保存密钥或用户选择“稍后配置”才结束引导;账号菜单中也保留同一入口。授权进行中时,次要按钮用于取消本次授权。
|
|
95
115
|
|
|
96
116
|
## 接入反向代理
|
|
97
117
|
|
package/cordis.patch.yml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# Bundle baseline: replace the native listener with the authenticated WebServer.
|
|
2
2
|
# The plugin reads the listener address from the official web-startup service.
|
|
3
|
-
#
|
|
4
|
-
# bundle
|
|
3
|
+
# Remote deployments must also disable this row in the independent profile patch.
|
|
4
|
+
# A skipped bundle cannot apply this patch or protect the listener itself.
|
|
5
5
|
- id: webserver
|
|
6
6
|
disabled: true
|
|
7
7
|
|
package/dist/index.js
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
// src/index.ts
|
|
2
2
|
import { Service } from "@deepseek-ai/cordis";
|
|
3
|
+
import { readFileSync as readFileSync3 } from "node:fs";
|
|
4
|
+
import { createRequire as createRequire2 } from "node:module";
|
|
3
5
|
import { basename } from "node:path";
|
|
4
6
|
|
|
5
7
|
// src/adapters/dsh/compatibility.ts
|
|
@@ -2904,7 +2906,72 @@ var ManualAccountLogin = class {
|
|
|
2904
2906
|
}
|
|
2905
2907
|
};
|
|
2906
2908
|
|
|
2909
|
+
// src/shared/dsh-support.ts
|
|
2910
|
+
function legacy(version, windowDays, eligibleRetirement) {
|
|
2911
|
+
return {
|
|
2912
|
+
state: "legacy",
|
|
2913
|
+
version,
|
|
2914
|
+
legacySince: "2026-10-19",
|
|
2915
|
+
windowDays,
|
|
2916
|
+
eligibleRetirement,
|
|
2917
|
+
migrationTarget: "0.2.1-rc.2"
|
|
2918
|
+
};
|
|
2919
|
+
}
|
|
2920
|
+
var LEGACY_DSH_RELEASES = [
|
|
2921
|
+
legacy("0.1.7-rc.1", 14, "2026-11-02"),
|
|
2922
|
+
legacy("0.1.7-rc.2", 14, "2026-11-02"),
|
|
2923
|
+
legacy("0.2.0-rc.1", 21, "2026-11-09"),
|
|
2924
|
+
legacy("0.2.0-rc.2", 21, "2026-11-09"),
|
|
2925
|
+
legacy("0.2.1-alpha.1", 21, "2026-11-09"),
|
|
2926
|
+
legacy("0.2.1-alpha.2", 21, "2026-11-09")
|
|
2927
|
+
];
|
|
2928
|
+
var RETIRED_DSH_RELEASES = [];
|
|
2929
|
+
var lifecycle = [...LEGACY_DSH_RELEASES, ...RETIRED_DSH_RELEASES];
|
|
2930
|
+
function classifyDshSupport(version, declared, records = lifecycle) {
|
|
2931
|
+
if (declared.has(version)) {
|
|
2932
|
+
const record3 = records.find(
|
|
2933
|
+
(item) => item.version === version && item.state === "legacy"
|
|
2934
|
+
);
|
|
2935
|
+
return record3 ? { state: "legacy", version, record: record3 } : { state: "supported", version };
|
|
2936
|
+
}
|
|
2937
|
+
const record2 = records.find(
|
|
2938
|
+
(item) => item.version === version && item.state === "retired"
|
|
2939
|
+
);
|
|
2940
|
+
return record2 ? { state: "retired", version, record: record2 } : { state: "unverified", version };
|
|
2941
|
+
}
|
|
2942
|
+
function dshSupportWarning(support) {
|
|
2943
|
+
const guides = "See docs/support-policy.md and docs/support-history.md.";
|
|
2944
|
+
if (support.state === "supported") return;
|
|
2945
|
+
if (support.state === "legacy") {
|
|
2946
|
+
const record2 = support.record;
|
|
2947
|
+
return `auth-remote: DSH ${support.version} is legacy since ${record2.legacySince}; earliest eligible retirement ${record2.eligibleRetirement} (Asia/Shanghai, ${record2.windowDays} calendar days). Support continues until an explicit retirement release. Migrate to DSH ${record2.migrationTarget} with a supporting plugin release. ${guides}`;
|
|
2948
|
+
}
|
|
2949
|
+
if (support.state === "retired") {
|
|
2950
|
+
const record2 = support.record;
|
|
2951
|
+
return `auth-remote: DSH ${support.version} retired on ${record2.retiredOn} in plugin ${record2.effectivePlugin}; last supported plugin ${record2.lastSupportedPlugin}. No current compatibility commitment; technical checks still apply. Upgrade to DSH ${record2.migrationTarget} with a supporting plugin release, or consult the historical installation guidance. ${guides}`;
|
|
2952
|
+
}
|
|
2953
|
+
return `auth-remote: DSH ${support.version} has no current exact-version support commitment. Technical admission does not establish verified compatibility. Select a declared DSH release and a supporting plugin release. ${guides}`;
|
|
2954
|
+
}
|
|
2955
|
+
var warningKey = /* @__PURE__ */ Symbol.for("dsh-auth-remote.support-warnings");
|
|
2956
|
+
function warnDshSupport(support, write = console.warn) {
|
|
2957
|
+
const message = dshSupportWarning(support);
|
|
2958
|
+
if (!message) return false;
|
|
2959
|
+
const processState = globalThis;
|
|
2960
|
+
const warned = processState[warningKey] ??= /* @__PURE__ */ new Set();
|
|
2961
|
+
const key = `${support.version}:${support.state}`;
|
|
2962
|
+
if (warned.has(key)) return false;
|
|
2963
|
+
warned.add(key);
|
|
2964
|
+
write(message);
|
|
2965
|
+
return true;
|
|
2966
|
+
}
|
|
2967
|
+
|
|
2907
2968
|
// src/index.ts
|
|
2969
|
+
var ownManifest = JSON.parse(
|
|
2970
|
+
readFileSync3(createRequire2(import.meta.url).resolve("dsh-auth-remote/package.json"), "utf8")
|
|
2971
|
+
);
|
|
2972
|
+
var declaredDshReleases = new Set(
|
|
2973
|
+
Object.entries(ownManifest.dsh.compatibility.dshReleases).filter(([, state]) => state === "compatible").map(([version]) => version)
|
|
2974
|
+
);
|
|
2908
2975
|
var name = "auth-remote";
|
|
2909
2976
|
async function disposeResources(disposers) {
|
|
2910
2977
|
const errors = [];
|
|
@@ -2938,6 +3005,7 @@ var AuthRemoteWebServer = class extends GuardedWebServer {
|
|
|
2938
3005
|
super(ctx, config, gate);
|
|
2939
3006
|
this.pending = config;
|
|
2940
3007
|
this.switchGate = gate;
|
|
3008
|
+
warnDshSupport(classifyDshSupport(config.capabilities.version, declaredDshReleases));
|
|
2941
3009
|
installAuthenticatedHostCapability(ctx, config.capabilities.version);
|
|
2942
3010
|
if (config.legacyWarning)
|
|
2943
3011
|
console.warn("auth-remote: allowedOrigins is deprecated; use publicUrl with one root URL");
|