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

Aberta
#474 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
15/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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!

Linguagem predominante
Python
Estrelas
29
Forks
45
Merge médio
2d 4h
PRs com merge (30d)
51

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de SAP/cloud-sdk-python

Todas as issues de SAP/cloud-sdk-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.