LiteLLM v1.96.0-rc.1

v1.96.0-rc.1Pre-release
Added 8
  • Expose classifier context window fields on Auto-Router screens
  • Add generic list handler for /management/v1
  • Source the ID-JAG subject from the user's stored SSO assertion
  • Add GET /management/v1/budgets
  • Show which log rows are the auto-router's own classifier calls
  • Add sorting, filtering and search to the budgets page
  • Add global exclude_metrics and exclude_labels options for prometheus
  • Let AI API keys read /model/info
Changed 1
  • Gate all mock testing request params behind a single config flag
Fixed 17
  • Annotate connected-app reachability on the gateway connect page
  • Recover the tool-name prefix boundary from registered prefixes
  • Exclude skipped tests from coverage-registry numerator
  • Deny MCP access when a named entitlement cannot be read
  • Dispose recycled client sessions deterministically
  • Run bedrock guardrail on MCP tool calls in during_mcp_call mode
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-rc.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-rc.1/cosign.pub \
  ghcr.io/berriai/litellm:v1.96.0-rc.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

Full Changelog: https://github.com/BerriAI/litellm/compare/v1.96.0-dev.2...v1.96.0-rc.1

View original

Upgraded? How did it go?

Discussion