Files
zhu1090093659 30ab8692a9 chore(sdk): advance the plugin cohort to 0.1.7-rc.2
Move every family manifest, the plugin scaffold and the shared workspace
package onto the 0.1.7-rc.2 cohort, together with the surfaces that state
the same fact:

- the dsh.engines.dsh floors and the matching @deepseek-ai/dsh host peers
- the release-age exclusion ledger and the two packageExtensions keys
- the root README badges, the CI/release mount-smoke pins and the
  docs/publish-prep.md and docs/plugins.md prose

Two rc.2 facts were verified against the published artifacts rather than
inferred from the version number:

- the shell's frozen static module table is unchanged (the same nine
  specifiers in the dsh-web-frontend rc.2 dist bundle), so
  shared/web-platform.ts keeps its list and only its provenance comment
  moves; the new dsh-client-shortcuts is an ordinary client plugin, not a
  static module
- @deepseek-ai/dsh-client-ui-primitives@0.1.7-rc.2 imports a further
  undeclared face, @deepseek-ai/dsh-util-code-language, so the
  primitives packageExtensions patch gains that pin

The satellite peer floors in pnpm-lock.yaml still read >=0.1.7-rc.1: they
belong to the satellite packages and move when those repositories release
the aligned version.
2026-09-24 22:26:05 +08:00

24 lines
683 B
JSON

{
"name": "dsh-web-shared",
"version": "0.0.0",
"private": true,
"type": "module",
"description": "Shared runtime modules for the dsh-web plugin family (inlined into each consumer bundle; never published).",
"scripts": {
"typecheck": "tsc --noEmit",
"test": "vitest run"
},
"devDependencies": {
"@deepseek-ai/dsh-client-store": "^0.1.7-rc.2",
"@deepseek-ai/dsh-client-ui-settings": "0.1.7-rc.2",
"@deepseek-ai/dsh-client-ui-slots": "0.1.7-rc.2",
"@types/node": "^22.20.1",
"@types/react": "~18.3.1",
"@types/react-dom": "~18.3.0",
"jsdom": "29.1.1",
"react": "^18.2.0",
"typescript": "^6.0.3",
"vitest": "^4.1.8"
}
}