dsh-auth-remote 0.1.10 → 0.3.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 +31 -0
- package/CHANGELOG.zh-CN.md +31 -0
- package/CONTRIBUTING.md +5 -1
- package/CONTRIBUTING.zh-CN.md +5 -1
- package/README.md +22 -24
- package/README.zh-CN.md +22 -24
- package/cordis.patch.yml +2 -2
- package/dist/client.js +2 -2
- package/dist/client.js.map +1 -1
- package/dist/index.js +102 -38
- package/dist/index.js.map +4 -4
- package/dist/types/adapters/dsh/compatibility.d.ts +1 -1
- package/dist/types/adapters/dsh/compatibility.d.ts.map +1 -1
- package/dist/types/adapters/dsh/runtime-capabilities.d.ts +6 -11
- package/dist/types/adapters/dsh/runtime-capabilities.d.ts.map +1 -1
- package/dist/types/config.d.ts +2 -2
- package/dist/types/config.d.ts.map +1 -1
- package/dist/types/http/account-login.d.ts.map +1 -1
- 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 +25 -21
- package/docs/deployment.zh-CN.md +25 -21
- package/docs/development.md +80 -23
- package/docs/development.zh-CN.md +80 -23
- package/docs/legacy-compatibility.md +106 -79
- package/docs/legacy-compatibility.zh-CN.md +106 -79
- package/docs/releasing.md +46 -10
- package/docs/releasing.zh-CN.md +46 -10
- package/docs/reverse-proxy.md +2 -2
- package/docs/reverse-proxy.zh-CN.md +2 -2
- package/docs/support-history.md +103 -0
- package/docs/support-history.zh-CN.md +103 -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 +3 -2
- package/package.json +26 -23
package/docs/releasing.zh-CN.md
CHANGED
|
@@ -2,10 +2,14 @@
|
|
|
2
2
|
|
|
3
3
|
[English](releasing.md)
|
|
4
4
|
|
|
5
|
-
每次发布都从已通过检查的 `master` 提交开始。`vX.Y.Z` 标签必须与 `package.json`
|
|
5
|
+
每次发布都从已通过检查的 `master` 提交开始。`vX.Y.Z` 标签必须与 `package.json` 中的稳定版本以及两份更新日志的日期条目一致。标签工作流先核对标签与 master 祖先关系,只构建一个 npm 压缩包,对全部声明的 DSH 版本验证该包,再核对或发布 npm 版本,并创建包含相同压缩包和 `SHA256SUMS` 的 GitHub Release。
|
|
6
|
+
|
|
7
|
+
七版支持迁移归入未发布候选 `0.3.1`。发布前须验证最终归档,既有 npm 版本不可重发。更新日志与 `retiredOn: 2026-10-28` 记录准备日期,不证明 registry 已发布。
|
|
6
8
|
|
|
7
9
|
发布准备中修改支持版本前,先复核 [Legacy 兼容维护清单](legacy-compatibility.zh-CN.md),共同检查 peers、兼容声明、运行时准入、测试目标、CI 和指南。同次删除与支持集合无交集的专属运行时适配,保留共享安全逻辑;旧插件配置退役有独立条件。打包前同步更新并人工核对中英文清单、两个维度的矩阵及完整版本号。
|
|
8
10
|
|
|
11
|
+
打包前同步维护双语 README、[DSH → 插件](support-history.zh-CN.md#by-dsh)和[插件 → DSH](support-history.zh-CN.md#by-plugin)历史及库存。本次 `0.3.1` 迁移保持两份 support-policy 原样,作为前一发布记录。保留历史行/锚点,区分已发布 `0.2.0` 和未发布候选,不引用不存在的候选 tag 作为已核实证据。
|
|
12
|
+
|
|
9
13
|
## 准备版本
|
|
10
14
|
|
|
11
15
|
将 `package.json` 更新为 `X.Y.Z`,把两份更新日志中用户可见的“未发布”变更移入 `## X.Y.Z - YYYY-MM-DD`,同时更新带版本号的安装示例。创建 Pull Request,等待 `CI Verify` 通过,合入后再等待 `master` 检查通过。检查尚未结束时不要打标签。
|
|
@@ -15,12 +19,44 @@
|
|
|
15
19
|
```sh
|
|
16
20
|
pnpm install --frozen-lockfile
|
|
17
21
|
pnpm exec playwright install chromium
|
|
18
|
-
pnpm check
|
|
19
|
-
pnpm
|
|
20
|
-
pnpm
|
|
22
|
+
pnpm check:static
|
|
23
|
+
pnpm test:unit
|
|
24
|
+
pnpm exec tsx --test tests/integration/*.test.ts
|
|
25
|
+
node scripts/pack.mjs
|
|
26
|
+
node scripts/packed-artifact.mjs record
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
生产及全部消费验证使用 Node.js 24。直接集成测试命令复用静态检查的构建,`pack.mjs` 只生成一次归档,随后 `packed-artifact.mjs record` 写入摘要和精确全量矩阵。对全部声明目标串行消费这份冻结归档:
|
|
30
|
+
|
|
31
|
+
```sh
|
|
32
|
+
node --input-type=module - <<'JS'
|
|
33
|
+
import { spawnSync } from 'node:child_process'
|
|
34
|
+
import { readFile } from 'node:fs/promises'
|
|
35
|
+
import { archive, testedDshVersions } from './scripts/runtime.mjs'
|
|
36
|
+
import { sha256 } from './scripts/verify-packed.mjs'
|
|
37
|
+
const digest = sha256(await readFile(archive))
|
|
38
|
+
for (const version of testedDshVersions) {
|
|
39
|
+
const result = spawnSync(process.execPath, [
|
|
40
|
+
'scripts/verify-packed.mjs', '--archive', archive, '--sha256', digest,
|
|
41
|
+
'--dsh-version', version, '--suite', 'cli', '--suite', 'browser', '--suite', 'smoke',
|
|
42
|
+
], { stdio: 'inherit' })
|
|
43
|
+
if (result.error) throw result.error
|
|
44
|
+
if (result.status !== 0) throw new Error(`Verification failed for ${version}`)
|
|
45
|
+
}
|
|
46
|
+
JS
|
|
21
47
|
```
|
|
22
48
|
|
|
23
|
-
|
|
49
|
+
后续每次 full/发布还须用同包验证相邻退役宿主;本次迁移最终验收另外串行运行开发指南列出的全部六版负向。它们不属于正向业务矩阵。
|
|
50
|
+
|
|
51
|
+
```sh
|
|
52
|
+
node scripts/verify-retired.mjs --archive artifacts/dsh-auth-remote-0.3.1.tgz --sha256 <recorded-sha256> --retired-dsh-version 0.2.1-alpha.2
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
消费循环中不得构建或打包。归档内容变化须产生新候选并重新全量验证。JSON 报告记录摘要、精确版本、suite 范围、命令和真实用例数,见[固定归档指南](development.zh-CN.md#消费固定归档)。
|
|
56
|
+
|
|
57
|
+
工作流 DAG 为 `tag` → `package` → 共用 `verify-packed.yml` → `publish`。producer 上传一份 `release-package` 制品,独立 CLI/smoke 与完整 browser job 覆盖全部七个声明版本,消费前核对 producer 给出的预期 SHA-256、包身份及摘要文件。验证 job 拒绝不完整矩阵,full 聚合要求全部计划 job(含独立 `0.2.1-alpha.2` 退役拒绝)成功;失败、取消或意外跳过均阻止发布。
|
|
58
|
+
|
|
59
|
+
`publish` 下载同一制品,再次与 producer 预期摘要核对,不构建或打包。保留 npm 同版本字节比较、可信发布及 GitHub Release 重试行为。工作流用 `npm publish ./artifacts/dsh-auth-remote-X.Y.Z.tgz --access public` 发布已验证 tgz,无需在本地手动发布。
|
|
24
60
|
|
|
25
61
|
## 打标签并核对结果
|
|
26
62
|
|
|
@@ -29,18 +65,18 @@ pnpm smoke:packed
|
|
|
29
65
|
```sh
|
|
30
66
|
git switch master
|
|
31
67
|
git pull --ff-only origin master
|
|
32
|
-
git tag -a v0.1
|
|
33
|
-
git push origin v0.1
|
|
68
|
+
git tag -a v0.3.1 -m "Release v0.3.1"
|
|
69
|
+
git push origin v0.3.1
|
|
34
70
|
```
|
|
35
71
|
|
|
36
|
-
执行时把 `0.1
|
|
72
|
+
执行时把 `0.3.1` 换成目标版本。标签必须指向 `master` 可达的提交。标签版本不匹配、缺少更新日志条目、测试失败,或 npm 现存版本与本次压缩包字节不同,都会阻止发布。
|
|
37
73
|
|
|
38
74
|
工作流结束后检查运行状态、GitHub Release 和 npm 版本:
|
|
39
75
|
|
|
40
76
|
```sh
|
|
41
77
|
gh run list --workflow release.yml --limit 5
|
|
42
|
-
gh release view v0.1
|
|
43
|
-
npm view dsh-auth-remote@0.1
|
|
78
|
+
gh release view v0.3.1
|
|
79
|
+
npm view dsh-auth-remote@0.3.1 version dist.integrity
|
|
44
80
|
```
|
|
45
81
|
|
|
46
82
|
GitHub Release 包含 `.tgz` 和 `SHA256SUMS`。把两者下载到同一个目录,在该目录运行 `sha256sum -c SHA256SUMS` 验证附件。工作流失败时先查看 **Actions → Release** 再重试;npm 版本不可覆盖,因此只有现存版本的压缩包字节与本次构建一致时,工作流才会跳过重复发布。
|
package/docs/reverse-proxy.md
CHANGED
|
@@ -6,7 +6,7 @@ DSH Auth Remote validates the browser authority before rewriting authenticated t
|
|
|
6
6
|
|
|
7
7
|
## Direct loopback
|
|
8
8
|
|
|
9
|
-
With the [profile example](../examples/web-profile-auth-remote.patch.yml), DSH binds `127.0.0.1:13090`. A browser on the same host may use `http://127.0.0.1:13090/`. Literal `localhost`, canonical `127.0.0.0/8` and bracketed `::1` are implicitly allowed when the actual listener is reachable. An IPv4-mapped IPv6 loopback origin is admitted when it is the effective `publicUrl`, either configured explicitly or derived from the listener. For a DSH
|
|
9
|
+
With the [profile example](../examples/web-profile-auth-remote.patch.yml), DSH binds `127.0.0.1:13090`. A browser on the same host may use `http://127.0.0.1:13090/`. Literal `localhost`, canonical `127.0.0.0/8` and bracketed `::1` are implicitly allowed when the actual listener is reachable. An IPv4-mapped IPv6 loopback origin is admitted when it is the effective `publicUrl`, either configured explicitly or derived from the listener. For a supported DSH IPv6 HTTP or HTTPS listener, follow the [native transport configuration](deployment.md#native-https-and-ipv6). The auth bundle disables the native `webserver` row; an independent profile disable is required for protected remote access.
|
|
10
10
|
|
|
11
11
|
Admission is the unique effective public origin plus literal loopback. Without a public URL, derive one root from the actual bound protocol, address and port. Root paths only are supported; no child path, query, fragment or credentials. Mutations and WebSocket upgrades need Origin matching their Host; extra CLI native trusted hosts do not widen this policy. A GET without Origin cannot set or clear auth cookies when its protocol is unknown. See the [old-field migration rules](deployment.md#migrate-old-allowedorigins) before changing a legacy array.
|
|
12
12
|
|
|
@@ -24,6 +24,6 @@ Set `publicUrl: https://dsh.example.com/` for the example. For a public `:8443`
|
|
|
24
24
|
|
|
25
25
|
Use one canonical public entry; route alternate hostnames to it before requests reach the protected upstream. Replace `publicUrl` and restart after an entry change, then verify the new root and rejection of the former non-loopback origin. Check anonymous redirect/API denial, password plus TOTP login, cookies, Settings, WebSocket, SSE, uploads, previews and revocation. Keep access private until `/auth-remote/ready` reports the expected plugin/protocol and `ready: true`.
|
|
26
26
|
|
|
27
|
-
A DSH
|
|
27
|
+
A supported DSH native HTTPS upstream also works behind a public HTTP or HTTPS proxy. Use an HTTPS upstream URL and configure the proxy's upstream certificate verification and hostname/SNI for that certificate. Plugin cookies follow the external entry's protocol; server-side native cookies use the listener's HTTPS audience/Secure. Preserve Host/Origin even when the two transport protocols differ. Relative file/CLI certificate paths have different bases; see the [path rules](deployment.md#configuration-priority-and-path-bases).
|
|
28
28
|
|
|
29
29
|
The authentication gate ignores `Forwarded` and `X-Forwarded-*` for trust decisions. This avoids treating a client-supplied hint as proof of TLS or hostname. The source checkout's browser suite tests these rules with its own Node HTTP/HTTPS forwarder; it does not execute Nginx or Traefik binaries.
|
|
@@ -6,7 +6,7 @@ DSH Auth Remote 会先验证浏览器 authority,再为 DSH 改写已认证流
|
|
|
6
6
|
|
|
7
7
|
## 回环直连
|
|
8
8
|
|
|
9
|
-
按 [profile 示例](../examples/web-profile-auth-remote.patch.yml),DSH 绑定 `127.0.0.1:13090`。同机浏览器可以使用 `http://127.0.0.1:13090/`。字面 `localhost`、规范 `127.0.0.0/8` 和方括号 `::1` 隐式准入,实际监听须可达。IPv4-mapped IPv6 回环来源只有作为生效 `publicUrl`
|
|
9
|
+
按 [profile 示例](../examples/web-profile-auth-remote.patch.yml),DSH 绑定 `127.0.0.1:13090`。同机浏览器可以使用 `http://127.0.0.1:13090/`。字面 `localhost`、规范 `127.0.0.0/8` 和方括号 `::1` 隐式准入,实际监听须可达。IPv4-mapped IPv6 回环来源只有作为生效 `publicUrl` 时才准入,可以显式配置,也可以从监听地址派生。当前支持 DSH 的 IPv6 HTTP/HTTPS 监听见[原生传输配置](deployment.zh-CN.md#原生-https-与-ipv6)。认证 bundle 禁用原生 `webserver`,受保护远程入口还必须在 profile 独立禁用。
|
|
10
10
|
|
|
11
11
|
准入为唯一生效公开来源加字面回环;未设置公开 URL 时,根据实际监听协议、地址、端口派生唯一根地址。只支持根路径,拒绝子路径、查询、片段、凭据。修改请求和 WebSocket 升级的 Origin 须匹配 Host,额外 CLI 原生 trusted hosts 不扩大策略。无 Origin 且协议不明的 GET 不能写入或清除认证 Cookie。变更旧数组前参阅[旧字段迁移](deployment.zh-CN.md#迁移旧-allowedorigins)。
|
|
12
12
|
|
|
@@ -24,6 +24,6 @@ DSH Auth Remote 会先验证浏览器 authority,再为 DSH 改写已认证流
|
|
|
24
24
|
|
|
25
25
|
使用唯一规范公开入口,在请求到达受保护上游前,把其他主机名导向该入口。入口变更后替换 `publicUrl` 并重启,核对新根地址以及旧非回环来源被拒绝。检查匿名跳转/API 拒绝、密码加 TOTP、Cookie、设置、WebSocket、SSE、上传、预览及撤销。`/auth-remote/ready` 返回预期插件/协议与 `ready: true` 前保持访问私有。
|
|
26
26
|
|
|
27
|
-
DSH
|
|
27
|
+
当前支持 DSH 原生 HTTPS 上游也可位于公开 HTTP 或 HTTPS 代理后。使用 HTTPS 上游 URL,配置代理的上游证书验证和与证书对应的 hostname/SNI。插件 Cookie 按外部入口协议,服务端原生 Cookie 按监听的 HTTPS audience/Secure;两个协议不同时仍保留 Host/Origin。文件和 CLI 相对证书路径基准不同,见[路径规则](deployment.zh-CN.md#配置优先级与路径基准)。
|
|
28
28
|
|
|
29
29
|
认证门禁不会用 `Forwarded` 或 `X-Forwarded-*` 作信任判断,避免把客户端可伪造提示当成 TLS 或主机证明。源码检出的浏览器套件使用自有 Node HTTP/HTTPS 转发器测试这些规则,不运行 Nginx 或 Traefik 二进制。
|
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
# DSH support history
|
|
2
|
+
|
|
3
|
+
[简体中文](support-history.zh-CN.md)
|
|
4
|
+
|
|
5
|
+
Pre-`0.2.0` registry baseline, checked on **2026-10-19** against the complete [DSH registry](https://registry.npmjs.org/@deepseek-ai/dsh) and [plugin registry](https://registry.npmjs.org/dsh-auth-remote): 36 DSH versions, 10 npm plugin versions, and the additional Git-only tag `v0.1.4`. All 36 DSH and 10 plugin archives were downloaded and their registry integrity values checked. Availability is a dated observation, not a compatibility or maintenance guarantee.
|
|
6
|
+
|
|
7
|
+
Incremental check on 2026-10-28: the registries listed 39 DSH and 11 plugin versions. New DSH `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.2-alpha.2` and plugin `0.2.0` archives were downloaded and integrity-checked. `0.2.2-alpha.2` is outside this candidate support/test set. This does not turn baseline availability into an ongoing guarantee.
|
|
8
|
+
|
|
9
|
+
Start with [DSH → plugin](#by-dsh) or [plugin → DSH](#by-plugin). Current candidate commitments are in [README](../README.md#dsh-compatibility) and the [compatibility inventory](legacy-compatibility.md); both support policies retain the previous release record.
|
|
10
|
+
|
|
11
|
+
## Reading the evidence
|
|
12
|
+
|
|
13
|
+
- **D**: the exact version appears in the referenced manifest's `dsh.compatibility.dshReleases`. Each row separately identifies a published npm package, Git-only tag or unreleased source candidate; a declaration alone establishes neither availability nor a successful test.
|
|
14
|
+
- **R**: a release README reports that exact DSH version as tested or covered by its CI; its tagged CI/runtime identifies the same targets. This records the historical project's report, without claiming a surviving successful Actions run or a new run of that old archive.
|
|
15
|
+
- **R\***: a later README reports testing an earlier authentication implementation. It does not establish which old npm archive was exercised.
|
|
16
|
+
- **V**: a real run of an identified candidate archive in this development effort. The first eleven-version Node.js 24 run passed CLI, complete browser and installation smoke on one SHA-256. It applies to that unreleased candidate; the final archive must be verified again after all changes.
|
|
17
|
+
- **Unknown**: no exact pair was found in the checked npm manifests/READMEs, Git tags, CI/runtime files or changelogs. A peer/runtime range alone means technical admission, not D, R or V. An omitted pair is not proof of incompatibility.
|
|
18
|
+
|
|
19
|
+
The initial V record applies to an earlier candidate with working version `0.1.10`, not to `0.2.0`. It identifies SHA-256 `aac4843d079634e47b1d6e5a6f3c3bc4f7a29d41ec35c81993ab03bef6bb798e`, Node.js `24.21.0`, CLI 99/99, full browser 599/599 and smoke 11/11 on 2026-10-19. Raw reports are retained in maintainer verification records outside the npm archive. This history and later documentation postdate that archive; this record does not certify a revised final package.
|
|
20
|
+
|
|
21
|
+
Historical plugin rows are archived evidence, not continuously maintained per-version matrices. The eleven declarations in `0.2.0` remain historical facts. Unpublished `0.3.1` declares only the seven rows below; six older hosts have last supported plugin `0.2.0`. Maintenance dates do not automatically change technical admission or history.
|
|
22
|
+
|
|
23
|
+
## Choosing an installation
|
|
24
|
+
|
|
25
|
+
`0.3.1` is an unpublished candidate (its exact registry endpoint returned 404 on 2026-10-28). Use its verified local archive for the seven current targets, then the npm version after publication. Published `0.2.0` was retrievable that day with registry integrity checked and SHA-256 `7b4156a75398daef079435af85ff1387a26e94055e17871000e945299fc66efc`; it is the last supported plugin for the six retired hosts. Only this candidate explicitly declares `0.2.1-rc.3` and `0.2.1-rc.4`; they do not inherit a `0.2.0` declaration.
|
|
26
|
+
|
|
27
|
+
Migrate toward DSH `0.2.1-rc.4` with candidate `0.3.1`: follow the [deployment guide](deployment.md) to stop and back up, upgrade DSH first, then install the plugin, retaining the independent profile-level native webserver disable. Roll back with an explicit old host and `0.2.0`; existing npm versions stay immutable. Git-only `0.1.4`, unknown pairs and undeclared future hosts receive no current support recommendation; identity/API checks remain in force.
|
|
28
|
+
|
|
29
|
+
<a id="by-plugin"></a>
|
|
30
|
+
|
|
31
|
+
## Plugin → DSH
|
|
32
|
+
|
|
33
|
+
Every listed version has a stable `#plugin-<version>` anchor. Historical npm rows through `0.1.10` were retrievable with integrity checks at the baseline above. Their manifests and packaged English READMEs match the corresponding tags, apart from npm removing `packageManager`. None of these historical npm archives was rerun in this change.
|
|
34
|
+
|
|
35
|
+
| Plugin version / availability | Exact historical DSH evidence | Sources |
|
|
36
|
+
| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
37
|
+
| <a id="plugin-0.1.0"></a>`0.1.0` — npm available; historical | `0.1.7-rc.1` **R**. No exact manifest table. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.0), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.0/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.0/.github/workflows/ci.yml) |
|
|
38
|
+
| <a id="plugin-0.1.1"></a>`0.1.1` — npm available; historical | `0.1.7-rc.1` **R**. No exact manifest table. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.1), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.1/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.1/.github/workflows/ci.yml) |
|
|
39
|
+
| <a id="plugin-0.1.2"></a>`0.1.2` — npm available; historical | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1` **R**. No exact manifest table. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.2), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.2/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.2/.github/workflows/ci.yml) |
|
|
40
|
+
| <a id="plugin-0.1.3"></a>`0.1.3` — npm available; historical | `0.1.7-rc.1`, `0.1.7-rc.2`, `0.2.0-rc.1`, `0.2.0-rc.2` **R**. Additionally `0.2.1-alpha.1` **R\*** in the later `0.1.5` README; that is an implementation report, not an old-archive verification. No exact manifest table. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.3), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.3/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.3/.github/workflows/ci.yml), [later report](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.5/README.md) |
|
|
41
|
+
| <a id="plugin-0.1.4"></a>`0.1.4` — Git tag only; npm version endpoint returned 404 | `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` **D/R at the tag**. No retrievable npm artifact, no npm recommendation. | [tag](https://github.com/ChenLuoi/dsh-auth-remote/tree/v0.1.4), [manifest](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.4/package.json), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.4/README.md), [registry lookup](https://registry.npmjs.org/dsh-auth-remote/0.1.4) |
|
|
42
|
+
| <a id="plugin-0.1.5"></a>`0.1.5` — npm available; historical | `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` **D/R**. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.5), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.5/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.5/.github/workflows/ci.yml) |
|
|
43
|
+
| <a id="plugin-0.1.6"></a>`0.1.6` — npm available; historical | `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` **D/R**. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.6), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.6/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.6/.github/workflows/ci.yml) |
|
|
44
|
+
| <a id="plugin-0.1.7"></a>`0.1.7` — npm available; historical | `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` **D/R**. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.7), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.7/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.7/.github/workflows/ci.yml) |
|
|
45
|
+
| <a id="plugin-0.1.8"></a>`0.1.8` — npm available; historical | `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` **D/R**. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.8), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.8/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.8/.github/workflows/ci.yml) |
|
|
46
|
+
| <a id="plugin-0.1.9"></a>`0.1.9` — npm available; historical | `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`, `0.2.1-alpha.3` **D/R**. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.9), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.9/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.9/.github/workflows/ci.yml) |
|
|
47
|
+
| <a id="plugin-0.1.10"></a>`0.1.10` — npm available; latest in the pre-0.2.0 baseline | `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`, `0.2.1-alpha.3`, `0.2.1-alpha.4`, `0.2.1-alpha.5` **D/R**. No exact declaration for either new RC. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.10), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.10/README.md), [CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.10/.github/workflows/ci.yml) |
|
|
48
|
+
| <a id="plugin-unreleased"></a><a id="plugin-0.2.0"></a>`0.2.0` — npm published; archive/integrity checked 2026-10-28 | `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`, `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` **D**. Eleven exact declarations retained; earlier candidate V does not certify this package. | [npm](https://registry.npmjs.org/dsh-auth-remote/0.2.0), [version manifest](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.2.0/package.json), [README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.2.0/README.md), [verification and checksums](releasing.md) |
|
|
49
|
+
| <a id="plugin-0.3.1"></a>`0.3.1` — unpublished candidate; registry 404 on 2026-10-28 | `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`, `0.2.1-rc.3`, `0.2.1-rc.4` **D**. Candidate manifest declarations; final same-archive reports are separate, not a published V claim. | [candidate manifest](../package.json), [README](../README.md), [registry](https://registry.npmjs.org/dsh-auth-remote/0.3.1) |
|
|
50
|
+
|
|
51
|
+
The peer ceiling in `0.1.0` and `0.1.1` is `>=0.1.7-rc.1 <0.2.0-0`. From `0.1.2` through `0.2.0`, the historical host peer/runtime range is open-ended `>=0.1.7-rc.1`; npm `0.1.10` also declares that `engines.dsh` range. These ranges cannot fill unknown exact cells. The `0.1.5` changelog renumbers the earlier Git-only `0.1.4` entry, and the tags also contain test changes: those labels are not interchangeable artifacts.
|
|
52
|
+
|
|
53
|
+
<a id="by-dsh"></a>
|
|
54
|
+
|
|
55
|
+
## DSH → plugin
|
|
56
|
+
|
|
57
|
+
Every listed DSH version has a stable anchor. The npm column preserves historical source evidence without rerunning old positive pairs; follow plugin rows for D/R/R\*/V, with Git-only `0.1.4` separate. Availability is dated. Six retired hosts, three legacy Alphas, four normally supported RCs and the unverified future host are identified separately.
|
|
58
|
+
|
|
59
|
+
| Exact DSH version / registry evidence | Plugin evidence; check distribution in plugin row | Git-only evidence | Current candidate state / choice |
|
|
60
|
+
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------------------------------------------------------------- |
|
|
61
|
+
| <a id="dsh-0.0.1-rc.1"></a>[`0.0.1-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.0.1-rc.1) | Unknown | None found | Below current minimum; no recommendation |
|
|
62
|
+
| <a id="dsh-0.0.1-rc.2"></a>[`0.0.1-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.0.1-rc.2) | Unknown | None found | Below current minimum; no recommendation |
|
|
63
|
+
| <a id="dsh-0.0.1-rc.5"></a>[`0.0.1-rc.5`](https://registry.npmjs.org/@deepseek-ai/dsh/0.0.1-rc.5) | Unknown | None found | Below current minimum; no recommendation |
|
|
64
|
+
| <a id="dsh-0.1.0-rc.2"></a>[`0.1.0-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.2) | Unknown | None found | Below current minimum; no recommendation |
|
|
65
|
+
| <a id="dsh-0.1.0-rc.3"></a>[`0.1.0-rc.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.3) | Unknown | None found | Below current minimum; no recommendation |
|
|
66
|
+
| <a id="dsh-0.1.0-rc.6"></a>[`0.1.0-rc.6`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.6) | Unknown | None found | Below current minimum; no recommendation |
|
|
67
|
+
| <a id="dsh-0.1.0-rc.7"></a>[`0.1.0-rc.7`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.7) | Unknown | None found | Below current minimum; no recommendation |
|
|
68
|
+
| <a id="dsh-0.1.0-rc.8"></a>[`0.1.0-rc.8`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.8) | Unknown | None found | Below current minimum; no recommendation |
|
|
69
|
+
| <a id="dsh-0.1.1-rc.1"></a>[`0.1.1-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.1-rc.1) | Unknown | None found | Below current minimum; no recommendation |
|
|
70
|
+
| <a id="dsh-0.1.1-rc.2"></a>[`0.1.1-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.1-rc.2) | Unknown | None found | Below current minimum; no recommendation |
|
|
71
|
+
| <a id="dsh-0.1.2-alpha.2"></a>[`0.1.2-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-alpha.2) | Unknown | None found | Below current minimum; no recommendation |
|
|
72
|
+
| <a id="dsh-0.1.2-alpha.3"></a>[`0.1.2-alpha.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-alpha.3) | Unknown | None found | Below current minimum; no recommendation |
|
|
73
|
+
| <a id="dsh-0.1.2-alpha.4"></a>[`0.1.2-alpha.4`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-alpha.4) | Unknown | None found | Below current minimum; no recommendation |
|
|
74
|
+
| <a id="dsh-0.1.2-alpha.5"></a>[`0.1.2-alpha.5`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-alpha.5) | Unknown | None found | Below current minimum; no recommendation |
|
|
75
|
+
| <a id="dsh-0.1.2-rc.1"></a>[`0.1.2-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-rc.1) | Unknown | None found | Below current minimum; no recommendation |
|
|
76
|
+
| <a id="dsh-0.1.3-alpha.2"></a>[`0.1.3-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.3-alpha.2) | Unknown | None found | Below current minimum; no recommendation |
|
|
77
|
+
| <a id="dsh-0.1.5-alpha.1"></a>[`0.1.5-alpha.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-alpha.1) | Unknown | None found | Below current minimum; no recommendation |
|
|
78
|
+
| <a id="dsh-0.1.5-alpha.2"></a>[`0.1.5-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-alpha.2) | Unknown | None found | Below current minimum; no recommendation |
|
|
79
|
+
| <a id="dsh-0.1.5-rc.1"></a>[`0.1.5-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-rc.1) | Unknown | None found | Below current minimum; no recommendation |
|
|
80
|
+
| <a id="dsh-0.1.5-rc.2"></a>[`0.1.5-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-rc.2) | Unknown | None found | Below current minimum; no recommendation |
|
|
81
|
+
| <a id="dsh-0.1.5-rc.3"></a>[`0.1.5-rc.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-rc.3) | Unknown | None found | Below current minimum; no recommendation |
|
|
82
|
+
| <a id="dsh-0.1.6-alpha.1"></a>[`0.1.6-alpha.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.6-alpha.1) | Unknown | None found | Below current minimum; no recommendation |
|
|
83
|
+
| <a id="dsh-0.1.6-alpha.2"></a>[`0.1.6-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.6-alpha.2) | Unknown | None found | Below current minimum; no recommendation |
|
|
84
|
+
| <a id="dsh-0.1.7-alpha.1"></a>[`0.1.7-alpha.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.7-alpha.1) | Unknown | None found | Below current minimum; no recommendation |
|
|
85
|
+
| <a id="dsh-0.1.7-alpha.2"></a>[`0.1.7-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.7-alpha.2) | Unknown | None found | Below current minimum; no recommendation |
|
|
86
|
+
| <a id="dsh-0.1.7-rc.1"></a>[`0.1.7-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.7-rc.1) | `0.1.0`, `0.1.1`, `0.1.2`, `0.1.3`, `0.1.5`, `0.1.6`, `0.1.7`, `0.1.8`, `0.1.9`, `0.1.10`, [`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | Retired in `0.3.1`; last supported `0.2.0` |
|
|
87
|
+
| <a id="dsh-0.1.7-rc.2"></a>[`0.1.7-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.7-rc.2) | `0.1.2`, `0.1.3`, `0.1.5`, `0.1.6`, `0.1.7`, `0.1.8`, `0.1.9`, `0.1.10`, [`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | Retired in `0.3.1`; last supported `0.2.0` |
|
|
88
|
+
| <a id="dsh-0.2.0-rc.1"></a>[`0.2.0-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.0-rc.1) | `0.1.2`, `0.1.3`, `0.1.5`, `0.1.6`, `0.1.7`, `0.1.8`, `0.1.9`, `0.1.10`, [`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | Retired in `0.3.1`; last supported `0.2.0` |
|
|
89
|
+
| <a id="dsh-0.2.0-rc.2"></a>[`0.2.0-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.0-rc.2) | `0.1.3`, `0.1.5`, `0.1.6`, `0.1.7`, `0.1.8`, `0.1.9`, `0.1.10`, [`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | Retired in `0.3.1`; last supported `0.2.0` |
|
|
90
|
+
| <a id="dsh-0.2.1-alpha.1"></a>[`0.2.1-alpha.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.1) | `0.1.3` **R\***, `0.1.5`, `0.1.6`, `0.1.7`, `0.1.8`, `0.1.9`, `0.1.10`, [`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | Retired in `0.3.1`; last supported `0.2.0` |
|
|
91
|
+
| <a id="dsh-0.2.1-alpha.2"></a>[`0.2.1-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.2) | `0.1.6`, `0.1.7`, `0.1.8`, `0.1.9`, `0.1.10`, [`0.2.0`](#plugin-0.2.0) **D** | None found | Retired in `0.3.1`; last supported `0.2.0` |
|
|
92
|
+
| <a id="dsh-0.2.1-alpha.3"></a>[`0.2.1-alpha.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.3) | `0.1.9`, `0.1.10`, [`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | None found | Legacy; candidate `0.3.1` |
|
|
93
|
+
| <a id="dsh-0.2.1-alpha.4"></a>[`0.2.1-alpha.4`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.4) | `0.1.10`, [`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | None found | Legacy; candidate `0.3.1` |
|
|
94
|
+
| <a id="dsh-0.2.1-alpha.5"></a>[`0.2.1-alpha.5`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.5) | `0.1.10`, [`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | None found | Legacy; candidate `0.3.1` |
|
|
95
|
+
| <a id="dsh-0.2.1-rc.1"></a>[`0.2.1-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-rc.1) | [`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | None found | Normal; candidate `0.3.1` |
|
|
96
|
+
| <a id="dsh-0.2.1-rc.2"></a>[`0.2.1-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-rc.2) | [`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | None found | Normal; candidate `0.3.1` |
|
|
97
|
+
| <a id="dsh-0.2.1-rc.3"></a>[`0.2.1-rc.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-rc.3) | [`0.3.1`](#plugin-0.3.1) **D (candidate)** | None found | Normal; candidate `0.3.1` |
|
|
98
|
+
| <a id="dsh-0.2.1-rc.4"></a>[`0.2.1-rc.4`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-rc.4) | [`0.3.1`](#plugin-0.3.1) **D (candidate)** | None found | Normal; candidate `0.3.1` |
|
|
99
|
+
| <a id="dsh-0.2.2-alpha.2"></a>[`0.2.2-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.2-alpha.2) | Unknown; range does not establish a declaration | None found | Undeclared/unverified; forward admission still checks identity/APIs |
|
|
100
|
+
|
|
101
|
+
## Maintaining this history
|
|
102
|
+
|
|
103
|
+
These tables are maintained manually in both languages and both directions. Recheck registry metadata and tarball availability, inspect exact tag/package evidence, distinguish D/R/R\*/V, and record the check date. Update both cells when adding evidence; keep the stable anchors. A newly released plugin needs its own row and exact archive evidence. Actual DSH retirement updates current declarations, runtime adaptations, tests and this history together under the support policy; eligibility dates alone never change these tables. No inventory/history generator or dedicated CI gate is used.
|
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
# DSH 支持历史
|
|
2
|
+
|
|
3
|
+
[English](support-history.md)
|
|
4
|
+
|
|
5
|
+
`0.2.0` 发布前的 registry 基线,核对日期:**2026-10-19**。查阅完整 [DSH registry](https://registry.npmjs.org/@deepseek-ai/dsh) 和[插件 registry](https://registry.npmjs.org/dsh-auth-remote),共 36 个 DSH 版本、10 个 npm 插件版本,另有仅确认 Git tag 的 `v0.1.4`。已下载全部 36 个 DSH 和 10 个插件归档并核验 registry integrity。可获取性只是该日期的观察,不等于兼容或维护承诺。
|
|
6
|
+
|
|
7
|
+
2026-10-28 增量核对:registry 列出 39 个 DSH 与 11 个插件版本;新增 DSH `0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.2-alpha.2` 及插件 `0.2.0` 归档均已下载并核验 integrity。`0.2.2-alpha.2` 未列入本候选支持/实测目标。此记录不把 2026-10-19 的历史可获取性写成持续保证。
|
|
8
|
+
|
|
9
|
+
从 [DSH → 插件](#by-dsh)或[插件 → DSH](#by-plugin)查询。当前候选承诺见 [README](../README.zh-CN.md#dsh-兼容性)和[兼容库存](legacy-compatibility.zh-CN.md);两份支持规范保留前一发布记录。
|
|
10
|
+
|
|
11
|
+
## 如何阅读证据
|
|
12
|
+
|
|
13
|
+
- **D**:精确版本出现在所指 manifest 的 `dsh.compatibility.dshReleases`。各行单独标明已发布 npm 包、仅 Git tag 或未发布源码候选;声明本身不证明可获取性或实测通过。
|
|
14
|
+
- **R**:当时 README 将该精确 DSH 列为已测试或 CI 覆盖目标,tag 的 CI/runtime 也指向对应目标。这里只记录历史项目的报告,不声称取得了历史 Actions 成功记录,也不声称本次重跑了该旧归档。
|
|
15
|
+
- **R\***:后续 README 报告测试过较早的认证实现,没有证明当时使用了哪个旧 npm 归档。
|
|
16
|
+
- **V**:本轮开发对身份明确的候选归档进行了真实运行。同一 SHA-256 的十一版 Node.js 24 首轮 CLI、完整 browser 和安装 smoke 已通过;它只属于那个未发布候选,所有变更落定后的最终归档仍须重验。
|
|
17
|
+
- **未知**:在已核对的 npm manifest/README、Git tag、CI/runtime 和 changelog 中,没有找到该精确组合。仅满足 peer/runtime 范围表示技术准入,不能推导 D、R 或 V。表中未列组合也不等于已证明不兼容。
|
|
18
|
+
|
|
19
|
+
首轮 V 记录属于当时工作版本为 `0.1.10` 的旧候选,不是 `0.2.0` 的验证。其身份对应 SHA-256 `aac4843d079634e47b1d6e5a6f3c3bc4f7a29d41ec35c81993ab03bef6bb798e`,Node.js `24.21.0`,2026-10-19 的 CLI 99/99、完整 browser 599/599、smoke 11/11。原始报告保留在维护者的归档外验证记录中。本文及后续文档晚于该归档,这条记录不认证修订后的最终包。
|
|
20
|
+
|
|
21
|
+
历史插件行是存档证据,不是持续维护的逐插件版本测试矩阵。`0.2.0` 的十一版声明保持历史事实;未发布 `0.3.1` 仅声明下列七版,六个旧宿主最后支持插件为 `0.2.0`。维护日期不自动改变技术准入或历史关系。
|
|
22
|
+
|
|
23
|
+
## 如何选择安装
|
|
24
|
+
|
|
25
|
+
`0.3.1` 仅为未发布候选(2026-10-28 精确 registry 接口返回 404),当前七版使用经验证的本地归档,发布成功后再按 npm 版本安装。`0.2.0` 同日可下载,registry integrity 已核验,SHA-256 为 `7b4156a75398daef079435af85ff1387a26e94055e17871000e945299fc66efc`;它是六个退役宿主的最后支持插件。新宿主 `0.2.1-rc.3`、`0.2.1-rc.4` 只有本候选的明确声明,不能继承 `0.2.0` 的声明。
|
|
26
|
+
|
|
27
|
+
迁移推荐 DSH `0.2.1-rc.4` 与候选 `0.3.1`,按[部署指南](deployment.zh-CN.md)先停服备份、升级宿主,再安装新插件,保留 profile 级原生 webserver 独立禁用。回退须使用明确的旧宿主及 `0.2.0`,不改写已有 npm 版本。Git-only `0.1.4`、历史未知组合与未声明的未来宿主没有当前支持推荐;包身份/API 检查继续生效。
|
|
28
|
+
|
|
29
|
+
<a id="by-plugin"></a>
|
|
30
|
+
|
|
31
|
+
## 插件 → DSH
|
|
32
|
+
|
|
33
|
+
每个版本保留稳定的 `#plugin-<version>` 锚点。截至 `0.1.10` 的历史 npm 行均在上述基线可下载且 integrity 一致;manifest 和包内英文 README 与对应 tag 一致,除 npm 移除 `packageManager`。本次没有重跑这些历史 npm 归档。
|
|
34
|
+
|
|
35
|
+
| 插件版本 / 可获取性 | 精确历史 DSH 证据 | 来源 |
|
|
36
|
+
| --------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
37
|
+
| <a id="plugin-0.1.0"></a>`0.1.0` — npm 可获取;历史版本 | `0.1.7-rc.1` **R**;无 manifest 精确表。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.0)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.0/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.0/.github/workflows/ci.yml) |
|
|
38
|
+
| <a id="plugin-0.1.1"></a>`0.1.1` — npm 可获取;历史版本 | `0.1.7-rc.1` **R**;无 manifest 精确表。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.1)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.1/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.1/.github/workflows/ci.yml) |
|
|
39
|
+
| <a id="plugin-0.1.2"></a>`0.1.2` — npm 可获取;历史版本 | `0.1.7-rc.1`、`0.1.7-rc.2`、`0.2.0-rc.1` **R**;无 manifest 精确表。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.2)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.2/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.2/.github/workflows/ci.yml) |
|
|
40
|
+
| <a id="plugin-0.1.3"></a>`0.1.3` — npm 可获取;历史版本 | `0.1.7-rc.1`、`0.1.7-rc.2`、`0.2.0-rc.1`、`0.2.0-rc.2` **R**。后续 `0.1.5` README 还报告 `0.2.1-alpha.1` **R\***,仅指实现,并非旧归档验证;无 manifest 精确表。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.3)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.3/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.3/.github/workflows/ci.yml)、[后续报告](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.5/README.md) |
|
|
41
|
+
| <a id="plugin-0.1.4"></a>`0.1.4` — 仅确认 Git tag;npm 版本接口返回 404 | `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` **tag 级 D/R**。无可获取 npm 制品,不提供 npm 推荐。 | [tag](https://github.com/ChenLuoi/dsh-auth-remote/tree/v0.1.4)、[manifest](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.4/package.json)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.4/README.md)、[registry 查询](https://registry.npmjs.org/dsh-auth-remote/0.1.4) |
|
|
42
|
+
| <a id="plugin-0.1.5"></a>`0.1.5` — npm 可获取;历史版本 | `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` **D/R**。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.5)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.5/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.5/.github/workflows/ci.yml) |
|
|
43
|
+
| <a id="plugin-0.1.6"></a>`0.1.6` — npm 可获取;历史版本 | `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` **D/R**。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.6)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.6/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.6/.github/workflows/ci.yml) |
|
|
44
|
+
| <a id="plugin-0.1.7"></a>`0.1.7` — npm 可获取;历史版本 | `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` **D/R**。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.7)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.7/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.7/.github/workflows/ci.yml) |
|
|
45
|
+
| <a id="plugin-0.1.8"></a>`0.1.8` — npm 可获取;历史版本 | `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` **D/R**。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.8)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.8/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.8/.github/workflows/ci.yml) |
|
|
46
|
+
| <a id="plugin-0.1.9"></a>`0.1.9` — npm 可获取;历史版本 | `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`、`0.2.1-alpha.3` **D/R**。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.9)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.9/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.9/.github/workflows/ci.yml) |
|
|
47
|
+
| <a id="plugin-0.1.10"></a>`0.1.10` — npm 可获取;0.2.0 发布前基线最新插件 | `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`、`0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5` **D/R**;没有两个新 RC 的精确声明。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.1.10)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.10/README.md)、[CI](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.1.10/.github/workflows/ci.yml) |
|
|
48
|
+
| <a id="plugin-unreleased"></a><a id="plugin-0.2.0"></a>`0.2.0` — npm 已发布;2026-10-28 归档及 integrity 已核验 | `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`、`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` **D**. 保留十一版精确声明;不把更早候选 V 归入本包。 | [npm](https://registry.npmjs.org/dsh-auth-remote/0.2.0)、[版本 manifest](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.2.0/package.json)、[README](https://github.com/ChenLuoi/dsh-auth-remote/blob/v0.2.0/README.md)、[验证与摘要](releasing.zh-CN.md) |
|
|
49
|
+
| <a id="plugin-0.3.1"></a>`0.3.1` — 未发布候选;2026-10-28 registry 返回 404 | `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`、`0.2.1-rc.3`、`0.2.1-rc.4` **D**. 本候选 manifest 声明;最终同包报告单独记录,非已发布 V。 | [candidate manifest](../package.json), [README](../README.zh-CN.md), [registry](https://registry.npmjs.org/dsh-auth-remote/0.3.1) |
|
|
50
|
+
|
|
51
|
+
`0.1.0`、`0.1.1` 的 peer 上限为 `>=0.1.7-rc.1 <0.2.0-0`。从 `0.1.2` 到 `0.2.0`,历史 host peer/runtime 范围开放为 `>=0.1.7-rc.1`;npm `0.1.10` 还通过 `engines.dsh` 声明该范围。这些范围不能填补未知精确组合。`0.1.5` changelog 将更早 Git-only `0.1.4` 的条目重新编号,而且两个 tag 之间还存在测试修改,不能视为同一制品。
|
|
52
|
+
|
|
53
|
+
<a id="by-dsh"></a>
|
|
54
|
+
|
|
55
|
+
## DSH → 插件
|
|
56
|
+
|
|
57
|
+
每个表列 DSH 版本有稳定锚点。npm 列保留历史来源,没有重新运行旧正向组合;D/R/R\*/V 详情见插件行,Git-only `0.1.4` 单列。归档可获取性以相应核对日期为准;六版退役、三个 Alpha legacy、四个 RC 正常支持与未来未验证分别列出。
|
|
58
|
+
|
|
59
|
+
| 精确 DSH 版本 / registry 证据 | 插件证据;分发状态见插件行 | 仅 Git 证据 | 当前候选状态 / 选择 |
|
|
60
|
+
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------- |
|
|
61
|
+
| <a id="dsh-0.0.1-rc.1"></a>[`0.0.1-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.0.1-rc.1) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
62
|
+
| <a id="dsh-0.0.1-rc.2"></a>[`0.0.1-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.0.1-rc.2) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
63
|
+
| <a id="dsh-0.0.1-rc.5"></a>[`0.0.1-rc.5`](https://registry.npmjs.org/@deepseek-ai/dsh/0.0.1-rc.5) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
64
|
+
| <a id="dsh-0.1.0-rc.2"></a>[`0.1.0-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.2) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
65
|
+
| <a id="dsh-0.1.0-rc.3"></a>[`0.1.0-rc.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.3) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
66
|
+
| <a id="dsh-0.1.0-rc.6"></a>[`0.1.0-rc.6`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.6) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
67
|
+
| <a id="dsh-0.1.0-rc.7"></a>[`0.1.0-rc.7`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.7) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
68
|
+
| <a id="dsh-0.1.0-rc.8"></a>[`0.1.0-rc.8`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.0-rc.8) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
69
|
+
| <a id="dsh-0.1.1-rc.1"></a>[`0.1.1-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.1-rc.1) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
70
|
+
| <a id="dsh-0.1.1-rc.2"></a>[`0.1.1-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.1-rc.2) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
71
|
+
| <a id="dsh-0.1.2-alpha.2"></a>[`0.1.2-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-alpha.2) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
72
|
+
| <a id="dsh-0.1.2-alpha.3"></a>[`0.1.2-alpha.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-alpha.3) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
73
|
+
| <a id="dsh-0.1.2-alpha.4"></a>[`0.1.2-alpha.4`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-alpha.4) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
74
|
+
| <a id="dsh-0.1.2-alpha.5"></a>[`0.1.2-alpha.5`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-alpha.5) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
75
|
+
| <a id="dsh-0.1.2-rc.1"></a>[`0.1.2-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.2-rc.1) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
76
|
+
| <a id="dsh-0.1.3-alpha.2"></a>[`0.1.3-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.3-alpha.2) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
77
|
+
| <a id="dsh-0.1.5-alpha.1"></a>[`0.1.5-alpha.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-alpha.1) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
78
|
+
| <a id="dsh-0.1.5-alpha.2"></a>[`0.1.5-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-alpha.2) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
79
|
+
| <a id="dsh-0.1.5-rc.1"></a>[`0.1.5-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-rc.1) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
80
|
+
| <a id="dsh-0.1.5-rc.2"></a>[`0.1.5-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-rc.2) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
81
|
+
| <a id="dsh-0.1.5-rc.3"></a>[`0.1.5-rc.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.5-rc.3) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
82
|
+
| <a id="dsh-0.1.6-alpha.1"></a>[`0.1.6-alpha.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.6-alpha.1) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
83
|
+
| <a id="dsh-0.1.6-alpha.2"></a>[`0.1.6-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.6-alpha.2) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
84
|
+
| <a id="dsh-0.1.7-alpha.1"></a>[`0.1.7-alpha.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.7-alpha.1) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
85
|
+
| <a id="dsh-0.1.7-alpha.2"></a>[`0.1.7-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.7-alpha.2) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
86
|
+
| <a id="dsh-0.1.7-rc.1"></a>[`0.1.7-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.7-rc.1) | `0.1.0`、`0.1.1`、`0.1.2`、`0.1.3`、`0.1.5`、`0.1.6`、`0.1.7`、`0.1.8`、`0.1.9`、`0.1.10`、[`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | `0.3.1` 退役;最后支持 `0.2.0` |
|
|
87
|
+
| <a id="dsh-0.1.7-rc.2"></a>[`0.1.7-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.1.7-rc.2) | `0.1.2`、`0.1.3`、`0.1.5`、`0.1.6`、`0.1.7`、`0.1.8`、`0.1.9`、`0.1.10`、[`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | `0.3.1` 退役;最后支持 `0.2.0` |
|
|
88
|
+
| <a id="dsh-0.2.0-rc.1"></a>[`0.2.0-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.0-rc.1) | `0.1.2`、`0.1.3`、`0.1.5`、`0.1.6`、`0.1.7`、`0.1.8`、`0.1.9`、`0.1.10`、[`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | `0.3.1` 退役;最后支持 `0.2.0` |
|
|
89
|
+
| <a id="dsh-0.2.0-rc.2"></a>[`0.2.0-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.0-rc.2) | `0.1.3`、`0.1.5`、`0.1.6`、`0.1.7`、`0.1.8`、`0.1.9`、`0.1.10`、[`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | `0.3.1` 退役;最后支持 `0.2.0` |
|
|
90
|
+
| <a id="dsh-0.2.1-alpha.1"></a>[`0.2.1-alpha.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.1) | `0.1.3` **R\***、`0.1.5`、`0.1.6`、`0.1.7`、`0.1.8`、`0.1.9`、`0.1.10`、[`0.2.0`](#plugin-0.2.0) **D** | `0.1.4` | `0.3.1` 退役;最后支持 `0.2.0` |
|
|
91
|
+
| <a id="dsh-0.2.1-alpha.2"></a>[`0.2.1-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.2) | `0.1.6`、`0.1.7`、`0.1.8`、`0.1.9`、`0.1.10`、[`0.2.0`](#plugin-0.2.0) **D** | 未找到 | `0.3.1` 退役;最后支持 `0.2.0` |
|
|
92
|
+
| <a id="dsh-0.2.1-alpha.3"></a>[`0.2.1-alpha.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.3) | `0.1.9`、`0.1.10`、[`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | 未找到 | Legacy;候选 `0.3.1` |
|
|
93
|
+
| <a id="dsh-0.2.1-alpha.4"></a>[`0.2.1-alpha.4`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.4) | `0.1.10`、[`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | 未找到 | Legacy;候选 `0.3.1` |
|
|
94
|
+
| <a id="dsh-0.2.1-alpha.5"></a>[`0.2.1-alpha.5`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-alpha.5) | `0.1.10`、[`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | 未找到 | Legacy;候选 `0.3.1` |
|
|
95
|
+
| <a id="dsh-0.2.1-rc.1"></a>[`0.2.1-rc.1`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-rc.1) | [`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | 未找到 | 正常;候选 `0.3.1` |
|
|
96
|
+
| <a id="dsh-0.2.1-rc.2"></a>[`0.2.1-rc.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-rc.2) | [`0.2.0`](#plugin-0.2.0) **D**, [`0.3.1`](#plugin-0.3.1) **D (candidate)** | 未找到 | 正常;候选 `0.3.1` |
|
|
97
|
+
| <a id="dsh-0.2.1-rc.3"></a>[`0.2.1-rc.3`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-rc.3) | [`0.3.1`](#plugin-0.3.1) **D (candidate)** | 未发现 | 正常;候选 `0.3.1` |
|
|
98
|
+
| <a id="dsh-0.2.1-rc.4"></a>[`0.2.1-rc.4`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.1-rc.4) | [`0.3.1`](#plugin-0.3.1) **D (candidate)** | 未发现 | 正常;候选 `0.3.1` |
|
|
99
|
+
| <a id="dsh-0.2.2-alpha.2"></a>[`0.2.2-alpha.2`](https://registry.npmjs.org/@deepseek-ai/dsh/0.2.2-alpha.2) | 未知;不由范围推导声明 | 未发现 | 未声明/未验证;前向准入仍检查身份/API |
|
|
100
|
+
|
|
101
|
+
## 如何维护历史
|
|
102
|
+
|
|
103
|
+
两种语言、两个方向的表均人工维护。重新核实 registry 元数据及归档可获取性,检查精确 tag/包证据,区分 D/R/R\*/V 并记录核对日期。新增证据时同时更新两边单元格,保留稳定锚点。新发布插件须新增独立行和精确归档证据。实际 DSH 退役须按支持规范同步修改当前声明、运行适配、测试和历史,资格日期本身不改变这些表。不使用库存/历史生成器或专门 CI gate。
|
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
# DSH support lifecycle
|
|
2
|
+
|
|
3
|
+
[简体中文](support-policy.zh-CN.md)
|
|
4
|
+
|
|
5
|
+
Last updated: 2026-10-19. This policy separates maintenance commitments, exact-version verification and technical admission. Plugin **`0.2.0`** adds exact support for both `0.2.1` RC releases; its new DSH targets do not extend the support history of the published plugin `0.1.10`. Verify the final `0.2.0` archive before publishing.
|
|
6
|
+
|
|
7
|
+
## Support states and runtime admission
|
|
8
|
+
|
|
9
|
+
| State | Maintenance and verification | Runtime behavior |
|
|
10
|
+
| -------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
|
|
11
|
+
| Supported | Maintain promised features and block release on failed exact-version verification | Run after necessary technical checks |
|
|
12
|
+
| Legacy, including an elapsed window without actual retirement | Continue promised features, compatibility regression and security fixes; verification still blocks release | Run after technical checks, with maintenance dates and migration guidance |
|
|
13
|
+
| Explicitly retired in a plugin release | Remove that release's current support commitment and continuing matrix; retain historical evidence | May run with a warning if all necessary contracts remain; admission is not verified compatibility |
|
|
14
|
+
| Necessary API/behavior missing, necessary adaptation removed, or security check failed | Do not claim support | Refuse protected business service and provide an upgrade or last-compatible-plugin path |
|
|
15
|
+
| Unassessed old or future release | No exact support commitment | Apply technical checks; successful startup does not add support |
|
|
16
|
+
|
|
17
|
+
`dsh.compatibility.dshReleases` records exact support declarations. `engines.dsh`, the DSH peer and runtime checks express technical admission. Plugin `0.2.0` retains `>=0.1.7-rc.1`, including prereleases, together with package identity and required API checks. Calendar dates and maintenance-only retirement must not mechanically raise that floor. Current real retirement records are empty.
|
|
18
|
+
|
|
19
|
+
Diagnostics belong in startup logs, before protected service is offered: legacy dates and migration guidance, or the absence of a current support commitment for an admitted unverified/retired release. A process should emit each exact-version/state warning at most once, including across HMR. Diagnostics do not change authentication, login dialogs, request authorization or CLI JSON.
|
|
20
|
+
|
|
21
|
+
## Announced maintenance schedule
|
|
22
|
+
|
|
23
|
+
These dates were explicitly selected by development. Delayed implementation does not restart the windows. All eleven releases remain supported; legacy does not remove a release from verification. Every release requires real same-archive verification before publication.
|
|
24
|
+
|
|
25
|
+
| Exact DSH release | Maintenance state | Legacy since | Window in calendar days | Earliest eligible retirement |
|
|
26
|
+
| ----------------- | ------------------------------------------------------ | ------------ | ----------------------- | ---------------------------- |
|
|
27
|
+
| `0.1.7-rc.1` | Legacy | 2026-10-19 | 14 | 2026-11-02 |
|
|
28
|
+
| `0.1.7-rc.2` | Legacy | 2026-10-19 | 14 | 2026-11-02 |
|
|
29
|
+
| `0.2.0-rc.1` | Legacy | 2026-10-19 | 21 | 2026-11-09 |
|
|
30
|
+
| `0.2.0-rc.2` | Legacy | 2026-10-19 | 21 | 2026-11-09 |
|
|
31
|
+
| `0.2.1-alpha.1` | Legacy; independent capability-boundary exception | 2026-10-19 | 21 | 2026-11-09 |
|
|
32
|
+
| `0.2.1-alpha.2` | Legacy; independent capability-boundary exception | 2026-10-19 | 21 | 2026-11-09 |
|
|
33
|
+
| `0.2.1-alpha.3` | Supported | Not entered | Not applicable | Not specified |
|
|
34
|
+
| `0.2.1-alpha.4` | Supported | Not entered | Not applicable | Not specified |
|
|
35
|
+
| `0.2.1-alpha.5` | Supported | Not entered | Not applicable | Not specified |
|
|
36
|
+
| `0.2.1-rc.1` | Supported; new target | Not entered | Not applicable | Not specified |
|
|
37
|
+
| `0.2.1-rc.2` | Supported; new development/verification default target | Not entered | Not applicable | Not specified |
|
|
38
|
+
|
|
39
|
+
Use DSH `0.2.1-rc.2` with plugin `0.2.0` as the migration target, after checking its exact-version distribution record. Published `0.1.10` retains its historical declarations; it must not be republished to add the RCs.
|
|
40
|
+
|
|
41
|
+
## Dates and the Alpha/RC relationship
|
|
42
|
+
|
|
43
|
+
The general legacy window is **14 calendar days**. Development must explicitly announce any exception, its reason and duration. Do not derive the window from an alpha, RC or stable label; there is no general alpha seven-day or stable thirty-day policy.
|
|
44
|
+
|
|
45
|
+
Dates use `Asia/Shanghai`. Eligibility starts at local 00:00 on `legacySince + windowDays`: 2026-10-19 + 14 days = 2026-11-02; + 21 days = 2026-11-09. These are announced dates, not elapsed time since a user's installation, upstream release or plugin publication. An elapsed window grants eligibility for a later retirement release; it neither retires the version automatically nor requires retirement in the immediately following plugin release. Installed behavior never changes because the date passes.
|
|
46
|
+
|
|
47
|
+
Alpha releases of a base version follow its **entire RC release line**. While any RC remains normally supported, associated alphas do not automatically become legacy. When the last normally supported RC enters legacy, associated alphas without an independent announcement enter together and share its deadline. This rule covers `0.2.1-alpha.3`, `0.2.1-alpha.4` and `0.2.1-alpha.5`. The independent capability-boundary exceptions for `0.2.1-alpha.1` and `0.2.1-alpha.2` keep the announced 21-day dates; a later RC does not reset them.
|
|
48
|
+
|
|
49
|
+
## Add exact-version support
|
|
50
|
+
|
|
51
|
+
1. Development selects exact DSH releases. Check the actual registry packages, availability, integrity, matching tags, APIs and the installed DSH → WebApp → dependency chain. A Git tag, broad SemVer range, adjacent release or identical source is insufficient evidence of installation or compatibility.
|
|
52
|
+
2. Read the [compatibility inventory](legacy-compatibility.md). Update candidate dependencies, declarations, test targets, both inventory matrices and affected entries together. Preserve adaptations whose applicable releases still intersect support, and shared security checks.
|
|
53
|
+
3. Correct exact-version test branches and verify expected cases really register. Freeze one candidate tgz and record source identity, archive SHA-256, runtime composition, commands, test counts and reports. All current supported releases, including legacy, must pass CLI, full browser and isolated installation smoke against that same archive. An archive-affecting edit creates a new candidate and invalidates the previous final matrix.
|
|
54
|
+
4. Update bilingual user and development documents and the Unreleased changelog. Only publishing a newly versioned, verified plugin creates that released plugin's formal historical support record. Forward admission alone never adds a supported version.
|
|
55
|
+
|
|
56
|
+
## Announce entry into legacy
|
|
57
|
+
|
|
58
|
+
Development explicitly announces the exact release set, reason, legacy start, 14-day default or justified exception, eligibility date, migration target, feature limits and runtime-admission policy. Update declarations, history, README, inventory and operational guides together as applicable. A legacy announcement keeps the release supported and in release-blocking CI.
|
|
59
|
+
|
|
60
|
+
Maintain the promised authentication and feature boundaries, compatibility regression and security fixes throughout legacy, including after the eligibility date when retirement has not been scheduled. Record that continued legacy status rather than deleting verification jobs. Do not select dates from upstream publication or silently reset an earlier announcement.
|
|
61
|
+
|
|
62
|
+
## Execute actual retirement in a future release
|
|
63
|
+
|
|
64
|
+
Plugin `0.2.0` performs **no actual retirement**. A future retirement change must satisfy every item below in the same change:
|
|
65
|
+
|
|
66
|
+
1. Obtain development's explicit decision naming the exact releases and effective new plugin version, on or after each eligibility date. Record effective date, last supporting plugin version and verified distribution availability.
|
|
67
|
+
2. Provide migration and installation guidance. Separate maintenance withdrawal from technical refusal: visual/test-only adaptation removal does not by itself require blocking startup; missing necessary runtime or security contracts must refuse service.
|
|
68
|
+
3. Review each `dsh-runtime` entry's applicable versions against the resulting supported set. Keep it while the intersection is nonempty. When empty, remove its exclusive implementation and tests and update both inventory languages, both matrix directions and guides. Missing evidence requires obtaining exact-version evidence before retiring an adaptation. Keep shared authentication, origin, session, storage and transport checks.
|
|
69
|
+
4. Treat `plugin-contract` entries under their own migration policy. DSH retirement does not remove old plugin configuration such as `allowedOrigins`.
|
|
70
|
+
5. Update support declarations, CI, README, history, inventory and any necessary admission changes together. Record the effective retirement, last compatible plugin, upgrade path and actual runtime result; preserve historical rows.
|
|
71
|
+
6. Verify the final archive against every remaining supported release, and verify refusal cannot restore an unprotected native listener. Keep the independent profile safeguard and readiness checks in the [deployment guide](deployment.md).
|
|
72
|
+
|
|
73
|
+
An installed plugin must not retire versions by calendar timer. A scheduled CI run must not delete support or verification. Missing approval, dates, availability, adaptation evidence, deployment safeguards or final verification means retirement is not complete.
|
|
74
|
+
|
|
75
|
+
## Verification and delivery rules
|
|
76
|
+
|
|
77
|
+
Every pull request and main-branch check retains static, unit, integration and all-supported-release CLI/install smoke. The ordinary browser plan is permitted only for the explicit low-risk whitelist; source, shared behavior, dependencies, support documents, build/package/consumer mechanisms, unknown paths and uncertain diffs require full verification. Weekly verification at Monday 00:00 UTC (08:00 Asia/Shanghai), manual runs and releases use the full exact-version matrix. Representative ordinary checks do not replace another release's evidence.
|
|
78
|
+
|
|
79
|
+
Release verification must consume one immutable archive produced once after static/core checks. Independent jobs validate the same archive identity and SHA-256, restore its own `dist`, and run serial test files against isolated profiles. Reject failures, cancellations, unexpected skips and empty targeted suites. Publish depends on all required jobs and consumes the verified artifact without rebuilding or repacking. Real GitHub Actions results must be recorded separately from local workflow-equivalent checks.
|
|
80
|
+
|
|
81
|
+
See the [development guide](development.md) for verification commands and isolation, and the [release guide](releasing.md) for the publishing operation. Final production and same-archive verification use Node.js 24. Test credentials, task documents, profiles, screenshots and generated evidence stay outside the npm archive.
|
|
82
|
+
|
|
83
|
+
## Documentation and evidence responsibilities
|
|
84
|
+
|
|
85
|
+
The support policy defines decisions and operations. [Support history](support-history.md) provides [DSH → plugin](support-history.md#by-dsh) and [plugin → exact DSH](support-history.md#by-plugin) queries for all verifiable releases, availability, evidence grades, dates and installation guidance. The [compatibility inventory](legacy-compatibility.md) maintains feature → version and version → feature views, stable IDs, code/tests and adaptation retirement evidence. README lists current normal/legacy support and links to detailed queries; history survives removal from README.
|
|
86
|
+
|
|
87
|
+
Maintain these layers in English and Chinese for support additions, legacy announcements and actual retirement. Distinguish explicit historical declaration, real verification, technical admission only and unknown. Recommend only a verified available distribution; an old obtainable package is not thereby maintained or covered by current security verification. Record unavailable or missing evidence instead of inventing compatibility. Historical support must not be rewritten from a new candidate's manifest.
|