[Dependency Conflict] a2a-sdk<1.0 constraint in [extensibility] extra
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The conflict is in the packaging metadata of the sap-cloud-sdk [extensibility] extra, which pins a2a-sdk below 1.0; start in the project's pyproject.toml or setup metadata and find where that extra is declared. Check whether the MCP and A2A code paths actually need the old a2a-sdk API before changing the constraint. Done means the extra resolves alongside a2a-sdk 1.x in a clean install, with the existing extensibility tests still passing.
由索引模型根据 Issue 内容生成。
描述
Summary
The sap-cloud-sdk[extensibility] extra requires a2a-sdk<1.0, which creates an unresolvable dependency conflict for projects that need both:
- SAP Cloud SDK extensibility features
- A2A SDK 1.x (current protocol version)
This constraint blocks critical dependency upgrades, including security patches, and forces projects to choose between SAP integrations or modern dependency versions.
Impact
Currently blocking 2 of our PRs:
- sap-cloud-sdk upgrade (0.59.0 → 0.66.1)
- litellm security upgrade (1.99.0 → 1.109.1)
Dependency Conflict Chain
sap-internal-sdk >=0.9.2,<0.10.0
└─ sap-cloud-sdk[extensibility] >=0.55.2,<1
├─ a2a-sdk<1.0 ❌ Conflicts with a2a-sdk==1.3.0
└─ mcp>=1.1.0,<2 (v0.59.0) ❌ Blocks litellm 1.108.0+
OR
mcp>=1.1.0,<3 (v0.65.3+) ⚠️ Would allow mcp 2.x, BUT still blocked by a2a-sdk
Our project requirements:
├─ a2a-sdk[http-server]==1.3.0 (required for A2A protocol)
└─ litellm~=1.109.0 (needs mcp 2.x)
Why This Matters
- a2a-sdk 1.3.0 is current: Cannot downgrade to <1.0 without breaking A2A protocol compatibility
- sap-cloud-sdk 0.66.x allows mcp 2.x: Would unblock litellm upgrades, BUT requires a2a-sdk<1.0
- Security patches blocked:
- Dependency modernization blocked: Stuck on older versions of multiple packages
Requested Fix
Update sap-cloud-sdk[extensibility] to support a2a-sdk>=1.0
- Most projects use A2A SDK 1.x (current protocol)
- Allows both SAP integrations and modern dependencies
Workaround Attempted
- ❌ Downgrade a2a-sdk to <1.0 (breaks A2A protocol)
- ❌ Remove sap-internal-sdk (required for BTP integration)
- ❌ Skip [extensibility] extra (automatically included by sap-internal-sdk)
thx for your support!
- 主要语言
- Python
- 星标
- 29
- 派生
- 45
- 平均合并
- 2 天 4 小时
- 30 天内合并 PR
- 51
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
SAP/cloud-sdk-python 的其他 Issue
-
Relax opentelemetry-api cap (~=1.44.0) to allow 1.45.2 (fixes CVE-2026-114603 / GHSA-xcq7-p3pf-p88h)未关闭
难度 3/5 1-2 天 新手友好度 64/100
SAP/cloud-sdk-python#472 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 25/100
SAP/cloud-sdk-python#456 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 65/100
SAP/cloud-sdk-python#452 ·
维护者通常 1 天内回复
-
How/Whether langgraph-checkpoint-hana would be supported by sap-cloud-sdk?可能已有人在做 @gpretto 于 3 天前认领。 未关闭question
难度 5/5 一周以上 新手友好度 15/100
SAP/cloud-sdk-python#427 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
`list_mcp_tools` hangs when MCP endpoint returns plain-text error as `text/event-stream`可能重新可做 @cassiofariasmachado 于 54 天前认领，目前没有进行中的 PR。 未关闭bug
SAP/cloud-sdk-python#348 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 SAP/cloud-sdk-python 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
deepchem/deepchem#5289 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 1/5 1 小时以内 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 60/100
UKGovernmentBEIS/inspect_evals#2892 · 1 条评论 ·
维护者通常 1 天内回复
-
Versioning docs: say that no output from the 0.46 warning check means nothing is affected可能已有人在做 @grelinfo 今天认领。 未关闭documentation priority:low size:S
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
alphacrack/readme2demo#293 ·