BREAKING CHANGES

dsh breaking changes: every release, dated

Latest v0.2.0-rc.2 released 2026-09-29 · 29 releases tracked · 28 still under review · page checked 2026-09-30

dsh is in developer preview and the maintainers have been upfront about compatibility risk. Every release is listed here with its date. Where a review is finished you get a verdict; where it isn't, we say so rather than guess.

"DeepSeek Harness is currently in developer preview and is iterating rapidly. THERE WILL BE COMPATIBILITY-BREAKING CHANGES."— deepseek-ai/deepseek-harness official README, August 2026
30-SECOND CHECK

Before you upgrade

Step 1
Run dsh --version and note what you're on.
Step 2
Find your target version in the timeline below and check for a BREAKING tag.
Step 3
If it's breaking, check the audit reports for your installed plugins before upgrading.

Release timeline

from npm registry · updated daily · "In review" = we haven't finished verifying the changes, so no verdict yet
v0.2.0-rc.2In review released 2026-09-29 · latest

Current latest release on npm. Change review in progress — we do not label a release BREAKING or safe until the review is done. Before upgrading, see the official release notes.

v0.2.0-rc.1In review released 2026-09-28

Change review in progress.

v0.1.7-rc.2In review released 2026-09-24

Change review in progress.

v0.1.7-rc.1In review released 2026-09-23

Change review in progress.

v0.1.7-alpha.2In review released 2026-09-22

Change review in progress.

v0.1.7-alpha.1In review released 2026-09-22

Change review in progress.

v0.1.5-rc.3In review released 2026-09-22

Change review in progress.

v0.1.6-alpha.2In review released 2026-09-17

Change review in progress.

v0.1.6-alpha.1In review released 2026-09-15

Change review in progress.

v0.1.5-rc.2In review released 2026-09-10

Change review in progress.

v0.1.5-rc.1In review released 2026-09-10

Change review in progress.

v0.1.5-alpha.2In review released 2026-09-09

Change review in progress.

v0.1.5-alpha.1In review released 2026-09-08

Change review in progress.

v0.1.3-alpha.2In review released 2026-09-07

Change review in progress.

v0.1.2-rc.1In review released 2026-09-03

Change review in progress.

v0.1.2-alpha.5In review released 2026-09-02

Change review in progress.

v0.1.2-alpha.4In review released 2026-09-01

Change review in progress.

v0.1.2-alpha.3In review released 2026-08-31

Change review in progress.

v0.1.2-alpha.2In review released 2026-08-30

Change review in progress.

v0.1.1-rc.2In review released 2026-08-21

Change review in progress.

v0.1.1-rc.1In review released 2026-08-21

Jump from the 0.1.0 line to 0.1.1. Version-line jumps usually come with interface changes — until the review is done, treat this as potentially incompatible and check the maintenance status of your installed plugins first.

v0.1.0-rc.8In review released 2026-08-19

Change review in progress.

v0.1.0-rc.7In review released 2026-08-17

Change review in progress.

v0.1.0-rc.6In review released 2026-08-13

Change review in progress.

v0.1.0-rc.3In review released 2026-08-13

Change review in progress.

v0.1.0-rc.2In review released 2026-08-13

Jump from the 0.0.x line to 0.1.0. Version-line jumps usually come with interface changes — until the review is done, treat this as potentially incompatible and check the maintenance status of your installed plugins first.

v0.0.1-rc.5In review released 2026-08-12

Change review in progress.

v0.0.1-rc.2In review released 2026-08-11

Change review in progress.

v0.0.1-rc.1Non-breaking released 2026-08-10

First public release on npm (start of the developer preview).

Verified install & migration pitfalls

from the official docs and real plugin repos

Packages without dsh.bundle don't activate

Straight from the official docs: such packages "still install, but only as plain dependencies … activating no layer". Every affected plugin in the audit hall is flagged red.

Use the official install command

The only current flow: dsh plugin --profile <name> add <npm-package | github:owner/repo | link:local-path>. Other install forms from early write-ups no longer exist in the docs.

Restart dsh after installing

Activation happens on restart. If a plugin seems dead right after install, restart before debugging.

How we track this: npm releases and official repo activity are pulled automatically every day. New versions start as "In review"; only after a human verifies the changes do we tag them BREAKING or Non-breaking, and every listed plugin is re-audited the same day. No finished review, no verdict.