dsh-upgrade-assistant

Usage

1. Sidebar → Plugins → the Upgrades tab
2. Check plugin updates: compares each installed bundle against npm (profile mirror aware, 5-minute cache, concurrency 3)
3. Green Upgrade available → click Upgrade (inline confirm, then it runs); yellow Needs newer DSH → upgrade DSH first — the button is hidden because the attempt would certainly fail
4. Check DSH updates: compares the running Harness against the newest npm release

How the updates actually work

• npm-installed plugins: in-place pnpm update --latest --config.minimumReleaseAge=0 . The minimumReleaseAge=0 override skips pnpm's 24-hour release-cooling gate (the classic "version is too new to install" failure); this only happens on your explicit click.
• Transitive families (npm dependencies pulled in by GitHub-sourced bundles such as the dsh-web family): pnpm update --latest cannot move transitive dependencies — it silently no-ops. The tab instead runs an in-range refresh (pnpm update --config.minimumReleaseAge=0), moving each dependency to the newest version its parent's semver range allows.
• Post-run verification: the actually installed version is re-read from node_modules; a green pnpm exit that moved nothing is reported as stale, never as success.
• Downgrade protection: when npm's latest tag is behind the installed version (common for the official @deepseek-ai/* packages), the update is refused.