Files
deepseek-harness/docs/upgrade-guide/v0.2.1-alpha.3/plugin-engines-dsh/guide.md
T
turtle1999 3de3a977e0 feat(plugin-market): add the Custom plugin markets bundle and Discover tab
Read configured plugin market indexes on the Host, search them with fuzzy
multilingual matching, and install a chosen version from the Plugins page.

- dsh-plugin-market-index validates format-1 indexes and builds install
  arguments; inline icons are capped at 32 KiB.
- The pluginMarket service fetches configured http(s) URLs, parses bodies in
  a Worker Thread, caches documents, and pages filtered, ordered results with
  installation status and engines.dsh compatibility.
- Discover is an opt-in experimental bundle; the Plugins page gains a
  plugins.tab slot and confirmed installs.
- The plugin_market tool lists indexes, plugins, and versions for Creator mode.
- Plugin compatibility reads engines.dsh before DSH peer dependencies.
2026-10-15 05:37:44 +08:00

1.8 KiB

kind, description
kind description
upgrade-guide Plugin compatibility checks read engines.dsh before DSH peerDependencies, and refusals report requirements instead of peers.

Plugin compatibility reads engines.dsh first

English | 中文

Change

In v0.2.1-alpha.3, installation and profile startup judged a plugin or bundle only by its peerDependencies on @deepseek-ai/dsh and @deepseek-ai/dsh-*, and ignored engines.dsh. In the next release, an own engines.dsh range decides alone and those peers are ignored; the peer rule applies only when engines.dsh is absent. workspace: values are valid only in peers; in engines.dsh they are incompatible. A non-object engines or a non-string engines.dsh makes the manifest unreadable for compatibility, which refuses the package. Plugin authors whose package declares engines.dsh, or declares engines as something other than an object, are affected.

The incompatible-version refusal record that the plugin manager returns to clients, IncompatiblePlugin, and the app-boot PluginCompatibility result rename peers to requirements. Keys are engines.dsh for the engines rule or the peer package name for the fallback. Code that reads these records is affected.

Migration

  1. If your package declares engines.dsh, make that range cover every DSH release the package supports, because DSH peer ranges no longer widen or narrow it. Remove engines.dsh to keep peer-based checking.
  2. Replace workspace: values in engines.dsh with a semantic version range.
  3. Read requirements instead of peers from IncompatiblePlugin and PluginCompatibility.
  4. Confirm by installing the package with dsh plugin --profile <profile> add <package@version> or the plugin manager: a mismatch names engines.dsh or the peer package in the refusal.