Skip to content

Releases: PerryLink/dsh-plugin-kit

v0.1.9

Choose a tag to compare

@github-actions github-actions released this 12 Sep 02:31

[0.1.9] - 2026-09-12

Added

  • scripts/check-peer-range-latest.mjs — a dependency-free tripwire that reads the published @deepseek-ai/dsh dist-tags and fails when the canonical peer range no longer admits one, printing the clause to append. semver only admits a prerelease when a comparator in the same [major, minor, patch] tuple carries a prerelease, so every new upstream prerelease tuple silently stops matching; this turns that into a red gate. Wired into .github/workflows/peer-range.yml (push, PR, nightly, manual).

Changed

  • Rename the four translated READMEs to README-<lang>.md. npm selects the package-page readme as the first markdown file matching its {README,README.*} glob (@npmcli/package-json, publish path), and that glob order puts README.<lang>.md ahead of README.md — so npm was serving the Simplified-Chinese file for this package too (measured on 15/15 sampled packages of the family). The new names sit outside the glob, so the English source is served again. No content changed apart from the language-switcher link each translation holds to its siblings, and the repo readme gate still passes. Takes effect with the next release; an already-published version cannot gain a corrected readme retroactively.
  • data/peer-range.json canonical range is now >=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 (was the stale >=0.1.0-rc.8 <0.2.0 from 2026-08-26), which is what the ecosystem already declares.
  • scripts/sync-peer-range.mjs understands the ||-joined clause form: parseRangeSet/formatRangeSet were added and rangeStatus/targetRange now compare clause sets instead of a single floor/upper pair. The single-clause parseRange keeps its old signature, so existing callers and tests are unaffected.
  • The release workflow now creates the GitHub Release itself, with the body taken from this version's CHANGELOG section. Until now a v* tag published to npm and stopped there, so every Release page had to be created by hand afterwards.
  • Pin the @deepseek-ai/dsh-* dev/test dependencies to the published 0.1.5-rc.2 line; the monthly Compat workflow now runs against 0.1.5-rc.2. The peer range >=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 is unchanged, so no supported host line is dropped.

Fixed

  • verifyReadmeLanguages now expects README-<lang>.md. It built the dotted name from a template, so a textual rename cannot see it — this is the one place in the fleet that constructs the filename dynamically, and its own test is what caught the mismatch. Nothing consumes this verifier yet (each repo carries its own verify-readmes copy), so the change stays inside this repo.

v0.1.8

Choose a tag to compare

@PerryLink PerryLink released this 10 Sep 06:46

[0.1.8] - 2026-09-10

Changed

  • Pin the @deepseek-ai/dsh-* dev/test dependencies to the published 0.1.5-rc.1 line and record 0.1.5-rc.1 in dshWorkshop.compatibility.dshVersions; the monthly Compat workflow now runs against 0.1.5-rc.1. The peer range >=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 is unchanged, so no supported host line is dropped.

Docs

  • Refresh the five-language README compatibility baseline to dsh-v0.1.5-rc.1 (verified 2026-09-10).

v0.1.7

Choose a tag to compare

@PerryLink PerryLink released this 09 Sep 14:58

[0.1.7] - 2026-09-09

Changed

  • Align the @deepseek-ai/dsh-* peer ranges to >=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 and pin the dev/test dependencies to the published 0.1.5-alpha.1 line: adaptation to DeepSeek Harness dsh-v0.1.5-alpha.1 (session format V3, ctx.agent removal, Inbox type-only interface); runtime behavior is unchanged for every supported host line.
  • Record 0.1.5-alpha.1 in dshWorkshop.compatibility.dshVersions.

Docs

  • Refresh the five-language README compatibility baseline to dsh-v0.1.5-alpha.1 (verified 2026-09-09).

v0.1.6

Choose a tag to compare

@PerryLink PerryLink released this 07 Sep 10:54

[0.1.6] - 2026-09-07

Fixed

  • Align the @deepseek-ai/dsh-* peer ranges to >=0.1.2-rc.1 <0.2.0: the older >=0.1.0-rc.8 <0.2.0 band resolved to only the 0.1.0-rc.8 prerelease under registry-driven resolution and broke fresh tarball installs; no behavior change.

Docs

  • Refresh the five-language README support-version wording: the verified GitHub tag dsh-v0.1.3-alpha.1 now leads the compatibility claim, while npm 0.1.2-rc.1 stays the published dependency-pin line (peers >=0.1.2-rc.1 <0.2.0); no behavior change.

v0.1.5

Choose a tag to compare

@PerryLink PerryLink released this 04 Sep 14:43

Generated release notes.

v0.1.4

Choose a tag to compare

@PerryLink PerryLink released this 02 Sep 13:39

[0.1.4] - 2026-09-02

Changed

  • Refresh the five-language READMEs, AGENTS.md, and the session-event gate JSDoc to the 0.1.2-alpha.5 narrative (gate behavior unchanged: KNOWN_SESSION_EVENT_TYPES still holds 51 types, Session.append still cannot stamp the ignorable marker, and the Session.events getter rename to snapshotEvents() does not touch this kit).

v0.1.3

Choose a tag to compare

@PerryLink PerryLink released this 01 Sep 17:11

Full Changelog: v0.1.2...v0.1.3

v0.1.0

Choose a tag to compare

@PerryLink PerryLink released this 30 Aug 13:13