Repository navigation
Replies: 1 comment
|
补充两点数据。我们是从下游 CI(不是 npm quickstart)撞上的,结论与你一致,这里只补两处新证据。 1. 这个包像是被 rc.3 这批漏发了,而不是「还没发到」 发布时刻(取自各版本 manifest 的
该批发布后各包的
2. 影响面不止 任何把 CLI 装进 CI 做集成测试的下游仓库同样全红——我们这边一个桌面端仓库的 PR 门禁已经完全装不上它。空目录、无 manifest 的最小复现: mkdir /tmp/probe && cd /tmp/probe && npm init -y
npm install @deepseek-ai/dsh@0.1.5-rc.2 --dry-run
# npm error code ETARGET
# npm error notarget No matching version found for
# @deepseek-ai/dsh-client-ui-sidebar-documentpreview@^0.1.5-rc.3.在补发完整的 rc.3 集合之前,下游只能把整个 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
Following the official README's npm quickstart,
npx @deepseek-ai/dsh webfails before the Web UI starts:Official instructions: https://github.com/deepseek-ai/deepseek-harness#run-from-npm
Environment
Reproduction
Run the documented command in a directory without a package manifest or dependency overrides:
Expected: installation succeeds and the Web UI starts.
Actual: npm exits with ETARGET.
Registry evidence / likely cause
At the time of reporting:
@deepseek-ai/dsh: latest =0.1.5-rc.2, next =0.1.5-rc.3.@deepseek-ai/dsh@0.1.5-rc.2depends on@deepseek-ai/dsh-web-app@^0.1.5-rc.2.0.1.5-rc.3.@deepseek-ai/dsh-web-app@0.1.5-rc.3depends on@deepseek-ai/dsh-client-ui-sidebar-documentpreview@^0.1.5-rc.3.0.1.5-rc.1and0.1.5-rc.2, but no0.1.5-rc.3. Its newer published versions are prereleases of different release tuples and do not satisfy this range.These commands expose the mismatch:
Verified workaround
A separate local installation with the CLI and its transitive
@deepseek-ai/dsh*packages (208 DeepSeek packages total) pinned to exactly0.1.5-rc.2using npm overrides installs successfully. After the dependency install scripts run,dsh --versionreturns0.1.5-rc.2, and the authenticated Web UI loads on localhost. Native PTY command execution also succeeds.Pinning only the top-level CLI would still leave its caret dependency ranges able to resolve to rc.3.
Suggested fix
Please publish a complete compatible package set for the affected release (including the missing document-preview package), and consider exact internal prerelease dependency versions plus a clean-registry installation smoke test before promoting releases. The documented latest install should not resolve to an incomplete next release.
Related reports
I searched Discussions for ETARGET. #6168, #2991, and #3461 describe similar missing-package publication failures in earlier releases; this report concerns the current rc.2 → rc.3 document-preview dependency mismatch.
All reactions