Repository navigation
Replies: 2 comments
|
补一份独立复核(2026-11-03T08:44Z,直连 registry 逐个查询,不经本机 npm 缓存):主结论属实,alpha 渠道当前对所有人不可安装,失败原因就是这一个叶子包。 复核数据
一处建议修正:91→90 不能当作漏发信号本文把"依赖数 91 掉到 90、
另外两条可确认的事实
顺带补一处:现有 用户侧绕法(已实测) |
已修复:
|
|
补一份独立复核(2026-11-03T08:44Z,直连 registry 逐个查询,不经本机 npm 缓存):主结论属实,alpha 渠道当前对所有人不可安装,失败原因就是这一个叶子包。 复核数据
一处建议修正:91→90 不能当作漏发信号本文把"依赖数 91 掉到 90、
另外两条可确认的事实
顺带补一处:现有 用户侧绕法(已实测) |
已修复:
|
Uh oh!
There was an error while loading. Please reload this page.
TL;DR —
@deepseek-ai/dsh@0.2.2-alpha.3cannot be installed. It pins@deepseek-ai/dsh-tool-pwsh-persistent@0.2.2-alpha.3, a leaf that was never published (that package'salphatag still points at0.2.2-alpha.2). A single missing sibling hard-fails the wholealphachannel.Reproduction
Registry evidence (checked 2026-11-03T08:10Z)
@deepseek-ai/dsh@deepseek-ai/dsh-tool-pwsh-persistent0.2.2-alpha.3does not appear in theversionsmap ofdsh-tool-pwsh-persistentat all, and itsdist-tags.alphais still0.2.2-alpha.2.Full dependency audit (every declared dependency of the monolith resolved against the registry):
alpha@deepseek-ai/dsh-tool-pwsh-persistent@0.2.2-alpha.3latest/nextTwo additional signals that the alpha.3 wave was only partially published:
0.2.2-alpha.2and0.2.2-alpha.3:@deepseek-ai/dsh-cua-bundleis no longer declared at all;dsh-tool-pwsh-persistentwas last published 7 days earlier, in the alpha.2 wave.Impact
Following the alpha channel is currently impossible for everyone:
npm i -g @deepseek-ai/dsh@alphaandnpx @deepseek-ai/dsh@alphaboth abort at resolution time, before anything is written to disk.latest/next(0.2.1-rc.5) are unaffected.Suggested fix (any one of these unblocks the channel)
@deepseek-ai/dsh-tool-pwsh-persistent@0.2.2-alpha.3, and move itsalphatag to that version. Nothing else in the wave is missing.@deepseek-ai/dsh'salphadist-tag at0.2.2-alpha.2(which audits clean) until the wave finishes.~/^ranges instead of exact pins, so a partially-published wave resolves to the nearest published sibling instead of failing the whole install. This is the third release in a row where an exact pin on an unpublished sibling broke the channel (see below).Workaround for users, right now
Prior occurrences of the same failure mode
0.1.5-rc.2/rc.3wave shipped withoutdsh-client-ui-sidebar-documentpreview@0.1.5-rc.30.2.0-rc.2shipped withoutdsh-client-ui-settings-account@0.2.0-rc.20.1.5-rc.1shipped withoutdsh-util-crypto@0.1.5-rc.1So the underlying problem is the release pipeline allowing the monolith to be published before every sibling leaf is on the registry, not this one version. A pre-publish gate that asserts "every exact dependency of the new version resolves on the registry" would catch all of the above before the tag moves.
(Unrelated, but it appears in the same session output and confuses triage:
npm error config prefix cannot be changed from project config: ~/.npmrcis a local npmrc issue, not part of this bug.)All reactions