Skip to content

v0.2.0

Choose a tag to compare

View all tags
@beihzb beihzb released this 09 Oct 10:46
· 2 commits to main since this release
v0.2.0
bd950ae

v0.2.0

Admits the DSH 0.2.0-rc line, so the plugin is no longer skipped at startup on a 0.2.x runtime.

Why

DSH refuses to boot a plugin bundle whose @deepseek-ai/dsh* peer range excludes the running runtime — it prints

dsh: skipping profile bundle "@beihaizb/dsh-envsel": Error: Plugin @beihaizb/dsh-envsel@0.1.6 is incompatible
with dsh 0.2.0-rc.2: peerDependencies {...}. ... Exact-version exemption: not active.

and then loads the rest of the profile without this bundle. All 18 @deepseek-ai/dsh-* peers were pinned to ^0.1.7-rc.1, whose upper bound is <0.2.0, so a 0.2.x runtime was rejected. The gate is not new — it is the same rule DSH applied on the 0.1.7 line.

Change

  • peerDependencies and devDependencies: every @deepseek-ai/dsh-* entry is now ^0.1.7-rc.1 || ^0.2.0-rc.1, which admits 0.1.7-rc.2, 0.2.0-rc.1, 0.2.0-rc.2 and 0.2.1-alpha.2.
  • No source change. The seams this plugin uses are unchanged between the two lines; the shipped lib/ is identical to 0.1.6.
  • README (EN / 中文): Requirements, the version-compatibility table (new 0.2.0 row) and the peer-bound note now describe both lines. The earlier Requirements text claimed only the Typert peer was raised while "the other peers stay at ^0.1.0-rc.7" — that was stale since the 0.1.7 bump and is corrected here.

Install

dsh plugin --profile web add @beihaizb/dsh-envsel@0.2.0

Then restart dsh web.

Version pinning: if you install shortly after this release, pnpm's supply-chain policy (minimumReleaseAge) may skip the just-published version and install an older one. Pin the version explicitly as above, or use @latest once the release is older than the policy window.

Verification

  • Startup compatibility gate replayed with DSH's own rule (@deepseek-ai/dsh-app-boot/lib/index.js:286-313) and the real semver: 0.1.7-rc.2 / 0.2.0-rc.1 / 0.2.0-rc.2 / 0.2.1-alpha.2 all pass, for both this repo's manifest and an installed copy.
  • pnpm run build (tsc typecheck + tsdown) passes; the rebuilt bundle differs from the committed one only in the emission order of CSS-module class-name keys, so the committed artifact is kept as-is.
  • On DSH 0.1.7-rc.2 the plugin was verified previously (header dropdown included). The 0.2.0-rc line is admitted by the peer range; the runtime check of the header dropdown on 0.2.0-rc.2 is the follow-up step for this release.
Assets 2
Loading