dsh-versions

Upgrading the Dsh CLI by hand means running npm install -g globally, hoping a mirror does not hiccup, and praying you can roll back if anything goes sideways. dsh-versions folds all of that into a dedicated Version Management section under Settings in dsh web: see your current version and dist-tag channel at a glance, check the npm registry for the latest release with a ten-minute cache, and browse every published build grouped by latest, next, and alpha.

The upgrade engine is the heart of the plugin. Before every install it takes a local snapshot of the current version and a full backup of the framework directory, then runs npm install -g against two registries in sequence (npmjs first, then npmmirror), validates the result against the on-disk package.json, and—if anything fails—restores the backup with robocopy before relaunching the service. Every operation is appended to a local history.jsonl with source, target, and outcome. Up to five snapshots are kept on disk, so you can roll back to any previous version in seconds with no npm call and no network needed.

Version browsing and update checks work on every platform. The upgrade, reinstall, restore, and manual-restart engine, however, relies on Windows tooling (robocopy, schtasks, PowerShell 5.1), so those controls are disabled on macOS and Linux with a clear hint. If you want a browser-driven, snapshot-backed way to manage your Dsh main program on Windows—one-click upgrades, downgrades, reinstalls, instant rollback, and a full audit trail—dsh-versions fills that niche entirely from the settings page.