LiteLLM is moving to Rust Read the latest updates.
LiteLLM v1.103.6 fixes realtime handshake errors and double spend logs
Deploy this version
- Docker
- Pip
docker run \
-e LITELLM_MASTER_KEY=sk-<paste-a-long-random-key> \
-e DATABASE_URL=postgresql://<user>:<password>@<host>:5432/<dbname> \
-e STORE_MODEL_IN_DB=True \
-p 4000:4000 \
docker.litellm.ai/berriai/litellm:1.103.6
pip install litellm==1.103.6
This release is published as ghcr.io/berriai/litellm:v1.103.6. See the GitHub release and the full releases page
v1.103.6 is a patch release on top of v1.103.5. It backports two fixes from main onto stable/1.103.x, so upgrading from stable/1.102.x keeps them. There are no new database migrations. The v1.103.6 tag points at dce7feb
What's Changed
- When the upstream realtime API refuses the websocket handshake, for example with a 401 from Azure, the client now gets an
errorevent that names the upstream HTTP status. The socket then closes with 1008 for 401 and 403, 1013 for 429 and 1011 for anything else. Before, the client saw a bare 1006 or 1011 close with no event, and the Azure relay could leave the client socket open - PR #42388 - Non-streaming requests of 256 KiB or more on the chat to Responses bridge log their spend once instead of twice, so key, team and daily spend are no longer counted twice for one request - PR #44508
Both fixes and the version bump are backported in PR #47522
Full Changelog
https://github.com/BerriAI/litellm/compare/v1.103.5...v1.103.6
