PerryLink/dsh-plugin-upgrade
Plugin upgrade skill for DeepSeek Harness: one package with version-corridor indexes that migrate a plugin between DSH release bands.
An upgrade skill for DeepSeek Harness plugins that routes a repository to a matching closed corridor card and scans it for version-specific seams. It ships a bundled agent skill (plugin-upgrade) with the corridor cards and a fix-and-verify loop, plus a zero-dependency CLI (dsh-plugin-upgrade-scan) that resolves the corridor and reports file:line facts for that corridor's seams. Two corridors are covered: legAB (0.1.3-alpha.1 → 0.1.5-rc.1, twenty seams) and legC (0.1.5-rc.2 → 0.1.6-alpha.2, five seams E1–E5). The scanner chooses the corridor from the target repo's declared dsh band (or an explicit --span) and exits 1 on any error-severity hit so it can drop straight into CI. It targets this span's silent breakage, such as a stale type line (seam M1) and deleted client slots such as the bare 'conversation' key (seam C1), which pass typecheck and tests while the host drops the contribution. One package, one corridor index: it supersedes the retired version-locked packages dsh-plugin-upgrade-015 (leg A) and dsh-plugin-upgrade-016 (leg B/C), and the two catalogs are never merged.
Install
dsh plugin --profile web add dsh-plugin-upgradeCopied verbatim from the README's 'Install & uninstall' section (npm channel, also shown as step 1 of 'Quick start'). No placeholder is used; the README also lists the source channel, dsh plugin --profile web add "github:PerryLink/dsh-plugin-upgrade#main", and the reversible uninstall dsh plugin --profile web remove dsh-plugin-upgrade. Installing the bundle only registers a skill (removing the row removes the skill), and the bundled CLI is a normal npx target (npx dsh-plugin-upgrade-scan --repo ../my-plugin) that needs no profile.
Compatibility
Node ^22.19.0 || >=24.0.0; Harness DeepSeek Harness dsh-v0.2.1-alpha.1 (dev/test pins 0.2.1-alpha.1). Peer band: @deepseek-ai/dsh-skill >=0.1.6-0 <0.2.0 || >=0.2.0-0 <0.3.0 || >=0.2.1-0 <0.3.0, @deepseek-ai/cordis ^4.0.5-alpha.1, @deepseek-ai/schemastery ^3.18.5-alpha.1. Platforms: anywhere Node runs (the scanner is filesystem-only and platform-neutral); text-only models are fully supported (the skill is a Markdown body with no tool or vision requirement). It registers by inserting a profile patch row that mounts a bundled agent skill named 'plugin-upgrade' (model- and user-invocable), plus a zero-dependency CLI.
Details
- Repo: PerryLink/dsh-plugin-upgrade
- Category: Plugin Markets & Managers
- Stars: 2
- Version: GitHub repo PerryLink/dsh-plugin-upgrade; npm package dsh-plugin-upgrade; Apache-2.0. The README states no explicit package version number; it notes that the version-locked packages dsh-plugin-upgrade-015 and dsh-plugin-upgrade-016 are retired as of 2026-10-05.
FAQ
- How do I run the seam scanner?
- The README (Quick start) shows npx dsh-plugin-upgrade-scan --repo ../my-plugin; the scanner picks the corridor for you, and you add --span legC when the declared band is ambiguous. Flags include --repo <path>, --span legAB|legC, --json <out.json>, --seams S3,C1,P1 and --quiet; exit codes are 0 (no error-severity hit), 1 (at least one) and 2 (usage or scan failure).
- Can I mount the retired dsh-plugin-upgrade alongside this one?
- No. The README (Compatibility, Sibling row) says both register the agent skill 'plugin-upgrade', so the second mount collides on the skill name; that package is deprecated on npm and its repository is retired, and this package replaces both of its legs.
- Does a clean scan mean the upgrade is finished?
- No. The README states a clean scan is necessary but not sufficient — the exit criterion is a real-host smoke (temp DSH_HOME, target CLI, plugin add <tarball>, --dump-config) plus a resume round-trip for session-log writers (leg A) and a real browser assertion for the client half (leg B).
Alternatives
alex04130/dsh-forge · Toukaiteio/dsh-plugin-installer · lxzy-7/dsh-plugin-guard