LoginSign Up
← Back to all sparks
L

LiteLLM

AI-ML-PLATFORMS
Velocity5.0

LLM gateway and proxy for calling 100+ model providers with spend tracking

www.litellm.ai ↗

LiteLLM's 1.109 dev build stacks 704 PRs and 15 required config changes.

llm gatewaybreaking changessupply-chain securityaccess controlrelease maintenance
◆Current state
LiteLLM is patching four stable lines (1.103 to 1.106) in lockstep, most recently with leaner failure logs, a proxy-level GCS logger config and a new cosign signing key. On Oct 28 it opened a 1.109.0 dev line with 704 merged PRs and 15 items flagged as action required. Those include a new image-verification key, Gemini 3.6 Flash rejecting temperature/top_p/top_k, no more local token-count estimates, and budget edits on keys restricted to admins.
◆Where it's heading
The stable lines get hardening and backports, while the next minor is moving the gateway toward stricter defaults: tighter key and budget permissions, explicit max_tokens for unmapped Anthropic models, and provider-side token counting. The size of the action-required list means upgrades are turning into real migrations for self-hosters.
◆Prediction
Expect more 1.109 dev and rc builds that trim or document the breaking list before a stable 1.109.0, while the 1.103 to 1.106 lines keep getting matching patches.

◆Recent moves

  1. 1d ago

    LiteLLM 1.109 dev: 704 PRs, 15 changes need action

    The first 1.109 dev build moves the feature line on while the stable branches get backports. Its 15 action-required items, from new cosign verification to admin-only budget edits and provider-side token counting, show the next minor will require config work to adopt.

    View source ↗
  2. 1d ago

    v1.106.5: leaner failure logs, GCS logger uses proxy config

    Failure logs for rejected requests now keep only core request fields, tags and guardrail details, so less request data ends up in log sinks. The GCS logger also uses the proxy's configured bucket and credentials, fixing logs going to the wrong place.

    View source ↗
  3. 1d ago

    v1.105.6: failure-log and GCS logger fixes backported

    Backports the trimmed failure logs and GCS logger fix to the 1.105 line.

    View source ↗
  4. 1d ago

    v1.104.8: failure-log and GCS logger fixes backported

    Backports the trimmed failure logs and GCS logger fix to the 1.104 line.

    View source ↗
  5. 1d ago

    v1.103.10: failure-log and GCS logger fixes backported

    Backports the trimmed failure logs and GCS logger fix to the oldest supported line, 1.103.

    View source ↗
  6. 4d ago

    v1.105.5: startup crash fix and scanner-clean images

    1.105.5 fixes the proxy exiting with an ImportError when it cannot reach the remote model cost map, and clears image-scan flags. It is one of three same-day backports.

    View source ↗