dsh-plugin-console v0.3.1

Documentation-only release shipping the corrected upgrade path. No Host or client code changes.

Changed

• README install command pins @latest: dsh plugin --profile web add dsh-plugin-console@latest — fresh installs always resolve the newest release at install time.
• Documents that re-running the bare install command dsh plugin --profile web add dsh-plugin-console does not upgrade an existing profile: pnpm keeps the already-pinned ^x.y.z range and reports "Already up to date". Upgrade via add dsh-plugin-console@latest or the built-in one-click self-update (Settings → Plugin manager → Installed), then restart dsh web and refresh the browser.
• New troubleshooting section: registry/mirror sync lag, checking the profile's actual pinned/installed versions, missing restarts.
• RELEASING.md: hardcoded example versions replaced with <version> placeholders; post-publish verification steps added.

Upgrade: dsh plugin --profile web add dsh-plugin-console@latest, then restart.

dsh-plugin-console v0.2.2

Changelog

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

[0.2.2] - 2026-08-20

Added

• 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.

Fixed

• 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.

[0.2.1] - 2026-08-19

Added

• 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.

Changed

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

dsh-plugin-console v0.2.1

Changelog

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

[0.2.1] - 2026-08-19

Added

• 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.

Changed

• Failed canaries automatically restore the previous profile metadata and dependency graph without deleting the entire node_modules directory first.
• Operation results and confirmation UI report whether the isolated canary passed or failed.
• The canary now evaluates the complete composed profile, so initialization conflicts with existing third-party bundles are treated as update failures; uncertain recovery retains the original dependency snapshot for inspection.
• Profile locks reclaim stale directories atomically, and metadata recovery uses atomic writes.
• Removal now verifies that the package is gone from both profile dependencies and dsh.profile.bundles, repairing stale bundle entries left by older or replaced DSH launchers; any repair or composition failure restores the previous profile state.
• Removal success now explains that the running Host and browser still hold their startup module graph and must be restarted/refreshed; update discovery remains read-only and every install/update requires the visible review and confirmation controls.

[0.2.0] - 2026-08-19

Added

• First-level Settings → Plugin Manager page with catalog and installed-package views.
• Persisted pause and resume operations that cover every Loader entry contributed by an installed bundle, including aggregate bundles.
• README-specific GFM renderer with sanitized common HTML, GitHub-relative links and images, and a source view.
• Explicit dsh and pnpm capability reporting, localized pause/resume states, and focused operation diagnostics.

Changed

• Release publishing is idempotent when an npm version already exists and requires the repository npm environment to provide NPM_TOKEN for new versions.
• Profile capability checks accept optional workspace and lock files, while integrity validation follows the root pnpm importer and peer-suffixed resolutions.
• Pending installations can be removed before restart, allowing an installation to be cancelled cleanly.

Fixed

dsh-plugin-console v0.2.0

Full Changelog: v0.1.0...v0.2.0