DSH 0.2.2-rc.2 Reaches npm on the next Tag (Nov 12, 2026)

The question the rc.2 article left open now has a dated answer: DSH 0.2.2-rc.2: Worktree Review, Named SubAgents, DeepSeek Search by Default (Nov 11, 2026) recorded, per that day’s registry read, that @deepseek-ai/dsh listed no 0.2.2-rc.2 version — the version endpoint answered 404, and the dist-tags latest and next both read rc.1. Per this site’s registry read of 2026-11-12, 0.2.2-rc.2 published at 02:16:12 UTC that day and took over the next tag; latest still reads rc.1, stamped 09:20:32 UTC on 2026-11-04, and alpha reads 0.2.2-alpha.3.

The timing ran the other way

Per the releases API, the rc.2 GitHub release was published at 11:33:06 UTC on 2026-11-11, so the npm publish followed the release page by fourteen hours and forty-three minutes. Every earlier 0.2.2 version on npm ran npm-first: rc.1’s npm stamp (09:20:32 UTC on 2026-11-04) preceded its GitHub page (13:07:14 UTC) by three hours and forty-six minutes, alpha.3’s npm stamp (07:48:26 UTC on 2026-11-03) preceded its page (07:56:48 UTC) by eight minutes, and alpha.2’s npm stamp (19:10:28 UTC on 2026-10-27) preceded its page (02:50:54 UTC on 2026-10-28) by seven hours and forty minutes. rc.2 is the first 0.2.2 publish where npm followed the release page.

Corroborated from the TUI side

The release notes of dsh-TUI v0.20.0, published at 16:31 UTC on 2026-11-12, state the same registry state in their upgrade section: npm latest is still 0.2.2-rc.1, 0.2.2-rc.2 rides the next tag, and the in-app /update picks the highest published version within the peer range, so it aligns the dsh engine to 0.2.2-rc.2 — dsh-TUI 0.20.0: Validation Line at 0.2.2-rc.2, Notifications Cover the Waiting States (Nov 12, 2026) covers that release.

What the notes on either side do not say is when latest flips, and this article does not forecast it; the state above is a dated registry read, and any later state needs a fresh one.

The timing ran the other way

Corroborated from the TUI side

More in this series