sap-cloud-sdk 0.52.2+ requires protobuf>=7.36.0,<8, conflicting with a2a-sdk (protobuf<7)

[sam-garland]

Describe the Bug

sap-cloud-sdk 0.52.2 and above requires protobuf>=7.36.0,<8, but a2a-sdk requires protobuf>=5.29.5,<7 (as of version 1.1.4).
So sap-cloud-sdk 0.52.2 and above are incompatible with recent versions of the a2a-sdk.

Resolver output (uv):

Because a2a-sdk==1.1.2 depends on protobuf>=5.29.5,<7 and
sap-cloud-sdk==0.53.0 depends on protobuf>=7.36.0,<8, we can conclude
[that] your requirements are unsatisfiable.

Any project using sap-cloud-sdk>=0.52.2 and an a2a-sdk release that still caps protobuf<7 cannot resolve.

Steps to Reproduce

1. Create an a2a agent that requires a2a-sdk 1.1.4 and sap-cloud-sdk 0.53.0 and attempt to resolve the dependencies

Expected Behavior

It needs to be possible to use a2a-sdk in combination with the sap-cloud-sdk without dependency conflicts.

Screenshots

No response

Used Versions

• Python version via python --version: Python 3.13.13
• SAP Cloud SDK for Python version: 0.53.0
• Framework version (if applicable, e.g., Flask, FastAPI): Starlette 1.6.0 / uvicorn 0.52.4 (A2A agent server, via a2a-sdk 1.1.2)

Installed packages via pip list or uv pip list

This is the resolved set with sap-cloud-sdk==0.52.0 (the working baseline —
0.53.0 is unsatisfiable, see below). Key packages:

a2a-sdk==1.1.2
grpcio==1.83.1
httpx==0.28.1
langchain==1.4.0
langchain-core==1.6.3
langchain-litellm==0.7.1
litellm==1.96.0
protobuf==6.33.6
sap-cloud-sdk==0.52.0
starlette==1.6.0
uvicorn==0.52.4

With sap-cloud-sdk==0.53.0 the set does NOT resolve:

Because a2a-sdk==1.1.2 depends on protobuf>=5.29.5,<7 and
sap-cloud-sdk==0.53.0 depends on protobuf>=7.36.0,<8, we can conclude
that your requirements are unsatisfiable.

(Resolved with uv pip compile --python-version 3.13, 175 packages total.)

Code Examples

Stack Trace

No response

Log File

Log file

...

Affected Development Phase

Getting Started

Impact

No Impact

Timeline

No response

[ArthurTonial]

Thanks for the report. Before we relax the protobuf constraint on our end, could you try using the [http-server] extra of a2a-sdk?

a2a-sdk[http-server]==0.3.22

This extra has looser protobuf constraints and may resolve cleanly alongside sap-cloud-sdk>=0.52.2. Let us know if that unblocks you. If not, we'll proceed with fixing the version conflict on our side.