LiteLLM v1.96.0-dev.1

v1.96.0-dev.1Pre-release
Added 4
  • Add service_tier label to latency and spend metrics in Prometheus
  • Publish a generated JSON schema for model_prices_and_context_window.json
  • Split failed requests into their own series on the cache dashboard in UI
  • Add shareable log links via log_id query param on the logs page in UI
Fixed 15
  • Keep keep-alive connector config when an aiohttp session is rebuilt
  • Pin bundled postgres and redis to bitnamilegacy images in Helm
  • Decide rawPredict passthrough streaming from the request body for Vertex
  • Translate stop_sequences and disabled thinking for non-Claude targets in anthropic-adapter
  • Allow /v1/messages for JWT teams by default
  • Skip team model aliases that point at deleted deployments in proxy
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.96.0-dev.1

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.96.0-dev.1/cosign.pub \
  ghcr.io/berriai/litellm:v1.96.0-dev.1

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.95.0-rc.1...v1.96.0-dev.1

View original

Upgraded? How did it go?

Discussion