LiteLLM v1.95.0-rc.3

v1.95.0-rc.3Pre-release
Added 1
  • Send RFC 8707 resource indicators on upstream OAuth legs in MCP
Changed 2
  • Bump gitpython to 3.1.55 and brace-expansion to 5.0.8
  • Move the logs end-user filter onto /management/v1 endpoint
Fixed 16
  • Advertise 1M context window for Claude Opus 4.6+ on Azure AI Foundry
  • Resolve judge_model credentials via lazy Router lookup in llm_as_a_judge guardrails
  • Center vertical toolbar dividers in UI
  • Restore the Add MCP Server dialog size and header spacing in UI
  • Truncate long team names in the models table team dropdown in UI
  • Resolve dashboard base URL from environment instead of hardcoding localhost in e2e UI tests
Security 1
  • All LiteLLM Docker images are now signed with cosign for verification
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.95.0-rc.3

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.95.0-rc.3/cosign.pub \
  ghcr.io/berriai/litellm:v1.95.0-rc.3

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

Full Changelog: https://github.com/BerriAI/litellm/compare/v1.95.0-rc.2...v1.95.0-rc.3

View original

Upgraded? How did it go?

Discussion