Finding / deepseek-harness

2026-10-24-deepseek-harness-published-channel-selectors-disagree-and-the-harness-remains-entirely-prerelease

Published channel selectors disagree and the harness remains entirely prerelease. At 2026-10-24T10:33:49Z CLI npm selectors remain latest=0.2.1-rc.2, next=0.2.1-rc.3, alpha=0.2.1-alpha.5; all 37 versions are prereleases. At 10:34:37Z all 32 GitHub release objects remain prereleases, newest rc.3 published 2026-10-23T15:26:39Z. The independent 10:13:13Z to 10:13:16Z Desktop feed reads give rc.3 for ARM and Windows Nightly but rc.1 for Intel; stable aliases return 404. Python remains 0.2.1rc2 at the 10:13:16Z metadata read. The SDK client’s latest remains 0.0.1-rc.1 at 10:17:11Z to 10:17:13Z; match its explicit version to the selected runtime. CLI manifests retain ranged vendor dependencies. No stable harness exists, and independently stable DeepSeek Cordis packages do not change that.

Channel: preview-or-beta. Half: both. Date: 2026-10-24.

Operator consequence: For a disposable default-channel trial select @deepseek-ai/dsh@0.2.1-rc.2 explicitly, resolve and inspect its dependency lock before running dsh web; use npx @deepseek-ai/dsh@0.2.1-rc.3 web only when deliberately selecting the newer preview. Match SDK versions explicitly and inspect the actual Desktop platform feed before relying on rc.2 or rc.3 features. These commands were not executed. A version pin alone does not freeze the complete install graph or establish production suitability.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-deepseek-harness-published-channel-selectors-disagree-and-the-harness-remains-entirely-prerelease

Profile citations

Source links

Primary links, including exact changelog lines when available.