dsh-update-status 0.4.8 → 0.5.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 CHANGED
@@ -2,6 +2,19 @@
2
2
 
3
3
  All notable changes to this project are documented here.
4
4
 
5
+ ## 0.5.0 — 2026-10-28
6
+
7
+ Loadability is decided by DSH alone: `dsh.engines.dsh` and the `@deepseek-ai/dsh-settings` peer both declare `>=0.1.7-alpha.2 <0.3.0`, and this release changes neither. It publishes no per-release verification. Release notes: [`docs/releases/v0.5.0.md`](docs/releases/v0.5.0.md).
8
+
9
+ - **One card per upgradable version.** The panel lists every published version strictly newer than the running one, newest first, and gives each card its own copy-only command for that exact version. Nothing newer means no cards at all: the panel says the running release is the newest and there is no command block left over.
10
+ - **The newest version is the one that stands out.** The highest version gets an amber border and a **Newest** pill; every other card stays neutral. There is no sort control — the order is version order — and there is still no auto-install and no auto-restart.
11
+ - **The compatibility mechanism is removed.** `VERIFIED_DSH_VERSIONS` and `package.json`'s `dsh.compatibility.dshReleases` are gone, together with the verified/unverified labels, the `version-unverified` notice and the per-DSH-release patch releases that only moved a label. The panel no longer says that a DeepSeek Harness release was tested with this build.
12
+ - **Why:** the plugin's only job is to tell an operator that a newer release exists and how to upgrade. Keeping a compatibility ledger was out of scope, and it had produced six releases in 13 days whose headline was a declaration (`0.4.2`, `0.4.3`, `0.4.4`, `0.4.5`, `0.4.6`, `0.4.8`).
13
+ - **Breaking change in the panel's information model, not in configuration.** A card no longer carries a compatibility verdict, so a reader who used that label to decide loses the signal. Nothing else moves: no setting, stored profile value, service receipt or command changes, and upgrading needs no migration.
14
+ - **Engine and peer ranges are unchanged.** `>=0.1.7-alpha.2 <0.3.0` on both declarations is what decides whether DSH loads the plugin, so a newer DSH release inside that range needs no plugin release to be usable.
15
+ - **Both READMEs were rewritten rather than patched.** The feature list, install requirements, usage steps, dot table, update-check section, the renamed loadability section, the version matrix (the verified-DSH column is dropped), the install-command list and the release-note links all describe the card layout; every verified-release count and "current release" claim is gone.
16
+ - **Verification:** the automated test suite and a local visual check of the card layout. No full manual acceptance pass was run for this build.
17
+
5
18
  ## 0.4.8 — 2026-10-27
6
19
 
7
20
  Verified DeepSeek Harness: `0.2.1-rc.4`; retains all eleven previously verified releases. Engine and peer ranges remain unchanged. Release notes: [`docs/releases/v0.4.8.md`](docs/releases/v0.4.8.md).
package/README.md CHANGED
@@ -17,7 +17,7 @@
17
17
  <a href="#update-check">Update check</a> ·
18
18
  <a href="#supervised-restart">Supervised restart</a> ·
19
19
  <a href="#lan--non-loopback-pages">LAN pages</a> ·
20
- <a href="#compatibility">Compatibility</a> ·
20
+ <a href="#loadability-and-update-notices">Loadability</a> ·
21
21
  <a href="#configuration">Configuration</a> ·
22
22
  <a href="#troubleshooting">Troubleshooting</a> ·
23
23
  <a href="#security-boundary">Security</a> ·
@@ -25,9 +25,9 @@
25
25
  <a href="docs/RELEASING.md">Release guide</a>
26
26
  </p>
27
27
 
28
- > DSH Update Status is a community plugin for DeepSeek Harness. It does not modify DSH core, install or upgrade DSH, roll back DSH packages, download releases, or replace DSH files. It can request a **safe restart only after you explicitly install a verified user-level service** to supervise the current DSH Web process.
28
+ > DSH Update Status is a community plugin for DeepSeek Harness. It does not modify DSH core, install or upgrade DSH, roll back DSH packages, download releases, or replace DSH files. It never installs an update and never restarts DSH on its own. It can request a **safe restart only after you explicitly install a user-level service** to supervise the current DSH Web process.
29
29
 
30
- It shadows only the expanded sidebar brand name with `DeepSeek` plus a compact version chip that fits the 24px brand row, leaving the official fish mark untouched. A green dot next to the version means the running release is the newest one npm publishes; a breathing amber dot means a newer release exists — stable, release candidate or alpha. Tap the chip for the running version, the newer release, whether this plugin was verified against it, a copy-only upgrade command pinned to that exact version, and the guarded **Restart** control that appears once you have installed user-level supervision.
30
+ It shadows only the expanded sidebar brand name with `DeepSeek` plus a compact version chip that fits the 24px brand row, leaving the official fish mark untouched. A green dot next to the version means nothing newer is published; a breathing amber dot means at least one newer release exists — stable, release candidate or alpha. Tap the chip for the running version, one card per newer version, each with its own copy-only upgrade command, and the guarded **Restart** control that appears once you have installed user-level supervision.
31
31
 
32
32
  <p align="center">
33
33
  <img src="./assets/update-panel.png" width="400" alt="DSH Update Status panel: cache duration, the running 0.2.1-alpha.1 reported up to date with its last-checked time, the actions Check for updates, Release notes and Restart, and a note that restart is available only under a user-installed service">
@@ -40,10 +40,12 @@ It shadows only the expanded sidebar brand name with `DeepSeek` plus a compact v
40
40
  - **Three dot states, one glance** — with nothing to do the dot beside the version is a plain **green circle** (the theme's success colour, not the text colour, so a dark shell no longer paints a dot that reads as "off"). While a check is running it is the neutral grey pulse; a pending update is the amber halo. Only the update state animates or glows, and only a failed status read repaints the chip, in red.
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
- - **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.4` outranks `0.2.0-rc.2` and a release candidate still sorts below its own stable release.
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
- - **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.
43
+ - **One card per upgradable version** — every published version strictly newer than the running one gets its own card, newest first, and each card carries that version's own copy-only command. When nothing is newer there are no cards at all and the panel says the running release is the newest.
44
+ - **The newest card is the one that stands out** — the highest version gets an amber border and a **Newest** pill; every other card stays neutral. There is no sort control: the order is the version order, and only the top card is emphasized.
45
+ - **One release line, zero configuration** — reads npm's dist-tags in one registry request and keeps every version that is newer than the running one, stable, release candidate or alpha alike. There is no channel to follow and no choice to make.
46
+ - **An honest prerelease comparison** — the running version and each candidate are ordered with SemVer, so `0.2.1-rc.4` outranks `0.2.0-rc.2` and a release candidate still sorts below its own stable release.
47
+ - **Copy-only guidance, per version** — each card's command names that card's exact version, never a dist-tag that can move, and is never executed by the plugin.
48
+ - **No compatibility bookkeeping** — the panel no longer claims that a DeepSeek Harness release was tested with this build. What decides whether the plugin loads is DSH's own gate: the declared engine range and the `@deepseek-ai/dsh-settings` peer range.
47
49
  - **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.
48
50
  - **Mobile-safe panel** — uses a modal browser top layer so the scrollable, safe-area-aware bottom sheet stays above the DSH drawer.
49
51
  - **Supervised safe restart** — after a one-time service setup, the panel can restart DSH for you: it warns about the work it would interrupt, and refuses outright when DSH was started by hand or by the desktop app.
@@ -53,8 +55,8 @@ It shadows only the expanded sidebar brand name with `DeepSeek` plus a compact v
53
55
  Requirements:
54
56
 
55
57
  - DeepSeek Harness with the Web profile
58
+ - DeepSeek Harness `>=0.1.7-alpha.2 <0.3.0` — the range this plugin declares in `dsh.engines.dsh`, with the same bounds on the `@deepseek-ai/dsh-settings` peer. DSH refuses a bundle outside that range at profile load. There is no per-release tested list to consult: inside the range, the plugin is not waiting for a release to be "approved".
56
59
  - Node.js 20 or newer
57
- - Verified DSH releases: `0.2.1-rc.4` (newest published), `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` and `0.1.7-alpha.2`
58
60
 
59
61
  With an installed `dsh` command:
60
62
 
@@ -84,18 +86,18 @@ dsh plugin --profile web add "link:$(pwd)"
84
86
 
85
87
  1. Open the DSH sidebar drawer. The official fish remains in place; the name row shows `DeepSeek` plus the current version badge.
86
88
  2. Tap the badge. The update panel opens without triggering the parent New Session action.
87
- 3. Read the running version. When it is the newest release npm publishes, the panel says so and offers nothing to run.
88
- 4. When a newer release exists — stable, release candidate or alpha — the panel names it, its publish date, and whether this plugin was verified against it.
89
- 5. Copy the generated command, which is pinned to that exact version, and run it yourself in a terminal on the computer hosting DSH.
89
+ 3. Read the running version. When nothing newer is published, the panel says the running release is the newest and there is no card to act on.
90
+ 4. Otherwise every newer published version has its own card, newest first. A card shows the version, the dist-tag that carries it when npm reports one, its release line and publish date.
91
+ 5. Copy the command from the card you want — each one is pinned to that card's exact version — and run it yourself in a terminal on the computer hosting DSH.
90
92
  6. After the package-manager command completes, use the panel's **Restart** control only if you have completed [supervised restart](#supervised-restart); otherwise restart DSH yourself.
91
93
 
92
- Example commands generated for a global install:
94
+ Example command on a card for a global install:
93
95
 
94
96
  ```sh
95
97
  npm install -g @deepseek-ai/dsh@0.2.1-rc.4
96
98
  ```
97
99
 
98
- The plugin displays one command that matches the detected installation kind and names the exact release it found. It does not run it.
100
+ Each card shows one command that matches the detected installation kind and names that card's exact release. The plugin does not run it. When the installation kind cannot take a package-manager command — a source checkout, for example — the panel shows that guidance once instead of a copy button on every card, rather than inventing a command.
99
101
 
100
102
  ### What the dot means
101
103
 
@@ -103,10 +105,10 @@ The dot beside the version carries the whole status, and only the update state a
103
105
 
104
106
  | Dot | State | Meaning |
105
107
  | --- | --- | --- |
106
- | green circle | up to date | The running release is the newest one npm publishes. The chip keeps its normal fill. |
108
+ | green circle | up to date | Nothing newer is published. The chip keeps its normal fill. |
107
109
  | grey pulse | checking | A status read is in flight (first mount or **Check for updates**). |
108
- | amber dot with a halo | update | A newer release exists. Copy the command, run it yourself, restart DSH. |
109
- | chip turns red | failed read | The plugin could not determine the state: the registry read failed or the two versions are not SemVer-comparable. An *unverified* newer release is not this case — it is an advisory shown only in the panel. |
110
+ | amber dot with a halo | update | At least one newer release exists. Copy a card's command, run it yourself, restart DSH. |
111
+ | chip turns red | failed read | The plugin could not determine the state: the registry read failed or two versions are not SemVer-comparable. |
110
112
 
111
113
  <p align="center">
112
114
  <img src="./assets/sidebar-chip.png" width="300" alt="The version chip in a light shell (grey chip, dark text) and a dark shell (dark grey chip, white text), each showing the green up-to-date dot">
@@ -116,15 +118,14 @@ The chip itself is a neutral second-level surface — grey in both themes, with
116
118
 
117
119
  ## Update check
118
120
 
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.
121
+ The plugin asks the npm registry for `@deepseek-ai/dsh` once per cache window, collects every published version a dist-tag points at, keeps the ones strictly newer than the running release, and lists them newest first. `latest`, `next` and `alpha` are npm bookkeeping, not a user choice: a newer release counts whichever tag carries it.
120
122
 
121
- - The highest SemVer wins, prereleases included, so an `alpha` ahead of the stable line is offered rather than hidden.
123
+ - Every tag npm returns counts, including one this plugin has never seen. A version can carry several tags; its card shows one, picked in the order `latest`, `next`, `alpha`, `beta`, `rc`, then others.
124
+ - SemVer decides the order, prereleases included, so an `alpha` ahead of the stable line is offered rather than hidden.
122
125
  - The comparison is exact: `0.2.1-rc.4` is newer than `0.2.0-rc.2`, and both sort below `0.2.1`.
123
- - A dist-tag the plugin has never heard of still counts — the read takes every tag npm returns, not a fixed triple.
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 detail panel renders one answer; the upgrade command names the exact version found.
126
-
127
- Nothing here installs anything. Choosing to follow a channel — and the `channel` preference that stored it — was removed in `0.2.0`.
126
+ - The running version decides the list. Upgrading DSH and re-checking the panel shrinks it; installing an older one grows it.
127
+ - npm's web page shows only the `latest` tag on the package page; versions carried by other tags live on the Versions page. The panel does not copy that shortcut — it lists them.
128
+ - Nothing here installs anything, and nothing is applied on its own. Choosing to follow a channel — and the `channel` preference that stored it — was removed in `0.2.0`.
128
129
 
129
130
  ## Supervised restart
130
131
 
@@ -161,82 +162,91 @@ A restart interrupts running work and does not save it. If DSH cannot list what
161
162
 
162
163
  ## LAN / non-loopback pages
163
164
 
164
- Earlier DSH releases restricted non-loopback settings forms to memory-only state. DSH `0.2.1-rc.3` and later, verified through `0.2.1-rc.4`, no longer expose 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
+ Earlier DSH releases restricted non-loopback settings forms to memory-only state. DSH `0.2.1-rc.3` and later no longer expose 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
166
 
166
167
  From `0.1.2` this plugin is fully usable there anyway:
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
+ - 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 the release this bundle was built against 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
170
  - **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
171
 
171
172
  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
173
 
173
- ## Compatibility
174
-
175
- Current release: plugin **`0.4.8`** is verified against DeepSeek Harness **`0.2.1-rc.4`** — the newest release npm publishes, currently carried by the `next` tag while `latest` still names **`0.2.1-rc.2`** — and also against **`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`** and **`0.1.7-alpha.2`**.
176
-
177
- ### Which plugin version goes with which DeepSeek Harness version
178
-
179
- | Plugin | Verified DeepSeek Harness | On npm | What that version is |
180
- | --- | --- | --- | --- |
181
- | **`0.4.8`** | `0.2.1-rc.4`, `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` | Declares DSH `0.2.1-rc.4` verified: no functional code changed, both READMEs were re-checked, and the packed file list matches `files[]` (20 files) |
182
- | **`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` | published | Removes the redundant settings menu; version status and update notices remain on by default, with details in the sidebar chip panel |
183
- | **`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 |
184
- | **`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 |
185
- | **`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 |
186
- | **`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 |
187
- | **`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 |
188
- | **`0.4.1`** | `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 | The service saves the PATH used during installation, so tools installed by any package manager stay available after DSH is supervised |
189
- | **`0.4.0`** | `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 | Restart you can trust: the service stops instead of restarting forever, the button needs the service to really own the process, and a disabled button shows the two commands that recover it. Settings also shows when the service started |
190
- | **`0.3.2`** | `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 | Documentation only: the version table and every past release note are now plain language. Behaves exactly like `0.3.1` |
191
- | **`0.3.1`** | `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 | Small polish: the settings page explains Restart too, and a long job name can no longer push the buttons away. |
192
- | **`0.3.0`** | `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 | Adds **Restart** to the panel, plus the one-command service setup it needs. Without that service the button stays disabled and says why. |
193
- | **`0.2.1`** | `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 | Hiding the version chip brings DSH’s own name and fish mark back, instead of leaving the brand row blank. |
194
- | **`0.2.0`** | `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 | One update line instead of a channel picker: the panel reports whatever version npm publishes newest, and there is nothing to configure. |
195
- | **`0.1.12`** | `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 | Adds DSH `0.2.0-rc.2` to the verified list; no code change. |
196
- | **`0.1.11`** | `0.2.0-rc.1`, `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Declares the DSH `0.2.0` line and widens the supported range, so a newer DSH can no longer drop the plugin without a word. |
197
- | **`0.1.10`** | `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | published | No more button in the collapsed sidebar rail — it did not fit there and pushed a neighbouring plugin’s icon aside. |
198
- | `0.1.9` | `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Fixes the plugin disappearing after a DSH upgrade (a leftover copy of a shared library could take it down), and the settings page now says which folder to delete. |
199
- | `0.1.8` | `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Adds DSH `0.1.7-rc.2` to the verified list; no code change. |
200
- | `0.1.7` | `0.1.7-rc.1`, `0.1.7-alpha.2` | published | The English UI is fully English now: status messages are rendered by the browser in its own language. |
201
- | `0.1.6` | `0.1.7-rc.1`, `0.1.7-alpha.2` | published | Adapts to DSH 0.1.7, where the plugin’s two preferences are stored as its own settings entry. |
202
- | `0.1.5` | `0.1.6-alpha.2`, `0.1.6-alpha.1`, `0.1.5-rc.1` | published | One dot carries every state (green up to date, grey checking, amber for an update), and advisory notices stop recolouring the chip. |
203
- | `0.1.4` | `0.1.6-alpha.1`, `0.1.5-rc.1` | published | Fixes the entry for the version you are running showing as unselectable. |
204
- | `0.1.3` | `0.1.6-alpha.1`, `0.1.5-rc.1` | published | Carries the LAN-page fix and re-verifies it on DSH 0.1.6. |
205
- | `0.1.2` | `0.1.5-rc.1` | **never published** | Removes the loopback-only restriction, so a LAN page works too. |
206
- | `0.1.1` | `0.1.5-rc.1` | published | The previous npm `latest`; on a LAN page the plugin does nothing. |
207
- | `0.1.0` | `0.1.2-rc.1` | published | First release. |
208
- - **Which version goes with which DSH?** `0.1.6`–`0.1.10` are for the DSH `0.1.7` line; `0.1.11` and later also declare the `0.2.0` line. DSH 0.1.7 changed how a plugin stores its settings, so on an older DSH — including `0.1.6-alpha.2` — stay on plugin **`0.1.5`**.
209
- - **"Verified"** means that exact DSH release was tested with this build. A release that is missing from the list is shown as *unverified compatible* — a note in the panel only, which never recolours the chip — so upgrading DSH ahead of the plugin is safe to try. If a release turns out genuinely incompatible, disable or uninstall the plugin rather than editing DSH itself. (The list is kept in `package.json` and `src/shared/types.ts`, in sync by a test.)
174
+ ## Loadability and update notices
175
+
176
+ This plugin does not vouch for any DeepSeek Harness release. Loading is DSH's decision, and DSH makes it from two declarations only: `dsh.engines.dsh` says `>=0.1.7-alpha.2 <0.3.0`, and the `@deepseek-ai/dsh-settings` peer range says the same. Inside those bounds you can run any DSH release you like; no plugin update is needed to "allow" a newer one.
177
+
178
+ `0.5.0` removed the earlier mechanism completely. There is no verified-release list, no `dsh.compatibility` metadata, no verified or unverified label in the panel, and no warning because a newer DSH release was untested. The plugin's job is only to say that a newer release exists and how to upgrade; keeping a compatibility ledger was out of scope, and it had produced six releases in 13 days whose headline was a declaration.
179
+
180
+ What remains is the update notice: one card per version newer than the running one, each with its own command. What the plugin knows about a release is what npm publishes — version, tag and publish date — and it says nothing about whether the release is good for you.
181
+
182
+ The rows below `0.5.0` in the table still mention that removed list; that is history, and no release now waits for a list entry.
183
+
184
+ ### Plugin versions on npm
185
+
186
+ | Plugin | On npm | What that version is |
187
+ | --- | --- | --- |
188
+ | **`0.5.0`** | `latest` | One card per upgradable version, each with its own copy-only command; the verified-release mechanism is removed and DSH's engine and peer ranges alone decide loading |
189
+ | **`0.4.8`** | published | Added DSH `0.2.1-rc.4` to the then-current verified list, under the mechanism `0.5.0` removed; no functional code changed |
190
+ | **`0.4.7`** | published | Removes the redundant settings menu; version status and update notices remain on by default, with details in the sidebar chip panel |
191
+ | **`0.4.6`** | published | Added DSH `0.2.1-rc.3` to the then-current verified list; includes maintenance and starting terminals in restart confirmation, and restores restart-storm recovery guidance |
192
+ | **`0.4.5`** | published | Added DSH `0.2.1-rc.2` to the then-current verified list; no functional code changed |
193
+ | **`0.4.4`** | published | Added DSH `0.2.1-alpha.5` to the then-current verified list; no functional code changed |
194
+ | **`0.4.3`** | published | Added DSH `0.2.1-alpha.4` to the then-current verified list; no functional code changed |
195
+ | **`0.4.2`** | published | Added DSH `0.2.1-alpha.3` to the then-current verified list; no functional code changed |
196
+ | **`0.4.1`** | published | The service saves the PATH used during installation, so tools installed by any package manager stay available after DSH is supervised |
197
+ | **`0.4.0`** | published | Restart you can trust: the service stops instead of restarting forever, the button needs the service to really own the process, and a disabled button shows the two commands that recover it |
198
+ | **`0.3.2`** | published | Documentation only: the version table and every past release note are now plain language. Behaves exactly like `0.3.1` |
199
+ | **`0.3.1`** | published | Small polish: the panel explains Restart, and a long job name can no longer push the buttons away. |
200
+ | **`0.3.0`** | published | Adds **Restart** to the panel, plus the one-command service setup it needs. Without that service the button stays disabled and says why. |
201
+ | **`0.2.1`** | published | Hiding the version chip brings DSH’s own name and fish mark back, instead of leaving the brand row blank. |
202
+ | **`0.2.0`** | published | One update line instead of a channel picker: the panel reports the newest published version, and there is nothing to configure. |
203
+ | **`0.1.12`** | published | Added DSH `0.2.0-rc.2` to the then-current verified list; no code change. |
204
+ | **`0.1.11`** | published | Declared the DSH `0.2.0` line and widened the supported range, so a newer DSH could no longer drop the plugin without a word. |
205
+ | **`0.1.10`** | published | No more button in the collapsed sidebar rail — it did not fit there and pushed a neighbouring plugin’s icon aside. |
206
+ | `0.1.9` | published | Fixes the plugin disappearing after a DSH upgrade (a leftover copy of a shared library could take it down), and the panel says which folder to delete. |
207
+ | `0.1.8` | published | Added DSH `0.1.7-rc.2` to the then-current verified list; no code change. |
208
+ | `0.1.7` | published | The English UI is fully English now: status messages are rendered by the browser in its own language. |
209
+ | `0.1.6` | published | Adapts to DSH 0.1.7, where the plugin’s two preferences are stored as its own settings entry. |
210
+ | `0.1.5` | published | One dot carries every state (green up to date, grey checking, amber for an update), and advisory notices stop recolouring the chip. |
211
+ | `0.1.4` | published | Fixes the entry for the version you are running showing as unselectable. |
212
+ | `0.1.3` | published | Carries the LAN-page fix and was checked on the then-current DSH 0.1.6. |
213
+ | `0.1.2` | **never published** | Removes the loopback-only restriction, so a LAN page works too. |
214
+ | `0.1.1` | published | The previous npm `latest`; on a LAN page the plugin does nothing. |
215
+ | `0.1.0` | published | First release. |
216
+
217
+ - **Which version for which DSH?** `0.1.6`–`0.1.10` were built for the DSH `0.1.7` line; `0.1.11` and later also accept the `0.2.0` line. DSH 0.1.7 changed how a plugin stores its settings, so on an older DSH — including `0.1.6-alpha.2` — stay on plugin **`0.1.5`**.
218
+ - **Loadability is decided by DSH, not by a label.** If a DSH release refuses to load this plugin, disable or uninstall the plugin rather than editing DSH — and please report it. There is no tested-release list any more, and no list entry to wait for.
210
219
  - **On npm** means what `dsh plugin --profile web add dsh-update-status@latest` actually installs. A version that exists in this repository but not on npm is a development state, not a release.
211
220
 
212
- - Match them explicitly when it matters:
221
+ - Pin a plugin version when you need to stay on one:
213
222
 
214
223
  ```sh
215
- dsh plugin --profile web add dsh-update-status@0.4.8 # DSH 0.2.1-rc.4, 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
216
- 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
217
- dsh plugin --profile web add dsh-update-status@0.4.6 # 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
218
- 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
219
- 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
220
- 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
221
- dsh plugin --profile web add dsh-update-status@0.4.2 # DSH 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
222
- dsh plugin --profile web add dsh-update-status@0.3.2 # DSH 0.2.1-alpha.1
223
- dsh plugin --profile web add dsh-update-status@0.2.0 # DSH 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
224
- dsh plugin --profile web add dsh-update-status@0.1.12 # DSH 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
225
- dsh plugin --profile web add dsh-update-status@0.1.11 # DSH 0.2.0-rc.1, 0.1.7-rc.2, 0.1.7-rc.1 or 0.1.7-alpha.2
226
- dsh plugin --profile web add dsh-update-status@0.1.10 # DSH 0.1.7-rc.2, 0.1.7-rc.1 or 0.1.7-alpha.2
227
- dsh plugin --profile web add dsh-update-status@0.1.9 # DSH 0.1.7-rc.2, 0.1.7-rc.1 or 0.1.7-alpha.2
228
- dsh plugin --profile web add dsh-update-status@0.1.8 # DSH 0.1.7-rc.2, 0.1.7-rc.1 or 0.1.7-alpha.2
229
- dsh plugin --profile web add dsh-update-status@0.1.7 # DSH 0.1.7-rc.1 or 0.1.7-alpha.2
230
- dsh plugin --profile web add dsh-update-status@0.1.6 # DSH 0.1.7-rc.1 or 0.1.7-alpha.2
231
- dsh plugin --profile web add dsh-update-status@0.1.5 # DSH 0.1.6-alpha.2, 0.1.6-alpha.1 or 0.1.5-rc.1
232
- dsh plugin --profile web add dsh-update-status@0.1.4 # DSH 0.1.6-alpha.1 or 0.1.5-rc.1
233
- dsh plugin --profile web add dsh-update-status@0.1.0 # DSH 0.1.2-rc.1 only
224
+ dsh plugin --profile web add dsh-update-status@0.5.0
225
+ dsh plugin --profile web add dsh-update-status@0.4.8
226
+ dsh plugin --profile web add dsh-update-status@0.4.7
227
+ dsh plugin --profile web add dsh-update-status@0.4.6
228
+ dsh plugin --profile web add dsh-update-status@0.4.5
229
+ dsh plugin --profile web add dsh-update-status@0.4.4
230
+ dsh plugin --profile web add dsh-update-status@0.4.3
231
+ dsh plugin --profile web add dsh-update-status@0.4.2
232
+ dsh plugin --profile web add dsh-update-status@0.3.2
233
+ dsh plugin --profile web add dsh-update-status@0.2.0
234
+ dsh plugin --profile web add dsh-update-status@0.1.12
235
+ dsh plugin --profile web add dsh-update-status@0.1.11
236
+ dsh plugin --profile web add dsh-update-status@0.1.10
237
+ dsh plugin --profile web add dsh-update-status@0.1.9
238
+ dsh plugin --profile web add dsh-update-status@0.1.8
239
+ dsh plugin --profile web add dsh-update-status@0.1.7
240
+ dsh plugin --profile web add dsh-update-status@0.1.6
241
+ dsh plugin --profile web add dsh-update-status@0.1.5
242
+ dsh plugin --profile web add dsh-update-status@0.1.4
243
+ dsh plugin --profile web add dsh-update-status@0.1.0
234
244
  ```
235
245
 
236
- - Two declarations make the verified lines load at all, and a test keeps them honest:
237
- - `dsh.engines.dsh` and `peerDependencies['@deepseek-ai/dsh-settings']` both declare `>=0.1.7-alpha.2 <0.3.0`, which admits all twelve 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.
246
+ - Two declarations decide whether the plugin loads at all, and DSH evaluates them at profile load:
247
+ - `dsh.engines.dsh` and `peerDependencies['@deepseek-ai/dsh-settings']` both declare `>=0.1.7-alpha.2 <0.3.0`. 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. These bounds decide loading only — they are not a claim that every release inside them was tested.
238
248
  - `@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.
239
- - 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.8`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.8.md) · [`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`).
249
+ - 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.5.0`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.5.0.md) · [`v0.4.8`](https://github.com/idoall/dsh-update-status/blob/main/docs/releases/v0.4.8.md) · [`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`).
240
250
 
241
251
  ## Configuration
242
252
 
@@ -252,7 +262,7 @@ A cache preference is written only by your own selection in the panel. The plugi
252
262
  ## Troubleshooting
253
263
 
254
264
  **The chip shows a version that is not what I just installed, and tapping it does nothing.**
255
- That is the `connection.isLoopback` gate from plugin `0.1.1` and earlier: on a non-loopback page such as a LAN bridge (`dsh-bridge`, `dsh-lan-proxy`) the whole plugin goes inert and the chip falls back to this bundle's declared compatible release. Check what is installed and upgrade:
265
+ That is the `connection.isLoopback` gate from plugin `0.1.1` and earlier: on a non-loopback page such as a LAN bridge (`dsh-bridge`, `dsh-lan-proxy`) the whole plugin goes inert and the chip shows the release this bundle was built against instead of the running one. Check what is installed and upgrade:
256
266
 
257
267
  ```sh
258
268
  node -p "require(process.env.HOME + '/.dsh/profiles/web/node_modules/dsh-update-status/package.json').version" # 0.1.3 or newer
@@ -260,13 +270,14 @@ dsh plugin --profile web add dsh-update-status@latest
260
270
  ```
261
271
 
262
272
  **The chip turned red right after I upgraded DSH.**
263
- On `0.1.5` and newer a red chip means one thing: the plugin could not determine the update state — the registry read failed, or the two versions are not SemVer-comparable. Up to `0.1.4` the rule was broader: the client treated **any** warning as a problem, and *"this preview has not been verified against the plugin"* is exactly the warning a DSH release newer than the plugin's list produces. Upgrading DSH ahead of the plugin therefore painted the chip red even though the read had succeeded. `0.1.5` splits the two — `failure` still repaints, an advisory stays in the panel — so upgrade if you keep DSH ahead of this plugin:
273
+ On `0.1.5` and newer a red chip means one thing: the plugin could not determine the update state — the registry read failed, or two versions are not SemVer-comparable. Up to `0.1.4` the rule was broader: the client treated **any** warning as a problem, so a DSH release newer than the plugin's list painted the chip red even though the read had succeeded. `0.1.5` splits the two — `failure` still repaints, an advisory stays in the panel. `0.5.0` removes that advisory altogether, so a newer DSH release can no longer produce one:
264
274
 
265
275
  ```sh
266
276
  dsh plugin --profile web add dsh-update-status@latest
267
277
  ```
268
278
 
269
- Until then the advisory is harmless: it appears in the panel only, and disappears as soon as a later plugin release declares your DSH release as verified.
279
+ **No card appears even though I know a newer DSH exists.**
280
+ The list is built from npm's published versions at the moment of the check, compared with the version this page reports as running. Press **Check for updates** for a fresh read. If a release is only tagged in a registry the plugin cannot see, or the running version is already the highest one published, there is nothing to show — and no card is the correct answer.
270
281
 
271
282
  **The version never changes.**
272
283
  The Host caches one registry response, 360 minutes by default, and only a normal read can expire it. Press **Check for updates** for an immediate refresh, or lower `cacheTtlMinutes`. A failed check keeps the last good cache and shows the warning next to the version.