LiteLLM v1.105.0

v1.105.0
Added 7
  • Shared compatibility-aware result conversion across MCP tool surfaces
  • Rust registry validation for model catalog
  • Upstream response headers are passed to the native Messages stream in Rust
  • Agent clients for Claude Code, Codex and opencode in the testkit
  • Protocol versions and capability discovery can be configured for MCP
  • Databricks Zerobus trace logging callback integration
  • Native xAI batches and files support
Changed 2
  • SpendLogToolIndex is given its own share of the cleanup budget and logs a per-run summary
  • Framer trait replaced with tokio-util codecs
Fixed 9
  • Auth cache invalidation propagates over Redis Cluster via a node-level pub/sub client
  • Responses bridge stream failures are surfaced as Anthropic error events
  • Streamed /v1/responses container ownership is recorded before the response.completed frame
  • Provider budget spend is counted on every API surface in the router
  • Pre-output stream drops fall back, truncated streams fail, and request_timeout is honored for responses
  • A Bedrock converse-stream 200 that decodes to no events is surfaced as a 502 instead of an empty turn
Security 4
  • Docker images are signed with cosign using the same key, and users can verify signatures against a pinned commit hash or the release tag
  • SSO debug routes under /sso/debug are gated behind ENABLE_SSO_DEBUG and disabled by default behavior changed · inferred, marked in the notes below
  • Sentry scrubs PII and secrets inside object reprs and nested locals, with a SENTRY_SEND_DEFAULT_PII opt-in
  • raw_request is redacted when turn_off_message_logging is set in the proxy config

5 changes to check, marked in the notes below

From LiteLLM

Verify Docker Image Signature

All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53.

Verify using the pinned commit hash (recommended):

A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \
  ghcr.io/berriai/litellm:v1.105.0

Verify using the release tag (convenience):

Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/v1.105.0/cosign.pub \
  ghcr.io/berriai/litellm:v1.105.0

Expected output:

The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - The signatures were verified against the specified public key

What's Changed
New Contributors

Full Changelog: https://github.com/BerriAI/litellm/compare/v1.104.0...v1.105.0

View original

Upgraded? How did it go?

Discussion