Repository navigation
v2.3.6 — installer crashes without packaging evidence go to hub triage
DSH Plugin Hub is the community plugin marketplace plugin for DeepSeek Harness — https://dsh-plugin.org
This release stops blaming plugin authors for installer crashes that carry no packaging evidence, and validates the pinned npm version when matching an install target to its repository.
What's fixed
- Opaque installer crashes are no longer reported as "plugin distribution incomplete". A bare
Command failedline is only the outer process wrapper — when the embedded Electron pnpm exits without echoing pnpm output, that line says nothing about the package itself. The hub now requires positive packaging evidence (ERR_PNPM_PREPARE_PACKAGE,ELIFECYCLE,prepare-guard,prepare script failed,Failed to prepare) before classifying the failure as a plugin problem; anything else is routed to hub triage instead of generating an issue in an unrelated author's repository (#685). - Failure classification keeps real packaging failures intact. A prepare script that actually fails still classifies as a plugin packaging problem, so genuine author-side defects are reported exactly as before.
- Catalog installs validate the version they are about to install. When the hub pins an exact npm version, the repository/
dsh-pluginmetadata check now queries that version's manifest instead oflatest, so the repository-to-package mapping used by the installed list is recorded against the version actually installed (#679).
Install
dsh plugin --profile web add dsh-plugin
dsh plugin --profile web add git+https://github.com/dshplugin/dsh-plugin-hub.git