Evidence record / deepseek-harness
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-09-21-deepseek-harness-still-no-non-prerelease-tag-the-project-split-into-an-rc-line-and-an-alpha-line-and-npm
Still no non-prerelease tag; the project split into an rc line and an alpha line, and npm latest moved to 0.1.5-rc.2 by hand. There are now two preview streams: rc builds (0.1.5-rc.2 is the newest in window) and faster alpha builds (0.1.6-alpha.2), each with its own dist-tag. latest was promoted to 0.1.5-rc.2 outside the publish script, so the registry does not record when. At window close, applying the script’s rules to publish times, next resolved to 0.1.5-rc.2 and alpha to 0.1.6-alpha.2 (inferred, not observed on 2026-09-21).
Channel: preview-or-beta. Half: neither (channel). Date: 2026-08-21 to 2026-09-17.
Operator consequence: npx @deepseek-ai/dsh web installs 0.1.5-rc.2, still a release candidate. Pin @0.1.5-rc.2 explicitly; do not float on @alpha, which carries the telemetry default in section 4. Nothing here is a stable channel. Re-check next window for a non-prerelease tag and for who moves latest.
Receipt
Finding metadata
Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0
Finding ID: 2026-09-21-deepseek-harness-still-no-non-prerelease-tag-the-project-split-into-an-rc-line-and-an-alpha-line-and-npm
Profile citations
- deepseek-harness / claim / still-prerelease
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact