dsh-update-status 0.4.5 → 0.4.7
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 +18 -0
- package/README.md +17 -14
- package/README.zh.md +18 -15
- package/docs/service-supervision.md +1 -1
- package/lib/client.js +2 -164
- package/lib/client.js.map +1 -1
- package/lib/index.js +62 -8
- package/package.json +3 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,24 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project are documented here.
|
|
4
4
|
|
|
5
|
+
## 0.4.7 — 2026-10-24
|
|
6
|
+
|
|
7
|
+
Verified DeepSeek Harness: `0.2.1-rc.3`; retains all ten previously verified releases. Engine and peer ranges remain unchanged. Release notes: [`docs/releases/v0.4.7.md`](docs/releases/v0.4.7.md).
|
|
8
|
+
|
|
9
|
+
- **Removes the redundant Settings → Version & updates menu.** Installation still shows the sidebar version chip and update notices by default; click the chip for status, manual checks, cache duration, upgrade guidance and guarded restart. The generic settings page remains suppressed. Existing profile preferences remain compatible and are never rewritten on mount.
|
|
10
|
+
- **Why:** installation already enables version status and update notices, and the chip detail panel provides the same primary actions. Removing the duplicate page simplifies Settings. The page-only visibility toggle and service-start-time display are removed with it; no new automatic behavior is introduced.
|
|
11
|
+
- Removes the settings-only component, styles and translations; restart recovery rendering tests now exercise the remaining detail panel. All 219 tests pass.
|
|
12
|
+
- **Existing hidden profiles:** a persisted `sidebarEnabled: false` remains respected. Set it to `true` or remove that override to restore the default chip; no automatic preference migration runs.
|
|
13
|
+
|
|
14
|
+
## 0.4.6 — 2026-10-23
|
|
15
|
+
|
|
16
|
+
Verified DeepSeek Harness: `0.2.1-rc.3`; retains all ten previously verified releases, including `0.2.1-rc.2`. Release notes: [`docs/releases/v0.4.6.md`](docs/releases/v0.4.6.md).
|
|
17
|
+
|
|
18
|
+
- **Declares DSH `0.2.1-rc.3` verified compatible.** The existing engine and peer ranges remain unchanged.
|
|
19
|
+
- **Shows restart-storm guidance instead of an invalid-payload error.** The client now accepts the Host's `supervisor-thrashing` refusal, preserving its reason and copy-only recovery commands. Regression tests cover every declared refusal through status, check and request responses. No automatic recovery or restart-policy bypass was added.
|
|
20
|
+
- **Includes rc.3 background work in restart confirmation.** Idle-looking agents can still own maintenance; the check now observes `whenIdle()` without waiting indefinitely. Terminal ownership activity also covers unpublished spawns. Unreadable probes refuse the restart, and active work still requires explicit force confirmation.
|
|
21
|
+
- **Synchronizes release information.** Both READMEs, their current version and compatibility tables, upgrade commands, release-note links and verified-release counts are updated together. The npm tarball is checked against the release build after publication.
|
|
22
|
+
|
|
5
23
|
## 0.4.5 — 2026-10-17
|
|
6
24
|
|
|
7
25
|
Verified DeepSeek Harness: `0.2.1-rc.2` (the current release), also `0.2.1-alpha.5`, `0.2.1-alpha.4`, `0.2.1-alpha.3`, `0.2.1-alpha.1`, `0.2.0-rc.2`, `0.2.0-rc.1`, `0.1.7-rc.2`, `0.1.7-rc.1` and `0.1.7-alpha.2`. Release notes: [`docs/releases/v0.4.5.md`](docs/releases/v0.4.5.md).
|
package/README.md
CHANGED
|
@@ -41,7 +41,7 @@ It shadows only the expanded sidebar brand name with `DeepSeek` plus a compact v
|
|
|
41
41
|
- **Neutral chip surface** — the chip is a grey second-level surface in both themes (`#f1f3f5` light / `#353638` dark) with the theme's normal label colour, so the dark shell gets a dark grey chip with white text rather than a white pill that hides the amber halo.
|
|
42
42
|
- **Light, dark, or system — followed automatically** — every colour the plugin renders is a DSH semantic token, so the chip, the dot, its halo and the panel all resolve through whatever appearance DSH is using. Set DSH to light, to dark, or to system and the plugin switches with the shell: no plugin-side theme setting, no media query to keep in sync. Hover lifts the chip in both directions (darkened in light mode, lightened in dark mode) by mixing the theme's label colour into the surface.
|
|
43
43
|
- **One release line, zero configuration** — reads npm's dist-tags in one registry request and keeps only the newest published version, stable, release candidate or alpha alike. There is no channel to follow and no choice to make.
|
|
44
|
-
- **An honest prerelease comparison** — the running version and that newest version are ordered with SemVer, so `0.2.1-rc.
|
|
44
|
+
- **An honest prerelease comparison** — the running version and that newest version are ordered with SemVer, so `0.2.1-rc.3` outranks `0.2.0-rc.2` and a release candidate still sorts below its own stable release.
|
|
45
45
|
- **Compatibility labels** — a release this plugin was verified against is marked verified; an untested newer one is marked unverified rather than claimed safe, and that advisory never repaints the chip.
|
|
46
46
|
- **Copy-only guidance** — generates an installation-kind-aware command for the exact newer version it found, never a dist-tag that can move, and never executes it.
|
|
47
47
|
- **Cache without polling** — one Host check on mount, a configurable 30–1,440 minute cache, single-flight registry access, and no frontend polling. Only the Check for updates button bypasses the cache.
|
|
@@ -54,7 +54,7 @@ Requirements:
|
|
|
54
54
|
|
|
55
55
|
- DeepSeek Harness with the Web profile
|
|
56
56
|
- Node.js 20 or newer
|
|
57
|
-
- Verified DSH releases: `0.2.1-rc.
|
|
57
|
+
- Verified DSH releases: `0.2.1-rc.3` (current), `0.2.1-rc.2`, `0.2.1-alpha.5`, `0.2.1-alpha.4`, `0.2.1-alpha.3`, `0.2.1-alpha.1`, `0.2.0-rc.2`, `0.2.0-rc.1`, `0.1.7-rc.2`, `0.1.7-rc.1` and `0.1.7-alpha.2`
|
|
58
58
|
|
|
59
59
|
With an installed `dsh` command:
|
|
60
60
|
|
|
@@ -92,7 +92,7 @@ dsh plugin --profile web add "link:$(pwd)"
|
|
|
92
92
|
Example commands generated for a global install:
|
|
93
93
|
|
|
94
94
|
```sh
|
|
95
|
-
npm install -g @deepseek-ai/dsh@0.2.1-rc.
|
|
95
|
+
npm install -g @deepseek-ai/dsh@0.2.1-rc.3
|
|
96
96
|
```
|
|
97
97
|
|
|
98
98
|
The plugin displays one command that matches the detected installation kind and names the exact release it found. It does not run it.
|
|
@@ -119,10 +119,10 @@ The chip itself is a neutral second-level surface — grey in both themes, with
|
|
|
119
119
|
The plugin asks the npm registry for `@deepseek-ai/dsh` once per cache window, keeps the **newest version any dist-tag points at**, and compares it with the running release. `latest`, `next` and `alpha` are npm bookkeeping, not a user choice: a newer release is reported whichever tag carries it.
|
|
120
120
|
|
|
121
121
|
- The highest SemVer wins, prereleases included, so an `alpha` ahead of the stable line is offered rather than hidden.
|
|
122
|
-
- The comparison is exact: `0.2.1-rc.
|
|
122
|
+
- The comparison is exact: `0.2.1-rc.3` is newer than `0.2.0-rc.2`, and both sort below `0.2.1`.
|
|
123
123
|
- A dist-tag the plugin has never heard of still counts — the read takes every tag npm returns, not a fixed triple.
|
|
124
124
|
- Only a version this plugin was verified against is labelled verified. An untested newer release is offered with an *unverified* advisory (`notice`, which never repaints the chip).
|
|
125
|
-
- The panel
|
|
125
|
+
- The detail panel renders one answer; the upgrade command names the exact version found.
|
|
126
126
|
|
|
127
127
|
Nothing here installs anything. Choosing to follow a channel — and the `channel` preference that stored it — was removed in `0.2.0`.
|
|
128
128
|
|
|
@@ -147,7 +147,7 @@ dsh plugin --profile web exec dsh-update-status-service activate
|
|
|
147
147
|
|
|
148
148
|
`activate` stops if the port is still busy instead of killing anything, so the DSH you are already using is never taken down by surprise. It also checks afterwards that the service it just started really took over; a service that begins failing immediately is reported as a failure, not as a success. From then on, **Restart** lists what is running, asks for a second confirmation when something is, and lets DSH exit; the service starts it again and the page comes back on its own.
|
|
149
149
|
|
|
150
|
-
Only one thing may start DSH Web on that port. If another tool starts its own `dsh web` — a second plugin's restart helper, a `nohup` script — that process holds the port while your service keeps failing to start. The plugin asks your operating system which process the service really owns, so **Restart** stays disabled in that state instead of promising a recovery that cannot happen, and it shows the two copy-only commands that fix it: one to find whoever holds the port, one to give the service back. The generated service also stops after a few failed starts in a row rather than respawning forever, and writes the reason to its log.
|
|
150
|
+
Only one thing may start DSH Web on that port. If another tool starts its own `dsh web` — a second plugin's restart helper, a `nohup` script — that process holds the port while your service keeps failing to start. The plugin asks your operating system which process the service really owns, so **Restart** stays disabled in that state instead of promising a recovery that cannot happen, and it shows the two copy-only commands that fix it: one to find whoever holds the port, one to give the service back. The generated service also stops after a few failed starts in a row rather than respawning forever, and writes the reason to its log. More detail: [user-service supervision](docs/service-supervision.md).
|
|
151
151
|
|
|
152
152
|
| Platform | User-level owner | Starts | Restart works after setup | Notes |
|
|
153
153
|
| --- | --- | --- | --- | --- |
|
|
@@ -161,24 +161,26 @@ A restart interrupts running work and does not save it. If DSH cannot list what
|
|
|
161
161
|
|
|
162
162
|
## LAN / non-loopback pages
|
|
163
163
|
|
|
164
|
-
DSH
|
|
164
|
+
Earlier DSH releases restricted non-loopback settings forms to memory-only state. DSH `0.2.1-rc.3` no longer exposes that `mode` field in form snapshots: the official entry-addressed form calls the settings Remote directly. Do not infer current persistence or authorization from an origin check alone; the running Host's settings policy decides whether a write is accepted.
|
|
165
165
|
|
|
166
166
|
From `0.1.2` this plugin is fully usable there anyway:
|
|
167
167
|
|
|
168
168
|
- The version/update **status** is fetched normally. Earlier releases gated the whole feature on `connection.isLoopback === true`, so a page reached through a LAN bridge (`dsh-bridge`, `dsh-lan-proxy`, …) never sent `POST /api/dsh-update-status.get-status`, could not open the detail panel, and showed this bundle's declared compatible release as if it were the running version. That gate is gone — the Connection RPC is authenticated and the Host route is the plugin's own.
|
|
169
169
|
- **Preferences** (`sidebarEnabled`, `cacheTtlMinutes`) keep reading and writing the ONE shared Host settings entry `dsh-update-status`, through the same public Remote the official settings form speaks (`settings.describe` / `settings.mutate`). Writes stay revision-fenced, and a refused write surfaces as a conflict instead of a silent overwrite. The direct channel opens only when the official form reports `unavailable`, so a loopback page keeps the official path and pays no extra wire read.
|
|
170
170
|
|
|
171
|
-
|
|
171
|
+
A LAN bridge must preserve DSH's authenticated transport and Host authorization policy. This plugin does not change bridge configuration or grant settings access; a Host refusal must be resolved by the deployment operator.
|
|
172
172
|
|
|
173
173
|
## Compatibility
|
|
174
174
|
|
|
175
|
-
Current release: plugin **`0.4.
|
|
175
|
+
Current release: plugin **`0.4.7`** is verified against DeepSeek Harness **`0.2.1-rc.3`** (the current release), **`0.2.1-rc.2`**, **`0.2.1-alpha.5`**, **`0.2.1-alpha.4`**, **`0.2.1-alpha.3`**, **`0.2.1-alpha.1`**, **`0.2.0-rc.2`**, **`0.2.0-rc.1`**, **`0.1.7-rc.2`**, **`0.1.7-rc.1`** and **`0.1.7-alpha.2`**.
|
|
176
176
|
|
|
177
177
|
### Which plugin version goes with which DeepSeek Harness version
|
|
178
178
|
|
|
179
179
|
| Plugin | Verified DeepSeek Harness | On npm | What that version is |
|
|
180
180
|
| --- | --- | --- | --- |
|
|
181
|
-
| **`0.4.
|
|
181
|
+
| **`0.4.7`** | `0.2.1-rc.3`, `0.2.1-rc.2`, `0.2.1-alpha.5`, `0.2.1-alpha.4`, `0.2.1-alpha.3`, `0.2.1-alpha.1`, `0.2.0-rc.2`, `0.2.0-rc.1`, `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | `latest` | Removes the redundant settings menu; version status and update notices remain on by default, with details in the sidebar chip panel |
|
|
182
|
+
| **`0.4.6`** | `0.2.1-rc.3`, `0.2.1-rc.2`, `0.2.1-alpha.5`, `0.2.1-alpha.4`, `0.2.1-alpha.3`, `0.2.1-alpha.1`, `0.2.0-rc.2`, `0.2.0-rc.1`, `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Verifies DSH `0.2.1-rc.3`, includes maintenance and starting terminals in restart confirmation, and restores restart-storm recovery guidance |
|
|
183
|
+
| **`0.4.5`** | `0.2.1-rc.2`, `0.2.1-alpha.5`, `0.2.1-alpha.4`, `0.2.1-alpha.3`, `0.2.1-alpha.1`, `0.2.0-rc.2`, `0.2.0-rc.1`, `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Compatibility declaration for DSH `0.2.1-rc.2`; no functional code changed, both READMEs were re-checked, and the published package was compared with the repository |
|
|
182
184
|
| **`0.4.4`** | `0.2.1-alpha.5`, `0.2.1-alpha.4`, `0.2.1-alpha.3`, `0.2.1-alpha.1`, `0.2.0-rc.2`, `0.2.0-rc.1`, `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Compatibility declaration for DSH `0.2.1-alpha.5`; no functional code changed, and both READMEs were re-checked for stale version numbers |
|
|
183
185
|
| **`0.4.3`** | `0.2.1-alpha.4`, `0.2.1-alpha.3`, `0.2.1-alpha.1`, `0.2.0-rc.2`, `0.2.0-rc.1`, `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Compatibility declaration for DSH `0.2.1-alpha.4`; no functional code changed, and the panel now shows this running release as verified compatible |
|
|
184
186
|
| **`0.4.2`** | `0.2.1-alpha.3`, `0.2.1-alpha.1`, `0.2.0-rc.2`, `0.2.0-rc.1`, `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Compatibility declaration for DSH `0.2.1-alpha.3`; no functional code changed, and the panel now shows this running release as verified compatible |
|
|
@@ -209,6 +211,7 @@ Current release: plugin **`0.4.5`** is verified against DeepSeek Harness **`0.2.
|
|
|
209
211
|
- Match them explicitly when it matters:
|
|
210
212
|
|
|
211
213
|
```sh
|
|
214
|
+
dsh plugin --profile web add dsh-update-status@0.4.7 # DSH 0.2.1-rc.3, 0.2.1-rc.2, 0.2.1-alpha.5, 0.2.1-alpha.4, 0.2.1-alpha.3, 0.2.1-alpha.1, 0.2.0-rc.2, 0.2.0-rc.1, 0.1.7-rc.2, 0.1.7-rc.1 or 0.1.7-alpha.2
|
|
212
215
|
dsh plugin --profile web add dsh-update-status@0.4.5 # DSH 0.2.1-rc.2, 0.2.1-alpha.5, 0.2.1-alpha.4, 0.2.1-alpha.3, 0.2.1-alpha.1, 0.2.0-rc.2, 0.2.0-rc.1, 0.1.7-rc.2, 0.1.7-rc.1 or 0.1.7-alpha.2
|
|
213
216
|
dsh plugin --profile web add dsh-update-status@0.4.4 # DSH 0.2.1-alpha.5, 0.2.1-alpha.4, 0.2.1-alpha.3, 0.2.1-alpha.1, 0.2.0-rc.2, 0.2.0-rc.1, 0.1.7-rc.2, 0.1.7-rc.1 or 0.1.7-alpha.2
|
|
214
217
|
dsh plugin --profile web add dsh-update-status@0.4.3 # DSH 0.2.1-alpha.4, 0.2.1-alpha.3, 0.2.1-alpha.1, 0.2.0-rc.2, 0.2.0-rc.1, 0.1.7-rc.2, 0.1.7-rc.1 or 0.1.7-alpha.2
|
|
@@ -228,9 +231,9 @@ Current release: plugin **`0.4.5`** is verified against DeepSeek Harness **`0.2.
|
|
|
228
231
|
```
|
|
229
232
|
|
|
230
233
|
- Two declarations make the verified lines load at all, and a test keeps them honest:
|
|
231
|
-
- `dsh.engines.dsh` and `peerDependencies['@deepseek-ai/dsh-settings']` both declare `>=0.1.7-alpha.2 <0.3.0`, which admits all
|
|
234
|
+
- `dsh.engines.dsh` and `peerDependencies['@deepseek-ai/dsh-settings']` both declare `>=0.1.7-alpha.2 <0.3.0`, which admits all eleven verified releases. The lower bound names the alpha on purpose — under node-semver's default prerelease rule a range like `>=0.1.6-0 <0.2.0` does **not** admit `0.1.7-alpha.2`. The upper bound moved from `<0.2.0` to `<0.3.0` in `0.1.11` for the mirror-image reason: DSH refuses an incompatible bundle at profile load, and a plain `<0.2.0` excludes the `0.2.0` stable, so the day DSH `0.2.0` shipped the plugin would have been silently dropped. DSH evaluates the range with `includePrerelease: true`, so `0.2.0-rc.2` was already inside it and `0.1.12` needed no range change; conversely, a bundle that enumerates `... || 0.2.0-rc.1 || >=0.2.0 <0.3.0` is refused on rc.2, because `>=0.2.0` does not admit a `0.2.0` prerelease.
|
|
232
235
|
- `@deepseek-ai/schemastery` is a **peer**, not a plain dependency: DSH 0.1.7 resolves only a linked plugin's peer dependencies from the running installation, so a `link:` install of this directory would otherwise fail to import the Host half.
|
|
233
|
-
- Per-release notes — what changed, who is affected, what to do — are hand-written in Chinese and English and become the GitHub Release body: [`v0.4.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.5.md) · [`v0.4.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.4.md) · [`v0.4.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.3.md) · [`v0.4.2`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.2.md) · [`v0.4.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.1.md) · [`v0.4.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.0.md) · [`v0.3.2`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.2.md) · [`v0.3.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.1.md) · [`v0.3.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.0.md) · [`v0.2.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.2.1.md) · [`v0.2.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.2.0.md) · [`v0.1.12`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.12.md) · [`v0.1.11`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.11.md) · [`v0.1.10`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.10.md) · [`v0.1.9`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.9.md) · [`v0.1.8`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.8.md) · [`v0.1.7`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.7.md) · [`v0.1.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.6.md) · [`v0.1.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.5.md) · [`v0.1.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.4.md) · [`v0.1.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.3.md) (covers the never-published `0.1.2`).
|
|
236
|
+
- Per-release notes — what changed, who is affected, what to do — are hand-written in Chinese and English and become the GitHub Release body: [`v0.4.7`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.7.md) · [`v0.4.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.6.md) · [`v0.4.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.5.md) · [`v0.4.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.4.md) · [`v0.4.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.3.md) · [`v0.4.2`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.2.md) · [`v0.4.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.1.md) · [`v0.4.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.0.md) · [`v0.3.2`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.2.md) · [`v0.3.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.1.md) · [`v0.3.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.0.md) · [`v0.2.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.2.1.md) · [`v0.2.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.2.0.md) · [`v0.1.12`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.12.md) · [`v0.1.11`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.11.md) · [`v0.1.10`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.10.md) · [`v0.1.9`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.9.md) · [`v0.1.8`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.8.md) · [`v0.1.7`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.7.md) · [`v0.1.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.6.md) · [`v0.1.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.5.md) · [`v0.1.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.4.md) · [`v0.1.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.3.md) (covers the never-published `0.1.2`).
|
|
234
237
|
|
|
235
238
|
## Configuration
|
|
236
239
|
|
|
@@ -239,9 +242,9 @@ Current release: plugin **`0.4.5`** is verified against DeepSeek Harness **`0.2.
|
|
|
239
242
|
| `cacheTtlMinutes` | `360` | 30–1,440 minutes; expires only for the next on-demand read, never a background timer |
|
|
240
243
|
| `sidebarEnabled` | `true` | Hides only this plugin's sidebar entry; the brand row falls back to DSH's own mark and wordmark |
|
|
241
244
|
|
|
242
|
-
|
|
245
|
+
The plugin shows version status and update notices by default after installation. Click the sidebar version chip for the running version, check result, upgrade guidance and cache-duration input. There is no separate **Settings → Version & updates** menu. Existing `sidebarEnabled` profile values remain supported; set it to `true` or remove the override if an older configuration hid the chip. Changing the duration does not issue a request; only a later normal read can refresh an expired cache, while **Check for updates** always performs an immediate manual refresh.
|
|
243
246
|
|
|
244
|
-
A preference is written only by your own selection in the panel
|
|
247
|
+
A cache preference is written only by your own selection in the panel. The plugin has no automatic write path — no effect, timer, or mount-time write — and `tests/client/entry.spec.ts` mounts the real client entry to keep it that way. On DSH 0.1.7 the two preferences above are the **volatile** fields of this plugin entry's `Config`, so they persist as that entry's `config` in the active profile's patch (`~/.dsh/profiles/<profile>/cordis.patch.yml`); edit or remove that block to reset a preference, and DSH reloads the profile on the next change. The remaining `Config` fields are deployment-only and never appear in the form: `cacheTtlHours` (default `6`), `timeoutMs` (default `15000`) and `autoCheckOnMount` (default `true`), all set in the same profile patch.
|
|
245
248
|
|
|
246
249
|
## Troubleshooting
|
|
247
250
|
|
package/README.zh.md
CHANGED
|
@@ -41,7 +41,7 @@
|
|
|
41
41
|
- **中性版本底框**:Badge 在明暗两套主题下都用灰色二级面(浅色 `#f1f3f5` / 深色 `#353638`)配主题常规文字色,所以暗色下是「深灰底 + 白字」,不再是会把橙色光晕吃掉的白框;只有状态读取失败时才会重绘成红色。
|
|
42
42
|
- **浅色 / 深色 / 跟随系统,自动适配**:插件渲染的每个颜色都是 DSH 语义令牌,Badge、圆点、光晕与面板都按 DSH 当前外观解析。DSH 设为浅色、深色或跟随系统,插件就跟着切换——插件侧没有自己的主题开关,也没有需要同步的媒体查询。hover 在两个方向上都是「抬起」:浅色下压深、深色下提亮(把主题文字色按比例混进底色实现)。
|
|
43
43
|
- **只有一条发布线、零配置**:一次 registry 请求读取 npm 的全部 dist-tags,只保留其中最新的版本——稳定版、RC、Alpha 一视同仁。没有需要关注的通道,也没有需要做的选择。
|
|
44
|
-
- **诚实的预发布比较**:运行版本与线上最新版本按 SemVer 排序,因此 `0.2.1-rc.
|
|
44
|
+
- **诚实的预发布比较**:运行版本与线上最新版本按 SemVer 排序,因此 `0.2.1-rc.3` 高于 `0.2.0-rc.2`,而 RC 仍然低于它自己的正式版。
|
|
45
45
|
- **兼容性标识**:本插件验证过的版本显示“已验证兼容”;没验证过的更新版本显示“尚未验证兼容”,不冒充安全升级,而且这条提示永远不会重绘芯片。
|
|
46
46
|
- **仅复制命令**:根据安装来源,为**找到的那个确切版本**生成命令,不用会移动的 dist-tag,也从不执行。
|
|
47
47
|
- **缓存但不轮询**:Host 挂载时检查一次,缓存可设为 30–1,440 分钟并合并并发请求;前端没有轮询,只有“检查更新”按钮绕过缓存。
|
|
@@ -53,7 +53,7 @@
|
|
|
53
53
|
|
|
54
54
|
- 带 Web profile 的 DeepSeek Harness
|
|
55
55
|
- Node.js 20 或更新版本
|
|
56
|
-
- 已验证的 DSH 版本:`0.2.1-rc.
|
|
56
|
+
- 已验证的 DSH 版本:`0.2.1-rc.3`(当前)、`0.2.1-rc.2`、`0.2.1-alpha.5`、`0.2.1-alpha.4`、`0.2.1-alpha.3`、`0.2.1-alpha.1`、`0.2.0-rc.2`、`0.2.0-rc.1`、`0.1.7-rc.2`、`0.1.7-rc.1` 与 `0.1.7-alpha.2`
|
|
57
57
|
|
|
58
58
|
已经安装 `dsh` 命令:
|
|
59
59
|
|
|
@@ -91,7 +91,7 @@ dsh plugin --profile web add "link:$(pwd)"
|
|
|
91
91
|
全局安装时可能生成:
|
|
92
92
|
|
|
93
93
|
```sh
|
|
94
|
-
npm install -g @deepseek-ai/dsh@0.2.1-rc.
|
|
94
|
+
npm install -g @deepseek-ai/dsh@0.2.1-rc.3
|
|
95
95
|
```
|
|
96
96
|
|
|
97
97
|
插件只显示一条与检测到的安装方式匹配、并写明所查到确切版本号的命令,不会运行它。
|
|
@@ -118,10 +118,10 @@ npm install -g @deepseek-ai/dsh@0.2.1-rc.2
|
|
|
118
118
|
插件按缓存周期向 npm registry 请求一次 `@deepseek-ai/dsh`,取出**所有 dist-tag 指向的最新版本**,再与正在运行的版本比较。`latest`、`next`、`alpha` 是 npm 自己的记账方式,不是需要用户做的选择:哪个 tag 上挂着更新的版本,就报哪个。
|
|
119
119
|
|
|
120
120
|
- 取 SemVer 最高者(含预发布):因此跑到稳定版前面的 `alpha` 会被提示,而不是被藏起来。
|
|
121
|
-
- 比较是精确的:`0.2.1-rc.
|
|
121
|
+
- 比较是精确的:`0.2.1-rc.3` 比 `0.2.0-rc.2` 新,两者都低于 `0.2.1`。
|
|
122
122
|
- 插件没听说过的 dist-tag 同样计入——读取的是 npm 返回的全部 tag,不是写死的三个。
|
|
123
123
|
- 只有本插件验证过的版本才标注“已验证兼容”;没验证过的更新版本会带上“尚未验证兼容”的提示(`notice`,永远不会重绘芯片)。
|
|
124
|
-
-
|
|
124
|
+
- 详情面板渲染唯一答案;升级命令写明所查到的确切版本。
|
|
125
125
|
|
|
126
126
|
这里不会安装任何东西。跟随某条通道——以及保存它的 `channel` 偏好——已在 `0.2.0` 移除。
|
|
127
127
|
|
|
@@ -146,7 +146,7 @@ dsh plugin --profile web exec dsh-update-status-service activate
|
|
|
146
146
|
|
|
147
147
|
`activate` 发现端口还被占着就停手,绝不去杀进程,所以你正在用的 DSH 不会被突然掐掉;激活之后它还会确认服务真的接管了——一启动就不停失败的服务会被当作失败报出来,而不是假装成功。这之后就交给**重启**按钮:它先列出正在跑的东西,有东西在跑时再问一次,然后才让 DSH 退出;服务把新的拉起来,页面自己回来。
|
|
148
148
|
|
|
149
|
-
同一个端口只允许一个启动者。如果别的工具自己拉起了 `dsh web`——另一个插件的重启助手、`nohup`
|
|
149
|
+
同一个端口只允许一个启动者。如果别的工具自己拉起了 `dsh web`——另一个插件的重启助手、`nohup` 脚本——那个进程会占着端口,而你的服务会一直启动失败。插件会直接问操作系统「这个服务真正拥有的是哪个进程」,所以这种情况下**重启**按钮会保持禁用,而不是承诺一个做不到的恢复;同时它会给出两条只复制的命令:一条找出谁占着端口,一条把服务交还回去。生成的服务在连续几次启动失败后也会停下来(不再无限重拉),并把原因写进自己的日志。更多细节见[用户服务监督说明](docs/service-supervision.md)。
|
|
150
150
|
|
|
151
151
|
| 平台 | 用户级拥有者 | 启动时机 | 接管后页面重启 | 说明 |
|
|
152
152
|
| --- | --- | --- | --- | --- |
|
|
@@ -160,24 +160,26 @@ dsh plugin --profile web exec dsh-update-status-service activate
|
|
|
160
160
|
|
|
161
161
|
## 局域网(非回环页面)访问
|
|
162
162
|
|
|
163
|
-
DSH
|
|
163
|
+
较早的 DSH 会把非回环页面的设置表单限制为仅内存状态。DSH `0.2.1-rc.3` 的表单快照不再提供该 `mode` 字段,官方按条目寻址的表单直接调用设置 Remote。不能仅根据页面来源判断当前的持久化或授权行为;写入是否获准由正在运行的 Host 设置策略决定。
|
|
164
164
|
|
|
165
165
|
从 `0.1.2` 起,本插件在局域网页面同样可用:
|
|
166
166
|
|
|
167
167
|
- **版本/更新状态**照常读取。早先的版本把整个功能压在 `connection.isLoopback === true` 上,于是经局域网转发(`dsh-bridge`、`dsh-lan-proxy` 等)打开的页面从不发送 `POST /api/dsh-update-status.get-status`、详情面板打不开,还会把本包声明的兼容版本当成"当前运行版本"显示。该判断已移除——Connection RPC 本身是已认证的,Host 路由也是本插件自己的路由。
|
|
168
168
|
- **偏好设置**(`sidebarEnabled`、`cacheTtlMinutes`)继续读写 Host 上共享的那一份 `dsh-update-status` 设置条目,走的是与官方设置表单相同的公开 Remote(`settings.describe` / `settings.mutate`)。写入仍受 revision 栅栏保护,被拒时明确提示冲突而不会静默覆盖。直连通道只在官方表单报 `unavailable` 时才打开,所以回环页面仍走官方路径,不会多发一次线上读取。
|
|
169
169
|
|
|
170
|
-
|
|
170
|
+
局域网转发必须保留 DSH 的已认证传输和 Host 授权策略。本插件不会修改转发配置或授予设置访问权;Host 拒绝访问时,应由部署维护者处理。
|
|
171
171
|
|
|
172
172
|
## 兼容性
|
|
173
173
|
|
|
174
|
-
当前发布:插件 **`0.4.
|
|
174
|
+
当前发布:插件 **`0.4.7`** 已针对 DeepSeek Harness **`0.2.1-rc.3`**(当前发布版)、**`0.2.1-rc.2`**、**`0.2.1-alpha.5`**、**`0.2.1-alpha.4`**、**`0.2.1-alpha.3`**、**`0.2.1-alpha.1`**、**`0.2.0-rc.2`**、**`0.2.0-rc.1`**、**`0.1.7-rc.2`**、**`0.1.7-rc.1`** 与 **`0.1.7-alpha.2`** 验证。
|
|
175
175
|
|
|
176
176
|
### 插件版本与 DeepSeek Harness 版本的对应关系
|
|
177
177
|
|
|
178
178
|
| 插件版本 | 已验证的 DeepSeek Harness | npm 发布状态 | 该版本是什么 |
|
|
179
179
|
| --- | --- | --- | --- |
|
|
180
|
-
| **`0.4.
|
|
180
|
+
| **`0.4.7`** | `0.2.1-rc.3`、`0.2.1-rc.2`、`0.2.1-alpha.5`、`0.2.1-alpha.4`、`0.2.1-alpha.3`、`0.2.1-alpha.1`、`0.2.0-rc.2`、`0.2.0-rc.1`、`0.1.7-rc.2`、`0.1.7-rc.1`、`0.1.7-alpha.2` | `latest` | 移除重复的设置菜单;安装后默认显示版本与更新提示,详情统一由侧栏版本芯片打开 |
|
|
181
|
+
| **`0.4.6`** | `0.2.1-rc.3`、`0.2.1-rc.2`、`0.2.1-alpha.5`、`0.2.1-alpha.4`、`0.2.1-alpha.3`、`0.2.1-alpha.1`、`0.2.0-rc.2`、`0.2.0-rc.1`、`0.1.7-rc.2`、`0.1.7-rc.1`、`0.1.7-alpha.2` | 已发布 | 验证 DSH `0.2.1-rc.3`;后台维护和启动中的终端也需重启确认,并恢复重启风暴的原因与恢复指引 |
|
|
182
|
+
| **`0.4.5`** | `0.2.1-rc.2`、`0.2.1-alpha.5`、`0.2.1-alpha.4`、`0.2.1-alpha.3`、`0.2.1-alpha.1`、`0.2.0-rc.2`、`0.2.0-rc.1`、`0.1.7-rc.2`、`0.1.7-rc.1`、`0.1.7-alpha.2` | 已发布 | 为 DSH `0.2.1-rc.2` 追加兼容声明;功能代码不变,中英文 README 一并核对,npm 包内容也与仓库比对过 |
|
|
181
183
|
| **`0.4.4`** | `0.2.1-alpha.5`、`0.2.1-alpha.4`、`0.2.1-alpha.3`、`0.2.1-alpha.1`、`0.2.0-rc.2`、`0.2.0-rc.1`、`0.1.7-rc.2`、`0.1.7-rc.1`、`0.1.7-alpha.2` | 已发布 | 为 DSH `0.2.1-alpha.5` 追加兼容声明;功能代码不变,中英文 README 的版本号一并核对过 |
|
|
182
184
|
| **`0.4.3`** | `0.2.1-alpha.4`、`0.2.1-alpha.3`、`0.2.1-alpha.1`、`0.2.0-rc.2`、`0.2.0-rc.1`、`0.1.7-rc.2`、`0.1.7-rc.1`、`0.1.7-alpha.2` | 已发布 | 为 DSH `0.2.1-alpha.4` 追加兼容声明;功能代码不变,面板会将当前运行版显示为已验证兼容 |
|
|
183
185
|
| **`0.4.2`** | `0.2.1-alpha.3`、`0.2.1-alpha.1`、`0.2.0-rc.2`、`0.2.0-rc.1`、`0.1.7-rc.2`、`0.1.7-rc.1`、`0.1.7-alpha.2` | 已发布 | 为 DSH `0.2.1-alpha.3` 追加兼容声明;功能代码不变,面板会将当前运行版显示为已验证兼容 |
|
|
@@ -208,6 +210,7 @@ DSH 对来源不是 loopback(`localhost` / `127.0.0.1`)的页面会关闭 Ho
|
|
|
208
210
|
- 需要精确对应时显式指定版本:
|
|
209
211
|
|
|
210
212
|
```sh
|
|
213
|
+
dsh plugin --profile web add dsh-update-status@0.4.7 # DSH 0.2.1-rc.3、0.2.1-rc.2、0.2.1-alpha.5、0.2.1-alpha.4、0.2.1-alpha.3、0.2.1-alpha.1、0.2.0-rc.2、0.2.0-rc.1、0.1.7-rc.2、0.1.7-rc.1 或 0.1.7-alpha.2
|
|
211
214
|
dsh plugin --profile web add dsh-update-status@0.4.5 # DSH 0.2.1-rc.2、0.2.1-alpha.5、0.2.1-alpha.4、0.2.1-alpha.3、0.2.1-alpha.1、0.2.0-rc.2、0.2.0-rc.1、0.1.7-rc.2、0.1.7-rc.1 或 0.1.7-alpha.2
|
|
212
215
|
dsh plugin --profile web add dsh-update-status@0.4.4 # DSH 0.2.1-alpha.5、0.2.1-alpha.4、0.2.1-alpha.3、0.2.1-alpha.1、0.2.0-rc.2、0.2.0-rc.1、0.1.7-rc.2、0.1.7-rc.1 或 0.1.7-alpha.2
|
|
213
216
|
dsh plugin --profile web add dsh-update-status@0.4.3 # DSH 0.2.1-alpha.4、0.2.1-alpha.3、0.2.1-alpha.1、0.2.0-rc.2、0.2.0-rc.1、0.1.7-rc.2、0.1.7-rc.1 或 0.1.7-alpha.2
|
|
@@ -227,9 +230,9 @@ DSH 对来源不是 loopback(`localhost` / `127.0.0.1`)的页面会关闭 Ho
|
|
|
227
230
|
```
|
|
228
231
|
|
|
229
232
|
- 有两处声明让已验证的版本线能正常加载,并由测试守住:
|
|
230
|
-
- `dsh.engines.dsh` 与 `peerDependencies['@deepseek-ai/dsh-settings']` 都声明 `>=0.1.7-alpha.2 <0.3.0
|
|
233
|
+
- `dsh.engines.dsh` 与 `peerDependencies['@deepseek-ai/dsh-settings']` 都声明 `>=0.1.7-alpha.2 <0.3.0`,十一个已验证版本都在范围内。下界特意写成这个 alpha:按 node-semver 默认的预发布规则,`>=0.1.6-0 <0.2.0` 这样的范围**并不接纳** `0.1.7-alpha.2`。上界在 `0.1.11` 从 `<0.2.0` 放宽到 `<0.3.0` 是同一件事的镜像:DSH 会在 profile 加载时拒绝不兼容的 bundle,而裸的 `<0.2.0` 恰好排除 `0.2.0` 正式版——DSH `0.2.0` 发布当天插件就会被静默丢弃。DSH 判定时使用 `includePrerelease: true`,所以 `0.2.0-rc.2` 本来就在这个范围内,`0.1.12` 无需再动范围;反过来说,把范围写成 `... || 0.2.0-rc.1 || >=0.2.0 <0.3.0` 这类枚举的插件会因为 `>=0.2.0` 不接纳 `0.2.0` 预发布而被 rc.2 拒载。
|
|
231
234
|
- `@deepseek-ai/schemastery` 是 **peer**,不是普通依赖:DSH 0.1.7 只从运行安装解析 link 插件的 peer 依赖,否则 `link:` 安装会连 Host 半边都 import 失败。
|
|
232
|
-
- 每个版本的中英文详细说明(改了什么、影响谁、需要做什么)手写后直接作为 GitHub Release 正文:[`v0.4.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.5.md) · [`v0.4.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.4.md) · [`v0.4.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.3.md) · [`v0.4.2`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.2.md) · [`v0.4.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.1.md) · [`v0.4.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.0.md) · [`v0.3.2`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.2.md) · [`v0.3.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.1.md) · [`v0.3.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.0.md) · [`v0.2.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.2.1.md) · [`v0.2.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.2.0.md) · [`v0.1.12`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.12.md) · [`v0.1.11`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.11.md) · [`v0.1.10`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.10.md) · [`v0.1.9`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.9.md) · [`v0.1.8`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.8.md) · [`v0.1.7`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.7.md) · [`v0.1.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.6.md) · [`v0.1.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.5.md) · [`v0.1.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.4.md) · [`v0.1.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.3.md)(含从未发布的 `0.1.2`)。
|
|
235
|
+
- 每个版本的中英文详细说明(改了什么、影响谁、需要做什么)手写后直接作为 GitHub Release 正文:[`v0.4.7`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.7.md) · [`v0.4.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.6.md) · [`v0.4.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.5.md) · [`v0.4.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.4.md) · [`v0.4.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.3.md) · [`v0.4.2`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.2.md) · [`v0.4.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.1.md) · [`v0.4.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.0.md) · [`v0.3.2`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.2.md) · [`v0.3.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.1.md) · [`v0.3.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.3.0.md) · [`v0.2.1`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.2.1.md) · [`v0.2.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.2.0.md) · [`v0.1.12`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.12.md) · [`v0.1.11`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.11.md) · [`v0.1.10`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.10.md) · [`v0.1.9`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.9.md) · [`v0.1.8`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.8.md) · [`v0.1.7`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.7.md) · [`v0.1.6`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.6.md) · [`v0.1.5`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.5.md) · [`v0.1.4`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.4.md) · [`v0.1.3`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.1.3.md)(含从未发布的 `0.1.2`)。
|
|
233
236
|
|
|
234
237
|
## 配置
|
|
235
238
|
|
|
@@ -238,9 +241,9 @@ DSH 对来源不是 loopback(`localhost` / `127.0.0.1`)的页面会关闭 Ho
|
|
|
238
241
|
| `cacheTtlMinutes` | `360` | 30–1,440 分钟;仅在下一次按需读取时判断是否到期,绝不启动后台定时器 |
|
|
239
242
|
| `sidebarEnabled` | `true` | 只隐藏本插件自己的侧栏入口;隐藏期间品牌行恢复为 DSH 官方鱼标与字标 |
|
|
240
243
|
|
|
241
|
-
|
|
244
|
+
插件安装后默认显示版本状态与更新提示。点击侧栏版本芯片即可查看当前版本、检查结论、升级说明并调整缓存时长,不再提供单独的**设置 → 版本与更新**菜单。已有 profile 中的 `sidebarEnabled` 配置仍然兼容;若旧配置隐藏了芯片,将其设为 `true` 或删除该覆盖值即可恢复默认显示。修改缓存时长不会请求网络;只在之后普通读取且缓存已到期时更新,“检查更新”始终是立即手动检查。
|
|
242
245
|
|
|
243
|
-
|
|
246
|
+
缓存偏好只会在你于面板中主动选择时写入。插件没有任何自动写入路径——没有 effect、定时器,也不在挂载时写入,并由 `tests/client/entry.spec.ts` 挂载真实客户端入口长期守住这一点。在 DSH 0.1.7 上,上面两个偏好就是本插件条目 `Config` 的 **volatile** 字段,因此以该条目的 `config` 落在当前 profile 的 patch 里(`~/.dsh/profiles/<profile>/cordis.patch.yml`);要重置某个偏好,直接修改或删除该段即可,DSH 会在下次变更时重新加载 profile。`Config` 的其余字段只用于部署、不会出现在表单中:`cacheTtlHours`(默认 `6`)、`timeoutMs`(默认 `15000`)与 `autoCheckOnMount`(默认 `true`),同样写在同一份 profile patch 中。
|
|
244
247
|
|
|
245
248
|
## 故障排查
|
|
246
249
|
|
|
@@ -268,7 +271,7 @@ Host 会缓存一次 registry 响应,默认 360 分钟,且只有普通读取
|
|
|
268
271
|
插件会报告失败,并仍然显示本地检测到的运行版本。registry 访问只允许 HTTPS 的 `registry.npmjs.org`;代理或离线环境会给出这条警告,而不是编造一个版本号。
|
|
269
272
|
|
|
270
273
|
**升级之后插件整个消失了,宿主日志里是 `volatile is not a function`。**
|
|
271
|
-
`0.1.5` 及更早版本把 `@deepseek-ai/schemastery` 声明为普通依赖;从 `0.1.6` 起它是**由 DSH 提供的 peer**,而 DSH 给它加的 `volatile()`
|
|
274
|
+
`0.1.5` 及更早版本把 `@deepseek-ai/schemastery` 声明为普通依赖;从 `0.1.6` 起它是**由 DSH 提供的 peer**,而 DSH 给它加的 `volatile()` 正是把两个偏好变成这个条目设置表单的机制。如果该包的一份旧副本被留在插件自己的安装目录里(用本地目录安装时被一起拷进来的 dev `node_modules`,pnpm 永远不会清理),Node 就会解析到那份旧副本,缺失的方法在宿主半 import 阶段直接抛错,插件在来得及报告任何信息之前就消失了。新版本改为显式解析平台那份,两种情况都能加载;只找得到旧副本时,面板会给出 `stale-schemastery` 提示并指出该删除哪个目录。删除残留目录后重启 DSH:
|
|
272
275
|
|
|
273
276
|
```sh
|
|
274
277
|
rm -rf ~/.dsh/profiles/<profile>/node_modules/dsh-update-status/node_modules
|
|
@@ -139,7 +139,7 @@ Supervision only means something while the service is the only thing starting DS
|
|
|
139
139
|
- a restart storm (recent boot stamps plus DSH's own `startup-*.log` diagnostics, four within three minutes) is reported in the panel as its own reason;
|
|
140
140
|
- every generated definition carries a failure ceiling, and the wrapper/log line says which limit was reached.
|
|
141
141
|
|
|
142
|
-
Recovery is always the same: stop the extra instance, confirm the port is free (`lsof -nP -iTCP:3080 -sTCP:LISTEN`), then restart the service with the platform command above. The plugin never kills that other process for you — but it does hand you both commands: while a restart is refused, the panel
|
|
142
|
+
Recovery is always the same: stop the extra instance, confirm the port is free (`lsof -nP -iTCP:3080 -sTCP:LISTEN`), then restart the service with the platform command above. The plugin never kills that other process for you — but it does hand you both commands: while a restart is refused, the detail panel shows the refusal reason followed by the two copy-only lines, taken from the installer's own receipt (the port) and the service plan (`recoverCommand`, which includes `systemctl --user reset-failed` on Linux because the unit's own start limit is what stopped the storm). With no receipt, the panel points at this document instead.
|
|
143
143
|
|
|
144
144
|
## Restart behavior and limits
|
|
145
145
|
|
package/lib/client.js
CHANGED
|
@@ -317,26 +317,6 @@ window.__ModuleLoader__.load({
|
|
|
317
317
|
"guidance.unknownInstall": {
|
|
318
318
|
zh: "升级前请先确认 DSH 的安装方式;本插件无法代为执行升级。",
|
|
319
319
|
en: "Confirm how DSH was installed before upgrading; this plugin cannot perform the upgrade for you."
|
|
320
|
-
},
|
|
321
|
-
"settings.title": {
|
|
322
|
-
zh: "版本与更新",
|
|
323
|
-
en: "Version & updates"
|
|
324
|
-
},
|
|
325
|
-
"settings.sidebar": {
|
|
326
|
-
zh: "在侧栏显示版本状态入口",
|
|
327
|
-
en: "Show the version-status entry in the sidebar"
|
|
328
|
-
},
|
|
329
|
-
"settings.sidebarHint": {
|
|
330
|
-
zh: "关闭后不再渲染品牌行里的版本芯片,品牌行恢复为 DSH 官方内容。不会执行或安排升级。",
|
|
331
|
-
en: "When off, the version chip in the brand row is not rendered and the brand row falls back to DSH’s own content. No update is run or scheduled."
|
|
332
|
-
},
|
|
333
|
-
"settings.readonly": {
|
|
334
|
-
zh: "此连接的设置为只读;显示状态不受影响。",
|
|
335
|
-
en: "Settings are read-only on this connection; status display is unchanged."
|
|
336
|
-
},
|
|
337
|
-
"settings.serviceStarted": {
|
|
338
|
-
zh: "服务启动时间",
|
|
339
|
-
en: "Service started"
|
|
340
320
|
}
|
|
341
321
|
};
|
|
342
322
|
function languageOf() {
|
|
@@ -652,8 +632,7 @@ window.__ModuleLoader__.load({
|
|
|
652
632
|
} catch {}
|
|
653
633
|
}
|
|
654
634
|
/**
|
|
655
|
-
*
|
|
656
|
-
* settings section so both surfaces can never disagree about what to run.
|
|
635
|
+
* Copy-only commands for upgrade guidance and restart recovery.
|
|
657
636
|
*/
|
|
658
637
|
function CommandBlock({ command, disabled = false, label = t("panel.command"), note = t("panel.commandNote") }) {
|
|
659
638
|
const commandRef = React.useRef(null);
|
|
@@ -889,125 +868,6 @@ window.__ModuleLoader__.load({
|
|
|
889
868
|
})]
|
|
890
869
|
});
|
|
891
870
|
}
|
|
892
|
-
/** Separate setting page: disables only this plugin's own rendering. */
|
|
893
|
-
function UpdateSettings({ ui }) {
|
|
894
|
-
const preferences = useObservable(ui.preferences);
|
|
895
|
-
const snapshot = useObservable(ui.status);
|
|
896
|
-
const startedAt = useObservable(ui.restart).status?.startedAt ?? null;
|
|
897
|
-
const status = snapshot.status;
|
|
898
|
-
const summary = statusSummary(status, snapshot.loading, snapshot.error);
|
|
899
|
-
const hasUpdate = status?.hasUpdate === true && status.latestVersion !== null;
|
|
900
|
-
const command = status === null || !hasUpdate ? "" : localizedUpgradeGuidance(status);
|
|
901
|
-
return /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("section", {
|
|
902
|
-
className: "dus-settings",
|
|
903
|
-
children: [
|
|
904
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)("h2", {
|
|
905
|
-
className: "dus-settings-heading",
|
|
906
|
-
children: t("settings.title")
|
|
907
|
-
}),
|
|
908
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
|
|
909
|
-
className: "dus-settings-card",
|
|
910
|
-
children: [
|
|
911
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("label", {
|
|
912
|
-
className: "dus-settings-toggle",
|
|
913
|
-
children: [/* @__PURE__ */ (0, react_jsx_runtime.jsx)("input", {
|
|
914
|
-
type: "checkbox",
|
|
915
|
-
checked: preferences.sidebarEnabled,
|
|
916
|
-
disabled: !preferences.writable,
|
|
917
|
-
onChange: (event) => {
|
|
918
|
-
ui.preferences.setSidebarEnabled(event.currentTarget.checked);
|
|
919
|
-
}
|
|
920
|
-
}), /* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", { children: t("settings.sidebar") })]
|
|
921
|
-
}),
|
|
922
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
|
|
923
|
-
className: "dus-settings-hint",
|
|
924
|
-
children: t("settings.sidebarHint")
|
|
925
|
-
}),
|
|
926
|
-
!preferences.writable && /* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
|
|
927
|
-
className: "dus-settings-hint",
|
|
928
|
-
children: t("settings.readonly")
|
|
929
|
-
})
|
|
930
|
-
]
|
|
931
|
-
}),
|
|
932
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
|
|
933
|
-
className: "dus-settings-card",
|
|
934
|
-
children: [
|
|
935
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
|
|
936
|
-
className: "dus-settings-pair",
|
|
937
|
-
children: [/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("p", {
|
|
938
|
-
className: "dus-settings-hint",
|
|
939
|
-
children: [
|
|
940
|
-
t("panel.current"),
|
|
941
|
-
": ",
|
|
942
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)("code", { children: status?.currentVersion ?? "…" })
|
|
943
|
-
]
|
|
944
|
-
}), startedAt !== null && /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("p", {
|
|
945
|
-
className: "dus-settings-hint",
|
|
946
|
-
children: [
|
|
947
|
-
t("settings.serviceStarted"),
|
|
948
|
-
": ",
|
|
949
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)("code", { children: timeText(startedAt) })
|
|
950
|
-
]
|
|
951
|
-
})]
|
|
952
|
-
}),
|
|
953
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
|
|
954
|
-
className: "dus-state",
|
|
955
|
-
"data-kind": summary.kind,
|
|
956
|
-
children: summary.text
|
|
957
|
-
}),
|
|
958
|
-
hasUpdate && /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("p", {
|
|
959
|
-
className: "dus-settings-hint",
|
|
960
|
-
children: [
|
|
961
|
-
t("panel.newer"),
|
|
962
|
-
": ",
|
|
963
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)("code", { children: status.latestVersion }),
|
|
964
|
-
" · ",
|
|
965
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", {
|
|
966
|
-
className: "dus-compat",
|
|
967
|
-
"data-compatibility": status.compatibility,
|
|
968
|
-
children: compatibilityLabel(status.compatibility)
|
|
969
|
-
})
|
|
970
|
-
]
|
|
971
|
-
}),
|
|
972
|
-
snapshot.error !== null && /* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
|
|
973
|
-
role: "alert",
|
|
974
|
-
children: snapshot.error
|
|
975
|
-
}),
|
|
976
|
-
hasUpdate && /* @__PURE__ */ (0, react_jsx_runtime.jsx)(CommandBlock, {
|
|
977
|
-
command,
|
|
978
|
-
disabled: snapshot.loading
|
|
979
|
-
}),
|
|
980
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
|
|
981
|
-
className: "dus-actions",
|
|
982
|
-
children: [
|
|
983
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)("button", {
|
|
984
|
-
className: "dus-action",
|
|
985
|
-
type: "button",
|
|
986
|
-
disabled: snapshot.loading,
|
|
987
|
-
onClick: () => {
|
|
988
|
-
ui.status.refresh(preferences.cacheTtlMinutes);
|
|
989
|
-
},
|
|
990
|
-
children: snapshot.loading ? t("panel.checking") : t("panel.check")
|
|
991
|
-
}),
|
|
992
|
-
status !== null && /* @__PURE__ */ (0, react_jsx_runtime.jsx)("a", {
|
|
993
|
-
className: "dus-action",
|
|
994
|
-
href: status.changelogUrl,
|
|
995
|
-
target: "_blank",
|
|
996
|
-
rel: "noreferrer",
|
|
997
|
-
children: t("panel.releaseNotes")
|
|
998
|
-
}),
|
|
999
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)(RestartControl, { restart: ui.restart })
|
|
1000
|
-
]
|
|
1001
|
-
}),
|
|
1002
|
-
/* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
|
|
1003
|
-
className: "dus-settings-hint",
|
|
1004
|
-
children: t("panel.readOnly")
|
|
1005
|
-
})
|
|
1006
|
-
]
|
|
1007
|
-
})
|
|
1008
|
-
]
|
|
1009
|
-
});
|
|
1010
|
-
}
|
|
1011
871
|
//#endregion
|
|
1012
872
|
//#region src/client/contract.ts
|
|
1013
873
|
function errorMessage(error) {
|
|
@@ -1020,7 +880,7 @@ window.__ModuleLoader__.load({
|
|
|
1020
880
|
const record = objectOf(value);
|
|
1021
881
|
if (record === void 0 || typeof record.instanceId !== "string" || record.instanceId === "" || typeof record.available !== "boolean") return void 0;
|
|
1022
882
|
const supervisor = record.supervisor === null ? null : record.supervisor === "launchd" || record.supervisor === "systemd" || record.supervisor === "task-scheduler" || record.supervisor === "unknown" ? record.supervisor : void 0;
|
|
1023
|
-
const unavailableReason = record.unavailableReason === null ? null : record.unavailableReason === "not-supervised" || record.unavailableReason === "desktop" || record.unavailableReason === "supervisor-mismatch" || record.unavailableReason === "activity-unavailable" || record.unavailableReason === "timer-unavailable" || record.unavailableReason === "stale-instance" ? record.unavailableReason : void 0;
|
|
883
|
+
const unavailableReason = record.unavailableReason === null ? null : record.unavailableReason === "not-supervised" || record.unavailableReason === "desktop" || record.unavailableReason === "supervisor-mismatch" || record.unavailableReason === "supervisor-thrashing" || record.unavailableReason === "activity-unavailable" || record.unavailableReason === "timer-unavailable" || record.unavailableReason === "stale-instance" ? record.unavailableReason : void 0;
|
|
1024
884
|
if (supervisor === void 0 || unavailableReason === void 0) return void 0;
|
|
1025
885
|
if (record.startedAt !== void 0 && (typeof record.startedAt !== "string" || record.startedAt === "")) return void 0;
|
|
1026
886
|
const recovery = record.recovery === void 0 ? void 0 : objectOf(record.recovery);
|
|
@@ -2138,22 +1998,6 @@ window.__ModuleLoader__.load({
|
|
|
2138
1998
|
.dus-command:focus{outline:2px solid var(--dsw-alias-state-business-primary);outline-offset:2px}
|
|
2139
1999
|
.dus-note{color:var(--dsw-alias-label-secondary);font-size:11px;line-height:1.45;margin:8px 0 0}
|
|
2140
2000
|
.dus-copy-message{color:var(--dsw-alias-state-business-primary);font-size:11px;margin:7px 0 0}
|
|
2141
|
-
.dus-settings{display:grid;gap:14px;max-width:640px;padding:4px 0}
|
|
2142
|
-
.dus-settings-heading{font-size:16px;font-weight:650;margin:0}
|
|
2143
|
-
.dus-settings-card{border:1px solid var(--dsw-alias-border-l2);border-radius:10px;padding:12px}
|
|
2144
|
-
.dus-settings-toggle{align-items:flex-start;cursor:pointer;display:flex;gap:10px;font-size:13px;line-height:1.4}
|
|
2145
|
-
.dus-settings-toggle input{accent-color:var(--dsw-alias-state-business-primary);height:18px;margin:0;min-height:18px;min-width:18px;width:18px}
|
|
2146
|
-
.dus-settings-hint{color:var(--dsw-alias-label-secondary);font-size:12px;line-height:1.45;margin:8px 0 0}
|
|
2147
|
-
/* Running version and service start time share one row: version left, start time
|
|
2148
|
-
flush right. Each line asks for a 200px basis, so the row wraps into two stacked
|
|
2149
|
-
lines on a phone-width card instead of squeezing either value — the break is
|
|
2150
|
-
driven by available width, which keeps one declaration correct at every size and
|
|
2151
|
-
needs no width query. min(200px,100%) keeps a very narrow card from overflowing.
|
|
2152
|
-
The 5px bottom margin is the breathing room the status block below used to do
|
|
2153
|
-
without: the hints carry margin:8px 0 0, so the row's own box ends at the text and
|
|
2154
|
-
the green state block sat flush against it. */
|
|
2155
|
-
.dus-settings-pair{align-items:baseline;display:flex;flex-wrap:wrap;gap:0 12px;justify-content:space-between;margin:0 0 5px}
|
|
2156
|
-
.dus-settings-pair>.dus-settings-hint{flex:0 1 auto;min-width:min(200px,100%);overflow-wrap:anywhere}
|
|
2157
2001
|
.dus-compat{color:var(--dsw-alias-label-secondary)}
|
|
2158
2002
|
.dus-compat[data-compatibility=verified]{color:var(--dsw-alias-state-success-primary)}
|
|
2159
2003
|
.dus-compat[data-compatibility=incompatible]{color:var(--dsw-alias-state-error-primary)}
|
|
@@ -2304,12 +2148,6 @@ window.__ModuleLoader__.load({
|
|
|
2304
2148
|
id: "dsh-update-status",
|
|
2305
2149
|
order: 40
|
|
2306
2150
|
}, () => UpdatePanel({ ui })));
|
|
2307
|
-
ctx.slots.inject("settings.section", () => ctx.slots.register({
|
|
2308
|
-
name: "settings.section",
|
|
2309
|
-
id: "dsh-update-status",
|
|
2310
|
-
order: 80,
|
|
2311
|
-
label: () => t("settings.title")
|
|
2312
|
-
}, () => UpdateSettings({ ui })));
|
|
2313
2151
|
}
|
|
2314
2152
|
module.exports = {
|
|
2315
2153
|
name: PLUGIN_ID,
|