feat: bump DSH runtime to 0.2.0-rc.1 - #105
Merged
Merged
Conversation
Align bridge peerDependencies and workspace pins with DSH 0.2.0-rc.1 so the plugin passes compatibility checks. Adapt MessageSource and agent lifecycle hooks for the 0.2 API surface.
…gnature Probing open.length fell back to the 0.1.5 three-arg call under Cordis wrappers, mapping AbortSignal onto uplink and leaving signal undefined so $events failed after hello.ok with stream-failed/1011.
…=== 3 Always calling the dsh 0.2 five-arg form broke composition tests whose gateway open(endpoint, payload, signal) treated the empty uplink as AbortSignal. Only fall back to three-arg when arity is exactly 3; arity 0 wrappers still use five-arg so production Cordis hosts do not regress to stream-failed/1011.
… kind Bring back dsh-ptc-runtime, dsh-llm-deepseek, and dsh-deepseek-account so the web profile can activate ptcRuntime/workflowEngine for session.create. Update the smoke assertion to the 0.2 producer kind `browser-context`.
zzalancelot
added a commit
to zzalancelot/dsh-browser
that referenced
this pull request
Sep 30, 2026
…sions Bring maintain up to the PR omdsh-dev#105 runtime fixes: open Host wireStream with the five-arg 0.2 signature (arity-3 stubs only), restore ptc/llm/account smoke deps, and align smoke with browser-context. Bump dsh-browser 0.1.5, bridge 0.0.8, and extension 0.1.6.
4 tasks done
chintoleung
approved these changes
Sep 30, 2026
chintoleung
left a comment
chintoleung
left a comment
Contributor
There was a problem hiding this comment.
Verified locally on a fresh checkout of this branch (macOS arm64, Node 24.21, pnpm 11.7.0):
pnpm run check:runtime, typecheck (bridge + extension), bridge tests 142/142 ✓pnpm run test:smoke✓ — with one heads-up for dev checkouts: a stalelib/build fails smoke withstream-failed: signals[0] is not of type AbortSignal(the pre-0.2 bundle callswireStream.openwith the 3-arg form, so the AbortSignal lands in the uplink slot).pnpm --filter @yuxianglin/dsh-bridge-browser run buildbefore smoke avoids it.- Your unchecked manual box, covered indirectly: full
dsh webhost boot with the pinned runtime, stable bridge WS connect,hello.okwith nostream-failed/1011, and the smoke client exercises the extension protocol path end-to-end. - One non-blocking nit:
injectLatestSnapshotno longer recognizes 0.1.7-eraplugin:@yuxianglin/dsh-bridge-browserpending snapshots (that unit test was removed), so an old deferred session may keep one stale snapshot in its inbox. Harmless, but worth a line in release notes.
Also confirmed the rc.1→rc.2 delta is desktop-only, and sent #106 as a stacked re-pin to 0.2.0-rc.2 (verified green on rc.2: bridge 142/142, extension 388/388, smoke against the rc.2 runtime).
Lum1104
pushed a commit
that referenced
this pull request
Oct 1, 2026
Follow-up to #105: 0.2.0-rc.2 (2026-09-29) contains desktop-app fixes only; no bridge-facing changes. Re-pin workspace deps and bridge peers/devDeps from 0.2.0-rc.1 to 0.2.0-rc.2 and refresh pnpm-lock.yaml. Verified locally: check:runtime, typecheck, bridge 142/142, extension 388/388, and test:smoke green against the pinned 0.2.0-rc.2 runtime (peer gate accepts the bundle; hello.ok without stream-failed; V2 migration and browser-context V4 snapshots persist).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@deepseek-ai/dsh-*peers withsemver.satisfies. The bridge still declared^0.1.5-rc.2(upper bound<0.2.0), so it failed the compatibility check and would not load.mainonly. It pins the workspace and@yuxianglin/dsh-bridge-browserpeers/devDeps to exact0.2.0-rc.1(bridge0.0.7), with minimal 0.2 API adaptations (MessageSource→browser-context,agent/created), so the plugin passes the check and runs on 0.2.wireStream.openfor the dsh 0.2 five-arg signature (Cordis wrappers must not fall back to the 0.1.5 three-arg form), restores smoke runtime deps (dsh-ptc-runtime/dsh-llm-deepseek/dsh-deepseek-account), and updates the smoke assertion tobrowser-context.Fixes #104
Test plan
pnpm --filter @yuxianglin/dsh-bridge-browser testpnpm run test:smokedsh webon 0.2.0-rc.1 and confirm stable bridge connect (nostream-failed/ 1011 afterhello.ok)