From 39539a7d06f97b7809872e7f2576732ec52a3447 Mon Sep 17 00:00:00 2001 From: huangruiteng <14976749+huangruiteng@users.noreply.github.com> Date: Tue, 15 Sep 2026 12:30:48 +0800 Subject: [PATCH] chore(dsh): pin the managed dsh host to the latest released SDK The `deepseek-harness` extra now pins `deepseek-harness-sdk==0.1.5rc1` and its bundled `deepseek-harness-runtime-bin==0.1.5rc1`, the newest release channel published for dsh (PyPI for the wheels, `latest` on npm for `@deepseek-ai/dsh`). The Python client surface is unchanged from the previously pinned `0.1.2a3`; the bump moves the bundled dsh runtime behind the managed host. Validation (hermetic, local mock LLM, no provider call): - `examples/loopx-turn-dsh-real-e2e-smoke.py --host generic-cli` and `--host dsh` both pass against 0.1.2a3 (control) and 0.1.5rc1. - `tests/test_dsh_goal_mode.py` (55 passed), `examples/dsh-turn-host-adapter-smoke.py` (11 checks), `examples/loopx-turn-dsh-e2e-smoke.py`, `examples/loopx-turn-dsh-builtin-host-e2e-smoke.py` all pass. Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com> --- docs/integrations/deepseek-harness-connector.md | 10 +++++++++- loopx/dsh_goal_mode/README.md | 2 +- pyproject.toml | 2 +- 3 files changed, 11 insertions(+), 3 deletions(-) diff --git a/docs/integrations/deepseek-harness-connector.md b/docs/integrations/deepseek-harness-connector.md index 1b73bf7a6b..e22f82d05c 100644 --- a/docs/integrations/deepseek-harness-connector.md +++ b/docs/integrations/deepseek-harness-connector.md @@ -29,7 +29,7 @@ LoopX quota should-run - A `deepseek-harness` agent type in LoopX onboarding so users can request the exact host instead of the generic `other-agent`. - Optional dependency `loopx[deepseek-harness]` for the validated - `deepseek-harness-sdk==0.1.2a3` Python client. + `deepseek-harness-sdk==0.1.5rc1` Python client. ## Install @@ -39,6 +39,14 @@ Install LoopX's optional DeepSeek Harness extra: python -m pip install 'loopx[deepseek-harness]' ``` +The pin tracks the newest published dsh release channel rather than an +unreleased tag: `0.1.5rc1` for the PyPI SDK/runtime wheels and `0.1.5-rc.1` for +the npm `@deepseek-ai/dsh` `latest` tag. Upstream also publishes newer +`next`/`alpha` tags that are not the released channel. This release keeps the +Python client surface of the previously pinned `0.1.2a3` and moves the bundled +dsh runtime; LoopX selects the SDK's default `sdk` profile unless the operator +supplies an explicit cordis composition. + The DeepSeek Harness SDK spawns the bundled `dsh-jsonrpc-agent` runtime. It uses the explicit adapter configuration plus normal provider environment variables: diff --git a/loopx/dsh_goal_mode/README.md b/loopx/dsh_goal_mode/README.md index ec8a63e2ce..a775df8d55 100644 --- a/loopx/dsh_goal_mode/README.md +++ b/loopx/dsh_goal_mode/README.md @@ -86,7 +86,7 @@ contract failure instead of collapsing into `unknown`. ## Requirements - Optional dependency group `loopx[deepseek-harness]`, currently pinned to the - validated `deepseek-harness-sdk==0.1.2a3` API, or a compatible runner via + validated `deepseek-harness-sdk==0.1.5rc1` API, or a compatible runner via `--dsh-runner`. - A dsh `cordis.yml` plus any `DEEPSEEK_API_KEY` / `DEEPSEEK_BASE_URL` settings for the real runtime. diff --git a/pyproject.toml b/pyproject.toml index 37be35eef9..f535f75b62 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -22,7 +22,7 @@ Changelog = "https://github.com/huangruiteng/loopx/releases" [project.optional-dependencies] deepseek-harness = [ - "deepseek-harness-sdk==0.1.2a3", + "deepseek-harness-sdk==0.1.5rc1", ] test = [ "jsonschema>=4.23,<5",