Files
deepseek-harness/python
Chinesezjc 499c1262a2 ci(python): drop PR labeled trigger for python-release dry-run
Remove the pull_request:[labeled] trigger from python-release.yml so the
workflow no longer fires (and shows a gray skipped check) when a PR gets any
non-dry-run label. The credential-free dry-run validation is now manual-only
(workflow_dispatch with publish=false), preserving the validation capability
without a PR gray segment.

- python-release.yml: on is workflow_dispatch only; build.if is
  github.event_name == 'workflow_dispatch'.
- ci-workflow.spec.ts: assert python-release has no pull_request event and the
  simplified build.if.
- python/development.(md,zh.md) and 2026-08-11-python-publication-workflow note
  (en/zh/i18n): describe the manual dispatch-only dry-run path.

Verification: ci-workflow.spec.ts 14/14, typecheck clean, note-format 585,
verify-translation-pairing consistent.
2026-08-21 08:56:32 +08:00
..
2026-08-10 19:45:54 +08:00

DeepSeek Harness Python SDK

English | 中文

Python packages for driving DeepSeek Harness as a subprocess. The client SDK communicates with the bundled runtime over newline-delimited JSON-RPC on stdio.

Packages

Directory Dist / module Role
sdk deepseek-harness-sdk / deepseek_harness High-level turns API and lower-level JSON-RPC client
sdk-runtime deepseek-harness-runtime-bin / deepseek_harness_runtime Bundled runtime binaries and default agent configuration

Behavior

The SDK starts the matching bundled runtime unless the caller selects an explicit channel. The client selects the channel and supplies default configuration; the runtime itself always requires an explicit configuration. The SDK reference and runtime carrier reference own the complete runtime-selection and configuration contracts.

Contributor workflows

The Python contributor workflows cover building runtime artifacts, validating the packages, source-mode development, and distribution.