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
|
@@ -0,0 +1,97 @@
|
|
|
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
|
+
Start with [DSH → plugin](#by-dsh) or [plugin → DSH](#by-plugin). For current commitments, use the [support policy](support-policy.md) and [compatibility inventory](legacy-compatibility.md).
|
|
8
|
+
|
|
9
|
+
## Reading the evidence
|
|
10
|
+
|
|
11
|
+
- **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.
|
|
12
|
+
- **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.
|
|
13
|
+
- **R\***: a later README reports testing an earlier authentication implementation. It does not establish which old npm archive was exercised.
|
|
14
|
+
- **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.
|
|
15
|
+
- **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.
|
|
16
|
+
|
|
17
|
+
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.
|
|
18
|
+
|
|
19
|
+
Historical plugin rows are archived evidence, not continuously maintained per-version test matrices. DSH maintenance state is separate: plugin `0.2.0` keeps all eleven declared versions, including six legacy versions; none has actually retired. Legacy dates never automatically remove support. See the policy for exact dates and retirement requirements.
|
|
20
|
+
|
|
21
|
+
## Choosing an installation
|
|
22
|
+
|
|
23
|
+
For the eleven current DSH releases, select plugin **`0.2.0`** after its [exact registry endpoint](https://registry.npmjs.org/dsh-auth-remote/0.2.0) confirms availability. The release workflow verifies its final archive before publication. Follow the [deployment guide](deployment.md), including independent disabling of the native listener for protected remote use. The pre-release npm baseline was `0.1.10`, with nine declarations ending at `0.2.1-alpha.5`; historical availability does not make an old release preferred or newly verified.
|
|
24
|
+
|
|
25
|
+
DSH `0.2.1-rc.1` and `0.2.1-rc.2` require plugin `0.2.0`. During release preparation, use an explicitly verified source archive until publication succeeds. Version `0.2.0` does not change the bytes or promises of npm `0.1.10`, which must not be republished. No npm installation recommendation exists here for Git-only `0.1.4` or a DSH version with unknown history. Do not disable technical identity/API checks to force an old pair.
|
|
26
|
+
|
|
27
|
+
<a id="by-plugin"></a>
|
|
28
|
+
|
|
29
|
+
## Plugin → DSH
|
|
30
|
+
|
|
31
|
+
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.
|
|
32
|
+
|
|
33
|
+
| Plugin version / availability | Exact historical DSH evidence | Sources |
|
|
34
|
+
| ------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
35
|
+
| <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) |
|
|
36
|
+
| <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) |
|
|
37
|
+
| <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) |
|
|
38
|
+
| <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) |
|
|
39
|
+
| <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) |
|
|
40
|
+
| <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) |
|
|
41
|
+
| <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) |
|
|
42
|
+
| <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) |
|
|
43
|
+
| <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) |
|
|
44
|
+
| <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) |
|
|
45
|
+
| <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) |
|
|
46
|
+
| <a id="plugin-unreleased"></a><a id="plugin-0.2.0"></a>`0.2.0` — release version; check the exact registry endpoint for publication status | `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**. Its matching release workflow must record **V** for the final archive before publication; earlier candidate verification does not certify it. | [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) |
|
|
47
|
+
|
|
48
|
+
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`, the 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.
|
|
49
|
+
|
|
50
|
+
<a id="by-dsh"></a>
|
|
51
|
+
|
|
52
|
+
## DSH → plugin
|
|
53
|
+
|
|
54
|
+
Every registry-listed DSH version has its own stable anchor. The npm column lists historical source evidence, not newly rerun pairs; follow the plugin row for D/R/R\* details. Git-only `0.1.4` is kept separate. Every DSH archive below was retrievable with integrity verification at the check date. Unknown rows are below the current technical minimum and have no supported installation recommendation; the eleven current rows retain the maintenance state stated here.
|
|
55
|
+
|
|
56
|
+
| Exact DSH version / registry evidence | Plugin evidence; check distribution in plugin row | Git-only evidence | Current candidate state / choice |
|
|
57
|
+
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------- | ---------------------------------------------------------------- |
|
|
58
|
+
| <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 |
|
|
59
|
+
| <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 |
|
|
60
|
+
| <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 |
|
|
61
|
+
| <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 |
|
|
62
|
+
| <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 |
|
|
63
|
+
| <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 |
|
|
64
|
+
| <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 |
|
|
65
|
+
| <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 |
|
|
66
|
+
| <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 |
|
|
67
|
+
| <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 |
|
|
68
|
+
| <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 |
|
|
69
|
+
| <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 |
|
|
70
|
+
| <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 |
|
|
71
|
+
| <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 |
|
|
72
|
+
| <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 |
|
|
73
|
+
| <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 |
|
|
74
|
+
| <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 |
|
|
75
|
+
| <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 |
|
|
76
|
+
| <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 |
|
|
77
|
+
| <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 |
|
|
78
|
+
| <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 |
|
|
79
|
+
| <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 |
|
|
80
|
+
| <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 |
|
|
81
|
+
| <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 |
|
|
82
|
+
| <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 |
|
|
83
|
+
| <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` | Legacy; plugin `0.2.0` |
|
|
84
|
+
| <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` | Legacy; plugin `0.2.0` |
|
|
85
|
+
| <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` | Legacy; plugin `0.2.0` |
|
|
86
|
+
| <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` | Legacy; plugin `0.2.0` |
|
|
87
|
+
| <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` | Legacy; plugin `0.2.0`; R\* is not an old-archive recommendation |
|
|
88
|
+
| <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 | Legacy; plugin `0.2.0` |
|
|
89
|
+
| <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** | None found | Normal; plugin `0.2.0` |
|
|
90
|
+
| <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** | None found | Normal; plugin `0.2.0` |
|
|
91
|
+
| <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** | None found | Normal; plugin `0.2.0` |
|
|
92
|
+
| <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** | None found | Normal; plugin `0.2.0` |
|
|
93
|
+
| <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** | None found | Normal; plugin `0.2.0` |
|
|
94
|
+
|
|
95
|
+
## Maintaining this history
|
|
96
|
+
|
|
97
|
+
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,97 @@
|
|
|
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
|
+
从 [DSH → 插件](#by-dsh)或[插件 → DSH](#by-plugin)开始查询。当前承诺以[支持规范](support-policy.zh-CN.md)和[兼容库存](legacy-compatibility.zh-CN.md)为准。
|
|
8
|
+
|
|
9
|
+
## 如何阅读证据
|
|
10
|
+
|
|
11
|
+
- **D**:精确版本出现在所指 manifest 的 `dsh.compatibility.dshReleases`。各行单独标明已发布 npm 包、仅 Git tag 或未发布源码候选;声明本身不证明可获取性或实测通过。
|
|
12
|
+
- **R**:当时 README 将该精确 DSH 列为已测试或 CI 覆盖目标,tag 的 CI/runtime 也指向对应目标。这里只记录历史项目的报告,不声称取得了历史 Actions 成功记录,也不声称本次重跑了该旧归档。
|
|
13
|
+
- **R\***:后续 README 报告测试过较早的认证实现,没有证明当时使用了哪个旧 npm 归档。
|
|
14
|
+
- **V**:本轮开发对身份明确的候选归档进行了真实运行。同一 SHA-256 的十一版 Node.js 24 首轮 CLI、完整 browser 和安装 smoke 已通过;它只属于那个未发布候选,所有变更落定后的最终归档仍须重验。
|
|
15
|
+
- **未知**:在已核对的 npm manifest/README、Git tag、CI/runtime 和 changelog 中,没有找到该精确组合。仅满足 peer/runtime 范围表示技术准入,不能推导 D、R 或 V。表中未列组合也不等于已证明不兼容。
|
|
16
|
+
|
|
17
|
+
首轮 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。原始报告保留在维护者的归档外验证记录中。本文及后续文档晚于该归档,这条记录不认证修订后的最终包。
|
|
18
|
+
|
|
19
|
+
历史插件行是存档证据,并非持续维护的逐插件版本测试矩阵。DSH 维护层级单独判断:插件 `0.2.0` 仍声明十一版,其中六版 legacy,实际退役记录为空。日期到期不会自动移除支持;精确日期和退役要求见规范。
|
|
20
|
+
|
|
21
|
+
## 如何选择安装
|
|
22
|
+
|
|
23
|
+
对当前十一版 DSH,在[精确 registry 接口](https://registry.npmjs.org/dsh-auth-remote/0.2.0)确认可获取后选择插件 **`0.2.0`**。发布工作流须先验证最终归档,再执行发布。遵循[部署指南](deployment.zh-CN.md),包括受保护远程部署时独立禁用原生监听。发布前 registry 基线最新为 `0.1.10`,仅声明截至 `0.2.1-alpha.5` 的九版;历史包能下载不等于仍适合新部署或刚刚重新验证通过。
|
|
24
|
+
|
|
25
|
+
DSH `0.2.1-rc.1`、`0.2.1-rc.2` 需要插件 `0.2.0`。发布准备期间,在发布成功前使用明确验证过的源码归档。`0.2.0` 不改变 npm `0.1.10` 的字节或承诺,也不能重新发布既有版本。本文不为 Git-only `0.1.4` 或历史未知的 DSH 版本推荐 npm 安装;不要关闭包身份/API 技术检查来强行运行旧组合。
|
|
26
|
+
|
|
27
|
+
<a id="by-plugin"></a>
|
|
28
|
+
|
|
29
|
+
## 插件 → DSH
|
|
30
|
+
|
|
31
|
+
每个版本保留稳定的 `#plugin-<version>` 锚点。截至 `0.1.10` 的历史 npm 行均在上述基线可下载且 integrity 一致;manifest 和包内英文 README 与对应 tag 一致,除 npm 移除 `packageManager`。本次没有重跑这些历史 npm 归档。
|
|
32
|
+
|
|
33
|
+
| 插件版本 / 可获取性 | 精确历史 DSH 证据 | 来源 |
|
|
34
|
+
| ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
35
|
+
| <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) |
|
|
36
|
+
| <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) |
|
|
37
|
+
| <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) |
|
|
38
|
+
| <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) |
|
|
39
|
+
| <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) |
|
|
40
|
+
| <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) |
|
|
41
|
+
| <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) |
|
|
42
|
+
| <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) |
|
|
43
|
+
| <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) |
|
|
44
|
+
| <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) |
|
|
45
|
+
| <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) |
|
|
46
|
+
| <a id="plugin-unreleased"></a><a id="plugin-0.2.0"></a>`0.2.0` — 发布版本;通过精确 registry 接口核对发布状态 | `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) |
|
|
47
|
+
|
|
48
|
+
`0.1.0`、`0.1.1` 的 peer 上限为 `>=0.1.7-rc.1 <0.2.0-0`。从 `0.1.2` 开始,host peer/runtime 范围开放为 `>=0.1.7-rc.1`;npm `0.1.10` 还通过 `engines.dsh` 声明该范围。这些范围不能填补未知精确组合。`0.1.5` changelog 将更早 Git-only `0.1.4` 的条目重新编号,而且两个 tag 之间还存在测试修改,不能视为同一制品。
|
|
49
|
+
|
|
50
|
+
<a id="by-dsh"></a>
|
|
51
|
+
|
|
52
|
+
## DSH → 插件
|
|
53
|
+
|
|
54
|
+
每个 registry 中的 DSH 版本都有独立稳定锚点。npm 列记录历史来源,没有声称重新运行这些组合;D/R/R\* 详情见对应插件行。Git-only `0.1.4` 单独列出。下表每个 DSH 归档均在核对时可下载且 integrity 一致。未知行低于当前技术下限,没有受支持的安装推荐;当前十一版则保留表中的维护层级。
|
|
55
|
+
|
|
56
|
+
| 精确 DSH 版本 / registry 证据 | 插件证据;分发状态见插件行 | 仅 Git 证据 | 当前候选状态 / 选择 |
|
|
57
|
+
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------- | ---------------------------------------- |
|
|
58
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
59
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
60
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
61
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
62
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
63
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
64
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
65
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
66
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
67
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
68
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
69
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
70
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
71
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
72
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
73
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
74
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
75
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
76
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
77
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
78
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
79
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
80
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
81
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
82
|
+
| <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) | 未知 | 未找到 | 低于当前下限;不推荐 |
|
|
83
|
+
| <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` | Legacy;插件 `0.2.0` |
|
|
84
|
+
| <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` | Legacy;插件 `0.2.0` |
|
|
85
|
+
| <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` | Legacy;插件 `0.2.0` |
|
|
86
|
+
| <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` | Legacy;插件 `0.2.0` |
|
|
87
|
+
| <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` | Legacy;插件 `0.2.0`;R\* 不是旧归档推荐 |
|
|
88
|
+
| <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** | 未找到 | Legacy;插件 `0.2.0` |
|
|
89
|
+
| <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.2.0` |
|
|
90
|
+
| <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.2.0` |
|
|
91
|
+
| <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.2.0` |
|
|
92
|
+
| <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.2.0` |
|
|
93
|
+
| <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.2.0` |
|
|
94
|
+
|
|
95
|
+
## 如何维护历史
|
|
96
|
+
|
|
97
|
+
两种语言、两个方向的表均人工维护。重新核实 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.
|
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
# DSH 支持生命周期
|
|
2
|
+
|
|
3
|
+
[English](support-policy.md)
|
|
4
|
+
|
|
5
|
+
最后更新:2026-10-19。本规范区分维护承诺、精确版本验证和技术准入。插件 **`0.2.0`** 新增两个 `0.2.1` RC 的精确支持,新增 DSH 目标不扩写已发布插件 `0.1.10` 的历史支持。发布前必须验证最终 `0.2.0` 归档。
|
|
6
|
+
|
|
7
|
+
## 支持状态与运行准入
|
|
8
|
+
|
|
9
|
+
| 状态 | 维护与验证 | 运行行为 |
|
|
10
|
+
| ----------------------------------------------- | -------------------------------------------------- | ---------------------------------------------------- |
|
|
11
|
+
| 正常支持 | 维护已承诺功能,精确版本验证失败阻断发布 | 通过必要技术检查后运行 |
|
|
12
|
+
| Legacy,含窗口过期但尚未实际退役 | 继续已承诺功能、兼容回归与安全修复,验证仍阻断发布 | 通过技术检查后运行,提示维护日期和迁移建议 |
|
|
13
|
+
| 在某次插件发布中明确实际退役 | 撤销当前支持承诺和持续矩阵,保留历史证据 | 必要契约仍满足时可带提示尝试运行;准入不等于验证兼容 |
|
|
14
|
+
| 必要 API/行为缺失、必要适配已删除或安全检查失败 | 不宣称支持 | 拒绝提供受保护业务服务,给出升级或最后兼容插件路径 |
|
|
15
|
+
| 未评估的旧版或未来版 | 无精确支持承诺 | 执行技术检查;启动成功不增加支持版本 |
|
|
16
|
+
|
|
17
|
+
`dsh.compatibility.dshReleases` 记录精确支持声明;`engines.dsh`、DSH peer 和运行检查表达技术准入。插件 `0.2.0` 保持 `>=0.1.7-rc.1`(含预发布),同时检查包身份和必要 API。日历或纯维护退役不能机械提高下限。当前真实退役记录为空。
|
|
18
|
+
|
|
19
|
+
诊断应在启动日志中、提供受保护服务前输出:legacy 日期和迁移建议,或获准启动的未验证/已退役版本缺少当前支持承诺。同一进程每个精确版本/状态组合至多提示一次,HMR 也不重置。诊断不改变认证、登录弹窗、请求授权或 CLI JSON。
|
|
20
|
+
|
|
21
|
+
## 已公告的维护日期
|
|
22
|
+
|
|
23
|
+
以下日期由研发明确指定,实施延后不重新起算。十一版均继续支持;legacy 不移出验证。每次发布前须完成真实同包验证。
|
|
24
|
+
|
|
25
|
+
| 精确 DSH 版本 | 维护状态 | Legacy 起算日 | 窗口自然日数 | 最早可执行退役日期 |
|
|
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,独立能力边界例外 | 2026-10-19 | 21 | 2026-11-09 |
|
|
32
|
+
| `0.2.1-alpha.2` | Legacy,独立能力边界例外 | 2026-10-19 | 21 | 2026-11-09 |
|
|
33
|
+
| `0.2.1-alpha.3` | 正常支持 | 未进入 | 不适用 | 未指定 |
|
|
34
|
+
| `0.2.1-alpha.4` | 正常支持 | 未进入 | 不适用 | 未指定 |
|
|
35
|
+
| `0.2.1-alpha.5` | 正常支持 | 未进入 | 不适用 | 未指定 |
|
|
36
|
+
| `0.2.1-rc.1` | 正常支持;新增目标 | 未进入 | 不适用 | 未指定 |
|
|
37
|
+
| `0.2.1-rc.2` | 正常支持;新开发及验证默认目标 | 未进入 | 不适用 | 未指定 |
|
|
38
|
+
|
|
39
|
+
迁移目标为 DSH `0.2.1-rc.2` 与插件 `0.2.0`,使用前核对精确版本的分发记录。已发布 `0.1.10` 保留原历史声明,不得通过重发该版本增加 RC。
|
|
40
|
+
|
|
41
|
+
## 日期与 Alpha/RC 关联
|
|
42
|
+
|
|
43
|
+
一般 legacy 窗口为 **14 个自然日**。任何例外须由研发明确公告理由与期限,不按 alpha、RC 或正式版标签推算;不存在通用的 alpha 七天或正式版三十天政策。
|
|
44
|
+
|
|
45
|
+
日期使用 `Asia/Shanghai`。资格从 `legacySince + windowDays` 当地 00:00 起成立:2026-10-19 加 14 天为 2026-11-02,加 21 天为 2026-11-09。这是公告日期,不是自用户安装、上游发布或插件发布起算。窗口过期仅取得后续退役发布资格,不自动退役,也不强制在紧接着的插件发布退役。已安装插件行为不随日期改变。
|
|
46
|
+
|
|
47
|
+
同一基础版本的 alpha 跟随**整条 RC 发布线**:仍有任一正常支持 RC 时,关联 alpha 不自动进入 legacy。最后一个正常支持 RC 进入 legacy 时,未独立公告的关联 alpha 同时进入并共享截止日期。此规则适用于 `0.2.1-alpha.3`、`0.2.1-alpha.4`、`0.2.1-alpha.5`。`0.2.1-alpha.1`、`0.2.1-alpha.2` 使用独立能力边界例外,保留已公告的 21 天日期,后续 RC 不重新计时。
|
|
48
|
+
|
|
49
|
+
## 新增精确版本支持
|
|
50
|
+
|
|
51
|
+
1. 研发选择精确 DSH 版本。核对实际 registry 发布包、可获取性、完整性、对应 tag、API 以及安装后的 DSH → WebApp → 依赖链。Git tag、宽泛 SemVer、相邻版本或相同源码不足以证明可安装或兼容。
|
|
52
|
+
2. 阅读[兼容维护清单](legacy-compatibility.zh-CN.md)。同步候选依赖、声明、测试目标、两个库存矩阵和受影响条目;适用集合与支持集合仍有交集时保留适配,并保留共享安全检查。
|
|
53
|
+
3. 修正精确版本测试分支,确认预期用例真实注册。冻结一个候选 tgz,记录源码身份、归档 SHA-256、运行时组合、命令、测试数量和报告。所有当前支持版本(含 legacy)须使用同一归档通过 CLI、完整浏览器和隔离安装 smoke。影响归档的改动产生新候选,原最终矩阵随即失效。
|
|
54
|
+
4. 同步双语用户/开发文档及 Unreleased。只有发布已验证的新插件版本,才形成该已发布插件的正式历史支持记录;前向准入不增加支持版本。
|
|
55
|
+
|
|
56
|
+
## 公告进入 legacy
|
|
57
|
+
|
|
58
|
+
研发明确公告精确集合、原因、起算日、默认 14 天或有理由的例外、资格日、迁移目标、功能限制与运行准入政策。按影响同步声明、历史、README、库存及操作指南。Legacy 公告保持版本受支持,并保留发布阻断 CI。
|
|
59
|
+
|
|
60
|
+
整个 legacy 期间继续维护已承诺的认证和功能边界、兼容回归及安全修复;取得资格但尚未安排实际退役时也一样。记录继续 legacy,而不是删除验证任务。不得从上游发布日期选择日期或悄悄重置既有公告。
|
|
61
|
+
|
|
62
|
+
## 在未来发布中执行实际退役
|
|
63
|
+
|
|
64
|
+
插件 `0.2.0` **不执行实际退役**。未来退役变更须在同次变更满足以下所有项目:
|
|
65
|
+
|
|
66
|
+
1. 研发明确选定精确集合和生效新插件版本,时间不早于各资格日。记录生效日期、最后支持插件版本和已核实的分发可获取性。
|
|
67
|
+
2. 提供迁移和安装说明。区分维护退出与技术拒绝:删除视觉/测试专属适配本身不必阻止启动;缺少必要运行或安全契约必须拒绝服务。
|
|
68
|
+
3. 逐条比较 `dsh-runtime` 适用集合与结果支持集合;交集非空就保留,交集为空则同次删除独占实现和测试并同步中英文库存、两个方向矩阵及指南。缺证据须先取得精确版本证据,不能提前退役适配;保留共享认证、来源、会话、存储和传输检查。
|
|
69
|
+
4. `plugin-contract` 按其独立迁移政策处理。DSH 退役不移除 `allowedOrigins` 等旧插件配置。
|
|
70
|
+
5. 同步支持声明、CI、README、历史、库存及必要准入调整。记录实际退役、生效版本、最后兼容插件、升级路径和真实运行结果;保留历史行。
|
|
71
|
+
6. 对剩余全部支持版本验证最终归档,并验证拒绝路径不恢复未受保护的原生监听。保留[部署指南](deployment.zh-CN.md)中的独立 profile 保障与 readiness 检查。
|
|
72
|
+
|
|
73
|
+
已安装插件不得按日历定时退役;定时 CI 不得删除支持或验证。批准、日期、可获取性、适配证据、部署保障或最终验证缺少任何一项,都不能认定退役完成。
|
|
74
|
+
|
|
75
|
+
## 验证与交付规则
|
|
76
|
+
|
|
77
|
+
所有 PR 和主分支检查保留静态、单元、集成,以及全部支持版本的 CLI/安装 smoke。普通 browser 计划仅适用于明确低风险白名单;源码、共享行为、依赖、支持文档、构建/打包/消费机制、未知路径和不可靠差异均须全量。每周一 UTC 00:00(北京时间 08:00)、手动执行和发布固定全量精确版本矩阵。普通计划的代表验证不能替代其他版本的证据。
|
|
78
|
+
|
|
79
|
+
发布验证消费静态/核心检查后一次性生产的不可变归档。独立 job 核验相同归档身份和 SHA-256,恢复该包自己的 `dist`,并在隔离 profile 上串行运行文件。失败、取消、非预期跳过和零用例专项均须拒绝。发布依赖全部必要任务,消费已验证 artifact,不重新构建或打包。真实 GitHub Actions 结果与本地等价检查分别记录。
|
|
80
|
+
|
|
81
|
+
验证命令与隔离方式见[开发指南](development.zh-CN.md),发布操作见[发布指南](releasing.zh-CN.md)。最终生产和同包验证使用 Node.js 24。测试凭据、任务文档、profile、截图和生成证据均不进入 npm 归档。
|
|
82
|
+
|
|
83
|
+
## 文档与证据职责
|
|
84
|
+
|
|
85
|
+
支持规范定义决策和操作;[支持历史](support-history.zh-CN.md)提供全部可核实发布版本的 [DSH → 插件](support-history.zh-CN.md#by-dsh)及[插件 → 精确 DSH](support-history.zh-CN.md#by-plugin)查询,包含可获取性、证据等级、日期和安装建议;[兼容维护清单](legacy-compatibility.zh-CN.md)维护功能 → 版本、版本 → 功能、稳定 ID、代码/测试与适配退役证据。README 只列当前正常/legacy 支持并链接明细查询;退出 README 不删除历史。
|
|
86
|
+
|
|
87
|
+
新增支持、legacy 公告和实际退役时同时维护这三个层次的中英文。区分历史明确声明、真实验证、仅技术准入与未知。只推荐已有证据且可获取的分发包;旧包仍可下载不等于仍在维护或已通过当前安全验证。缺失或不可获取时如实记录,不编造兼容。不能用新候选 manifest 重写历史发布支持。
|
|
@@ -5,7 +5,8 @@
|
|
|
5
5
|
# DSH 0.2.1-alpha.2, 0.2.1-alpha.3, 0.2.1-alpha.4 and 0.2.1-alpha.5 support native TLS.
|
|
6
6
|
# Supply both tlsCert and tlsKey; relative file paths
|
|
7
7
|
# resolve from this profile directory, while CLI TLS paths resolve from cwd.
|
|
8
|
-
#
|
|
8
|
+
# This independent disable is required for a protected remote deployment:
|
|
9
|
+
# it remains effective if Loader skips the authentication bundle.
|
|
9
10
|
- id: webserver
|
|
10
11
|
disabled: true
|
|
11
12
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-auth-remote",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
4
4
|
"description": "Single-user remote authentication for DeepSeek Harness: password, TOTP and revocable sessions.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -49,6 +49,10 @@
|
|
|
49
49
|
"docs/development.zh-CN.md",
|
|
50
50
|
"docs/legacy-compatibility.md",
|
|
51
51
|
"docs/legacy-compatibility.zh-CN.md",
|
|
52
|
+
"docs/support-policy.md",
|
|
53
|
+
"docs/support-policy.zh-CN.md",
|
|
54
|
+
"docs/support-history.md",
|
|
55
|
+
"docs/support-history.zh-CN.md",
|
|
52
56
|
"docs/releasing.md",
|
|
53
57
|
"docs/releasing.zh-CN.md",
|
|
54
58
|
"docs/reverse-proxy.md",
|
|
@@ -61,18 +65,18 @@
|
|
|
61
65
|
"@deepseek-ai/schemastery": ">=3.18.4 <4"
|
|
62
66
|
},
|
|
63
67
|
"devDependencies": {
|
|
64
|
-
"@deepseek-ai/cordis": "4.0.5
|
|
65
|
-
"@deepseek-ai/dsh-authorization": "0.2.1-
|
|
66
|
-
"@deepseek-ai/dsh-client-connection": "0.2.1-
|
|
67
|
-
"@deepseek-ai/dsh-client-locale": "0.2.1-
|
|
68
|
-
"@deepseek-ai/dsh-client-ui-settings": "0.2.1-
|
|
69
|
-
"@deepseek-ai/dsh-client-ui-slots": "0.2.1-
|
|
70
|
-
"@deepseek-ai/dsh-deepseek-account": "0.2.1-
|
|
71
|
-
"@deepseek-ai/dsh-deepseek-account-platform": "0.2.1-
|
|
72
|
-
"@deepseek-ai/dsh-host-webserver": "0.2.1-
|
|
73
|
-
"@deepseek-ai/dsh-llm": "0.2.1-
|
|
74
|
-
"@deepseek-ai/dsh-scope": "0.2.1-
|
|
75
|
-
"@deepseek-ai/schemastery": "3.18.5
|
|
68
|
+
"@deepseek-ai/cordis": "4.0.5",
|
|
69
|
+
"@deepseek-ai/dsh-authorization": "0.2.1-rc.2",
|
|
70
|
+
"@deepseek-ai/dsh-client-connection": "0.2.1-rc.2",
|
|
71
|
+
"@deepseek-ai/dsh-client-locale": "0.2.1-rc.2",
|
|
72
|
+
"@deepseek-ai/dsh-client-ui-settings": "0.2.1-rc.2",
|
|
73
|
+
"@deepseek-ai/dsh-client-ui-slots": "0.2.1-rc.2",
|
|
74
|
+
"@deepseek-ai/dsh-deepseek-account": "0.2.1-rc.2",
|
|
75
|
+
"@deepseek-ai/dsh-deepseek-account-platform": "0.2.1-rc.2",
|
|
76
|
+
"@deepseek-ai/dsh-host-webserver": "0.2.1-rc.2",
|
|
77
|
+
"@deepseek-ai/dsh-llm": "0.2.1-rc.2",
|
|
78
|
+
"@deepseek-ai/dsh-scope": "0.2.1-rc.2",
|
|
79
|
+
"@deepseek-ai/schemastery": "3.18.5",
|
|
76
80
|
"@playwright/test": "1.63.0",
|
|
77
81
|
"@types/node": "24.13.6",
|
|
78
82
|
"@types/qrcode": "1.5.6",
|
|
@@ -109,7 +113,9 @@
|
|
|
109
113
|
"0.2.1-alpha.2": "compatible",
|
|
110
114
|
"0.2.1-alpha.3": "compatible",
|
|
111
115
|
"0.2.1-alpha.4": "compatible",
|
|
112
|
-
"0.2.1-alpha.5": "compatible"
|
|
116
|
+
"0.2.1-alpha.5": "compatible",
|
|
117
|
+
"0.2.1-rc.1": "compatible",
|
|
118
|
+
"0.2.1-rc.2": "compatible"
|
|
113
119
|
}
|
|
114
120
|
}
|
|
115
121
|
},
|
|
@@ -138,6 +144,7 @@
|
|
|
138
144
|
"release:pack": "pnpm check:static && node scripts/pack.mjs",
|
|
139
145
|
"pack:local": "pnpm release:pack",
|
|
140
146
|
"smoke:packed": "pnpm dev:prepare && node scripts/dev-install.mjs && node scripts/smoke.mjs",
|
|
141
|
-
"smoke": "pnpm pack:local && pnpm smoke:packed"
|
|
147
|
+
"smoke": "pnpm pack:local && pnpm smoke:packed",
|
|
148
|
+
"verify:packed": "node scripts/verify-packed.mjs"
|
|
142
149
|
}
|
|
143
150
|
}
|