[Dependency Conflict] a2a-sdk<1.0 constraint in [extensibility] extra

Aperta
#474 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
15/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

The sap-cloud-sdk[extensibility] extra requires a2a-sdk<1.0, which creates an unresolvable dependency conflict for projects that need both:

  1. SAP Cloud SDK extensibility features
  2. 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

  1. a2a-sdk 1.3.0 is current: Cannot downgrade to <1.0 without breaking A2A protocol compatibility
  2. sap-cloud-sdk 0.66.x allows mcp 2.x: Would unblock litellm upgrades, BUT requires a2a-sdk<1.0
  3. Security patches blocked:
  4. 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!

Lingua principale
Python
Stelle
29
Fork
45
Merge medio
2g 4h
PR unite (30g)
51

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di SAP/cloud-sdk-python

Tutte le issue di SAP/cloud-sdk-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.