Repository navigation
Pin the DSH harness to 0.2.2-rc.2 - #29
Conversation
The dsh-skill peer stays ^0.2.1-rc.2. DSH still accepts that range with includePrerelease, and a fresh profile mount listed the pstack skills. Co-authored-by: Kaitian Xie <caelaxie@users.noreply.github.com>
|
Harness proof against Version
|
caelaxie
left a comment
There was a problem hiding this comment.
verdict: pass.
- ci-only: one-line dsh pin bump 0.2.2-rc.1 -> 0.2.2-rc.2 in ci.yml, no plugin content touched.
- harness proof on the pr:
dsh plugin --profile ci add, mount in--dump-config, profile boot lists 61 pstack skills incl. deslop, control-cli, control-ui. - ci green on 20b2ec8 (validate + mount bundle in dsh).
- peer range left alone is fine under includePrerelease.
- no open issue to link.
squash-merging.
Summary
Pins the harness CI job to exactly
@deepseek-ai/dsh@0.2.2-rc.2so this profile bundle is proven on the currentnextrelease candidate (published 2026-11-12T02:16:12Z).latestis still0.2.2-rc.1.alphais0.2.2-alpha.3.The
@deepseek-ai/dsh-skillpeer stays^0.2.1-rc.2. DSH decides compatibility withsemver.satisfies(runtimeVersion, range, { includePrerelease: true })against the app-boot version (0.2.2-rc.2), and only@deepseek-ai/dsh/@deepseek-ai/dsh-*peers count. With prereleases included,0.2.2-rc.2satisfies^0.2.1-rc.2. The default semver check does not. A freshdsh plugin --profile ci addof this checkout did not skip or warn aboutdsh-pstack, and the profile booted the bundle, so the peer was not widened.@deepseek-ai/cordis@^4.0.1already includes cordis4.1.0.Release notes
From the
v0.2.2-rc.1section ofdocs/upgrade-guide/README.mdin the@deepseek-ai/dsh@0.2.2-rc.2tarball (the rc.1 → rc.2 changelog). There is nov0.2.2-rc.2section. Nothing there is a plugin-peer or third-party bundle-loading break. This package does not call the changed APIs:BundleInfo.updatereplacesBundleInfo.updatable. Install remainsdsh plugin --profile <name> add <checkout>.dsh-doc. That is inside DSH, not this bundle.The only non-version dependency change in the CLI package is adding
@deepseek-ai/dsh-cua-bundle@0.2.2-rc.2and removing@deepseek-ai/dsh-experimental-agent-team-profile. The runtime depends on@deepseek-ai/dsh-skill@0.2.2-rc.2..github/prove-dsh-profile.mjsstill importslib/profile-boot.jsandloadLayeredEnvfrom@deepseek-ai/dsh-app-boot, and both resolved.engines.nodeis still>=24.9.0. On Node v22.23.4,npm install -gwarnsEBADENGINEand still installs.dsh --versionprints0.2.2-rc.2, and the harness proof passes. This job stays on Node 22.Test
npm testpassed. Harness transcript is on the PR.