Skip to main content
LiteLLM is moving to Rust Read the latest updates.

LiteLLM v1.108.6 (LTS) fixes negative spend and Gemini image edit cost

tip

v1.108.6 is a patch release on the 1.108 LTS line. The lts image tag always points to the latest LTS release, so pull docker.litellm.ai/berriai/litellm:lts to stay on the newest LTS patch. See the LTS pilot.

Deploy this version​

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.108.6

This release is published as ghcr.io/berriai/litellm:v1.108.6. See the GitHub release and the full releases page.

v1.108.6 is a patch release on top of v1.108.5. There are no new database migrations. The v1.108.6 tag points at 65781e1.

Breaking Changes
  • Keys, teams and auth: Move tenant_id, client_id, client_secret, azure_username, azure_password and azure_scope request tags into metadata - PR #51254, also in v1.106.9

What's Changed​

  • OpenAI: Fixed gpt-5.4 and gpt-5.5 function-tool calls without reasoning_effort being bridged to /v1/responses - PR #50968
  • Vertex AI and Gemini: Fixed Gemini image edits being billed at a flat per-image price instead of by tokens - PR #51038
  • Chat completions: Fixed 400 on chat and bridged /v1/responses calls that send an allowed_tools tool choice - PR #50726
  • MCP: Fixed Slack and GitHub MCP reconnects looping between the provider and the Connect page, broken since v1.107.0 - PR #51045
  • Guardrails: Changed Zscaler AI Guard to scan only the latest user message on requests, not the whole conversation - PR #50139
  • Cost tracking and pricing: Fixed 500 on usage routes when the database drops during key, user or team detail lookups - PR #50253
  • Keys, teams and auth: Fixed key, user and team spend going negative after a scheduled budget reset on multi-pod deployments, broken since v1.103.0 - PR #51120
  • Keys, teams and auth: Changed model and pass-through routes to refuse body client_id, client_secret, tenant_id and Azure login fields - PR #51254, also in v1.106.9
  • Admin UI: Fixed the empty Spend Per User card and missing per-user data on /user/daily/activity/aggregated - PR #51043

The changes are backported in PR #50435, PR #51064, PR #51122, PR #51229, PR #51240 and PR #51260.

Full Changelog​

https://github.com/BerriAI/litellm/compare/v1.108.5...v1.108.6

LiteLLM Enterprise
SSO/SAML, audit logs, spend tracking, multi-team management, and guardrails, built for production.
Learn more →