Changelog

All notable changes to DSH Plugin Console are documented here. The project follows Semantic Versioning.

[0.2.2] - 2026-08-20

One-click updates for installed community plugins and dsh-plugin-console itself; the existing canary, profile lock, stale-plan checks and rollback remain on the execution path, followed by the normal restart notice.
GitHub CI and release jobs install the pinned DSH CLI required by the isolated activation tests; release runs can be manually retried against an existing v* tag.

Preserve update discovery after an operation by refreshing the installed projection instead of replacing it with a snapshot that omits latest-version data.
Reject updates against pending profile changes and stale pause/remove plans whose requested source changed at the same version.
Bound npm registry metadata responses, clean command timeout timers, terminate timed-out capability probes, and prevent catalog refresh from racing initial bootstrap.
CI pack verification no longer re-runs the full test suite inside npm pack --dry-run, and rollback fixtures stop inheriting npm's dry-run flag when they are packed during a prepack run.
Localize common command, plan, catalog and recovery failure states instead of exposing internal error codes.

Isolated activation canary for installs and updates: a temporary DSH Web profile starts on an OS-assigned local port, validates the exact package version, target Loader entries, client-bundle syntax/execution/registration/module dependencies and HTTP resources, and terminates before the real profile is accepted; browser UI interaction remains a manual post-restart check.

Failed canaries automatically restore the previous profile metadata and dependency graph without deleting the entire node_modules directory first.