From ada25255b335eaec79da2fc954dd7870029525ea Mon Sep 17 00:00:00 2001 From: LUOSENGWA Date: Tue, 1 Sep 2026 02:03:57 +0000 Subject: [PATCH] fix(copaw): pin mcp below 2.0.0 in copaw-worker mcp 2.0.0 renamed the client entrypoint streamablehttp_client to streamable_http_client. copaw 1.0.2 still imports the legacy name at worker startup, so any fresh image build resolving mcp>=1.13 to the 2.x line (2.1.1 since 2026-08-25) crashes every copaw worker with ImportError. The qwenpaw chain is unaffected because agentscope 2.x pins mcp<2.0.0. Cap copaw-worker's implicit mcp requirement at the 1.x line so CI integration tests (copaw->qwenpaw migration, copaw runtime shards) resolve mcp 1.29.1 again. --- copaw/pyproject.toml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/copaw/pyproject.toml b/copaw/pyproject.toml index c04357d73..dd1ea7f98 100644 --- a/copaw/pyproject.toml +++ b/copaw/pyproject.toml @@ -11,6 +11,12 @@ license = { text = "Apache-2.0" } requires-python = ">=3.10" dependencies = [ "copaw==1.0.2", + # mcp 2.0.0 renamed the client entrypoint + # `streamablehttp_client` -> `streamable_http_client` (breaking). + # copaw 1.0.2 imports the legacy name at worker startup, so the + # copaw worker crashes with ImportError when pip resolves mcp 2.x + # (agentscope 1.0.18 only requires mcp>=1.13). Cap at the 1.x line. + "mcp>=1.13,<2.0.0", "matrix-nio[e2e]>=0.24.0", "markdown-it-py>=3.0", "linkify-it-py>=2.0",