From 1d0fe354855a6efa25364a55624c88969b14e3bf Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 6 Nov 2026 06:21:38 +0000 Subject: [PATCH] chore(release): prepare v0.2.4 --- .../0.2.4}/dsh-0.2.2-rc1-realignment.md | 0 CHANGELOG.md | 7 +++++++ Cargo.lock | 2 +- Cargo.toml | 2 +- 4 files changed, 9 insertions(+), 2 deletions(-) rename .changes/{unreleased => archive/0.2.4}/dsh-0.2.2-rc1-realignment.md (100%) diff --git a/.changes/unreleased/dsh-0.2.2-rc1-realignment.md b/.changes/archive/0.2.4/dsh-0.2.2-rc1-realignment.md similarity index 100% rename from .changes/unreleased/dsh-0.2.2-rc1-realignment.md rename to .changes/archive/0.2.4/dsh-0.2.2-rc1-realignment.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 635b9a5..2b38581 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,13 @@ ## [Unreleased] +## [0.2.4] - 2026-11-06 + +### Changed +- The verified runtime baseline moved to `@deepseek-ai/dsh@0.2.2-rc.1`, and both frozen contracts — the wire-parity surface and the launch contract — were re-baselined against it. The wire delta is additive: upstream now declares eight request methods while this crate still sends the same six, and `session/query`, `approval/request`, and `user-question/ask` stay deliberately unwrapped, so a leading `/` in run input is still sent to the model as prompt text rather than executed as a native command. +- Two documented facts were corrected, with no public-API change: upstream declares six server-to-client notifications while the crate still models four, `subagent.started` is emitted only for subagent-origin sessions (an ordinary fork therefore adds no tree edge), and a resumed session takes the initialized provider/model route instead of its stored selection, where a stored reasoning effort survives only when both match. The two added notification names reach the crate only through its unknown-method path. +- The runtime's install floor is documented as Node `>= 24.9.0`. The crate still installs, downloads, and versions nothing, so a caller below that bound sees the runtime's own engine failure rather than a crate error. + ## [0.2.3] - 2026-10-17 ### Added diff --git a/Cargo.lock b/Cargo.lock index cabbacb..1311925 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -40,7 +40,7 @@ checksum = "f079e83a288787bcd14a6aea84cee5c87a67c5a3e660c30f557a3d24761b3527" [[package]] name = "deepseek-harness-sdk" -version = "0.2.3" +version = "0.2.4" dependencies = [ "nix", "serde", diff --git a/Cargo.toml b/Cargo.toml index 77bb3ad..c70984d 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -8,7 +8,7 @@ resolver = "2" [package] name = "deepseek-harness-sdk" -version = "0.2.3" +version = "0.2.4" edition = "2021" description = "Low-level Rust client and Python-parity high-level API for the DeepSeek Harness runtime stdio JSON-RPC 2.0 protocol" license = "Apache-2.0"