18 views
-/https://github.com/berriai/litellm/issues/11484
GitHub ยท issue

#11484 [Bug]: uvicorn dependency version too low

  • State: open
  • Author: @zhiruiwang
  • Labels: bug

### What happened?

Similar to this https://github.com/BerriAI/litellm/issues/7768 issue, the new releases of litellm specifies the `uvicorn` poetry dependency as: `uvicorn = {version = "^0.29.0", optional = true}`, which is `>=0.29.0 <0.30.0` (https://github.com/conda-forge/litellm-feedstock/issues/305)

This causes dependency conflicts in projects that use `google-adk`, because `google-adk` requires `uvicorn>=0.34.0`, while litellm enforces `uvicorn<0.30.0`.

Could you please review and publish a new release with higher `uvicorn` dependency? This would greatly help avoid installation issues for downstream projects.

Thank you in advance! Let me know if there's anything else I can do to assist.

### Relevant log output

```shell The following packages are incompatible โ”œโ”€ google-adk =* * is installable and it requires โ”‚ โ””โ”€ uvicorn >=0.34.0 * with the potential options โ”‚ โ”œโ”€ uvicorn [0.34.0|0.34.1|0.34.2|0.34.3], which can be installed; โ”‚ โ””โ”€ uvicorn [0.34.0|0.34.1|0.34.2|0.34.3] would require โ”‚ โ””โ”€ __win =* *, which is missing on the system; โ””โ”€ litellm =* * is not installable because there are no viable options โ”œโ”€ litellm [1.34.0|1.34.1|...|1.63.0] would require โ€ฆ

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 ยท 31d18h56m45s ago โ€” entered ยท #import:https:::github.com:berriai:litellm post #1788
The right task requires a new cross-cutting detection and observability integration, including runtime behavior, provider compatibility, configuration, and substantial testing. The left task is a narrowly scoped dependency constraint update with comparatively low implementation risk.
#0 of 0 ยท 31d18h1m39s ago โ€” current ยท #import:https:::github.com:berriai:litellm post #2694
The left issue requires coordinated request-schema and multimodal serialization changes in a provider-specific transformation, with compatibility handling and regression coverage for both silent correctness and API rejection paths. The right issue is primarily a dependency constraint update with packaging validation, so the left issue carries substantially greater implementation and testing risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search