DSH plugin market update badge stuck: causes and fixes

The badge has been lit for a week: you click Update, restart, and it is still lit — the most frustrating loop in update problems, because you acted and the interface refuses to acknowledge it. In dsh plugin market, an update badge only means "a newer version was detected"; it says nothing about success and nothing about the version actually changing (2.2.5 index). This article works by recovery priority: identify which of three causes you have, then decide whether to restart, roll back or refresh the index. The update entry sits on installed-list rows and market cards inside DSH Plugin Hub.

Why the DSH plugin market badge stays lit: real update, stale index, version pinning

A lit badge is not proof of failure: it may mean a genuinely newer version exists, the market index has not refreshed, or you pinned the version yourself. The three require completely different responses, so diagnose before acting.

1. Open the installed list and note the plugin's current version.
2. Return to the market, search for the same plugin and note the latest version on its card.
3. If the two differ, update normally; if they match and the badge persists, refresh or restart first.
4. If the version is pinned to an old build, confirm that was intentional before unpinning.

The key comparison is between installed version and market latest version. The badge alone cannot tell you whether the update failed or whether there was never anything to update.

After the update confirmation, why DeepSeek Harness must restart

The confirmation dialog only writes the new version in; the restart is what makes the running process use it. Skip the restart and the package has changed while the entry still runs old code.

1. After clicking Update Available, read the new version details in the dialog and confirm this is the version you want.
2. Confirm and wait for installation, watching notifications for a pending-restart reminder.
3. Fully quit and restart DeepSeek Harness; refreshing the page is not enough.
4. Reopen the plugin entry and invoke it once to confirm the new version behaves correctly.
5. Return to the installed list to check the version, then to the market to see whether the badge cleared.

The restart is not ceremony — it follows from load timing. Plugins load from the profile manifest at startup, and a running process does not swap modules just because the package was overwritten. Clicking Update again while a pending-restart reminder is visible only overwrites the same version.

Recovery order after a failed update in dsh plugin market

Recover in the order restart, retry once, roll back — one variable per step. Reinstalling immediately wipes the failure scene along with the problem.

1. Level one: restart. Confirm that "pending restart" was not misread as failure; after restarting, check version and entry.
2. Level two: retry once. Confirm the failing stage in notifications, fix the network or mirror issue, then retry exactly once.
3. Level three: roll back. If the retry fails, reinstall the last known good version and restore usability first.
4. Level four: change source. If you still want the upgrade after rolling back, try the npm prebuilt release or another source that avoids the failing channel.
5. Record. Write down the failing stage, version and outcome for the next attempt.

The core principle is restore usability before chasing the latest version. Repeatedly updating a broken environment makes the version state harder and harder to read. For the mechanics of rolling back, see how to roll back a failed update.

# Read-only check 1: the actual version in the current profile
dsh plugin --profile web list
# Read-only check 2: which profile holds the load layer
dsh --profile web --dump-config | grep -in <plugin-keyword>

Neither command changes anything. Confirm you are looking at the same profile and the same version before discussing updates. Many "failed updates" are actually installed in one profile and inspected in another.

Cache and index: why clearing the cache leaves the dsh plugin market badge lit

The badge is computed by comparing the market index with the installed version, and clearing the browser cache may not refresh that index. What you cleared is page assets; the index data may still sit on the server or in local configuration.

1. Restart the host first so the market fetches the index again, then check the badge.
2. Refresh the market page and look at whether the latest version on the card changed.
3. If the version is unchanged and the badge remains, verify the actual installed version.
4. If the installed version is already latest and the badge is still lit, treat it as a stale index, note the timestamp and keep watching.
5. Never uninstall and reinstall repeatedly just to make the badge disappear; that scrambles plugin state.

Cache problems generate the most false failures: you think the update did not work when the version is already correct and only the index lags. The judgment standard is always installed version versus market latest, not the color of a badge.

Should the version pin be removed?

1. If you pinned to avoid a known issue, do not unpin merely to clear the badge.
2. If the pin is leftover from an old trial, confirm the new version's compatibility range before unpinning.
3. After unpinning, run a normal update and confirm the version actually changes.
4. Then decide whether to pin again and write down the reason.

How to tell the update really finished: three DSH Plugin Hub proofs

Completion needs three proofs: version, entry behavior and a clean log. The badge disappearing is only a fourth signal and may be an artifact of index refresh.

1. Version: the installed list shows the target version.
2. Entry behavior: after restart, the plugin entry opens and one real invocation works.
3. Logs: system logs contain no new activation or dependency error for that plugin.
4. Badge: only after the first three line up, check whether the badge cleared; if it did not, the conclusion stands anyway.
5. Record: note version, time and verification result in your environment notes.

If any of the first three fails, return to the diagnosis table instead of reinstalling. For pinned versions, see how to pin a plugin version; for why a restart is mandatory, compare plugin updates and restarts.