Skip to content

v0.1.4 — Better development guidance and compatibility checks

Latest

Choose a tag to compare

@builtin-pb builtin-pb released this 19 Sep 08:07

dsh-developer 0.1.4 brings clearer development guidance and stronger checks against upstream DSH changes.

  • Turn vague ideas into useful plugins. Shared guidance for DeepSeek and GPT now makes intent, design tradeoffs, maintainable implementation and independent behavior checks explicit. Essential guidance stays in the main skill, including during repairs.
  • Catch API drift before running. DSH-facing JavaScript is checked against upstream TypeScript declarations, including the actual dependency graph of each tested runtime. Installation still needs no build step.
  • Navigate and set up projects more smoothly. Clearer installed-package lookups, missing-build hints, corrected example paths and Windows installer handling reduce common development friction.
  • Trust verification results more. Native cases reject numeric values that JSON transport would silently change. Source audits handle growing files within fixed budgets, recognize directly audited context helpers, and cover more loader and assignment cases.

Reviewed runtimes: DSH 0.1.5-rc.2 and 0.1.6-alpha.2. Local validation passed 890 tests, with 45 optional integrations skipped. The release archive passed native package-identity, source-audit and knowledge checks in both headless and Web profiles on both runtimes. Browser opening was disabled.

Install or update in DSH Web:

dsh plugin --profile web add 'github:builtin-pb/dsh-developer#v0.1.4' --ignore-scripts

Restart DSH after installation. The attached archive and SHA256SUMS provide the same release without build scripts.

All 18 CI jobs passed on both the release commit and the v0.1.4 tag, including Windows, macOS and Ubuntu checks and native development against npm latest, next and alpha.

Post-publication checks: the public Git tag and archive URL both installed version 0.1.4 into fresh Web profiles with scripts disabled. All 137 packaged files matched the tested artifact. Each publicly installed CLI passed the three native Web cases; all disposable profiles were removed. The downloaded archive matched the published SHA256SUMS and tested bytes.