Current release state
As of the August 26 registry snapshot, the latest official GitHub release and the npm latest dist-tag both point to 0.1.1-rc.2. No rc.3 release was present when this snapshot was collected.
| Signal | Previous registry snapshot | Current snapshot |
|---|---|---|
| GitHub release | 0.1.0-rc.8 | 0.1.1-rc.2 |
| npm latest | 0.1.0-rc.7 | 0.1.1-rc.2 |
| Compatibility evidence | Maintainer documentation only | Exact artifact × host × Node × surface × time |
What changed in the evidence boundary
The important ecosystem change is not another directory count. Upstream Radar now re-runs published artifacts in disposable environments, while dsh-compat-guard proposes a pre-upgrade gate, lockfile, backup, and rollback flow. These are community tools, not official DSH guarantees, but they establish a stronger standard for claims.
- A historical pass never applies to a newly published plugin artifact.
- A Headless pass does not automatically cover Web or TUI.
- Needs review is neither compatible nor incompatible.
- A current cell becomes stale after its published recheck deadline.
Newly reported fault lines after rc.2
Two August 25 discussions add failure intelligence beyond the release notes. One community reproduction links an undefined prepare crash to a second dsh-tools module copy. Another report and follow-up reproduction connect a plugin-origin tool hang to renderer output shape. Neither is an official released fix.
| Signal | Affected boundary | Evidence status |
|---|---|---|
| undefined (reading 'prepare') | Headless tool runtime and duplicate module identity | Community reproduction; discussion remains unanswered |
| Plugin-origin tool never settles | Code Mode renderer output and tool binding settlement | Community reproduction and source-pinned proposed fix |
| Pure text works, tool call fails | Tool path rather than model/provider path | Useful diagnostic control, not a root-cause verdict |
Release-diff rule for plugin users
Before changing the host, inventory exact plugin versions, preserve the current DSH home, and look for a compatibility cell matching the target release and the surface you use. If any required plugin is needs-review, stale, expired, update-pending, or not observed, stop treating the upgrade as routine.
DeepSeek Harness is in developer preview. Recheck official documentation and plugin evidence when the host version changes.
Sources and evidence
Official documentation and community evidence are labeled separately in the source pages and in this article.