DeepSeek Harness v0.1.2-alpha.5
DeepSeek Harness v0.1.2-alpha.5: npm Release Status
- Author
- DeepSeekAgent.io Editorial Team
- Published
- Updated
On September 2, 2026, @deepseek-ai/[email protected] was published to npm and the alpha dist-tag moved to that version. It is a new pre-release package after alpha.4. At the time this article was checked, however, the official GitHub repository did not yet expose a matching dsh-v0.1.2-alpha.5 tag or Release notes.
This update therefore records only facts confirmed by the official package registry. It does not infer features from a version number. Users who need a concrete changelog should wait for the matching GitHub Release or source tag before deciding to upgrade.
The short version
Alpha.5 is the current npm alpha build, but its release notes and source tag had not yet appeared when checked. Pin it in an isolated environment for compatibility testing; do not update an important environment merely because the moving alpha tag advanced.
What is confirmed
As of September 2, 2026 at 08:38 UTC:
| Check | Status |
|---|---|
| Exact npm version | @deepseek-ai/[email protected] published |
npm alpha dist-tag | Points to 0.1.2-alpha.5 |
npm latest | Still 0.1.1-rc.2 |
npm next | Still 0.1.1-rc.2 |
| npm publication time | September 2, 2026 at 08:38:34 UTC |
| GitHub alpha.5 tag | Not present when checked |
| GitHub alpha.5 Release | Not present when checked |
The package is installable, but commits after alpha.4 cannot automatically be treated as alpha.5's official changelog. npm publication and GitHub Release creation may have a short timing gap, and documentation may follow later.
How to pin alpha.5 for testing
npx @deepseek-ai/[email protected] web
Avoid relying on the moving @alpha tag in an important environment:
# This tag can point to a later build in the future
npx @deepseek-ai/dsh@alpha web
An exact version makes errors reproducible, enables a clean alpha.4 comparison, and gives plugin authors a useful compatibility report.
What cannot yet be confirmed
Without alpha.5 Release notes or a source tag, it is not yet safe to claim:
- Which features or fixes alpha.5 contains.
- Whether it adds another breaking Session, Plugin, or Agent API change.
- Whether it fixes any specific post-alpha.4 issue from the master branch.
- Whether later GitHub notes will include an additional migration step.
A higher version number establishes release order; it does not replace an itemized changelog.
What to do before upgrading
- Pin the currently working version and back up Sessions and configuration that matter.
- Wait for the official alpha.5 tag or Release notes and review the complete scope.
- Test with a separate
$DSH_HOME, Profile, and disposable workspace. - For plugins, run compilation, unit tests, and real Session-resume tests.
- When coming from alpha.2 or earlier, also account for alpha.3's SQLite removal and alpha.4's Session API migration.
The alpha.3-to-alpha.5 sequence
| Version | Publicly documented focus |
|---|---|
| alpha.3 | Long-chat and image fixes; optional SQLite Session backend removed |
| alpha.4 | Two-way parent-child Agent messaging; broader web_fetch defaults; Session API changes |
| alpha.5 | npm package and alpha tag published; detailed Release notes pending |
The sequence matters. Even if alpha.5 is the final target, its upgrade path can still inherit migration effects introduced by alpha.3 and alpha.4.
Related reading
- DeepSeek Harness v0.1.2-alpha.3: Long Conversations and SQLite Removal
- DeepSeek Harness v0.1.2-alpha.4: Two-Way Agent Messaging and Session API Changes
- DeepSeek Harness v0.1.2-alpha.2: Reconnects, Presets and Token Stats
Frequently asked questions
Has alpha.5 been released?
Yes. @deepseek-ai/[email protected] is published on npm and the alpha dist-tag points to it. A matching GitHub tag and Release notes were not present when this article was checked.
Is alpha.5 stable?
No. npm's latest and next tags still point to 0.1.1-rc.2; alpha.5 is explicitly on the pre-release channel.
Should I upgrade from alpha.4 now?
Unless you have a specific reason, wait for the official changelog. If you must test it, pin 0.1.2-alpha.5 and use an isolated environment.