LiteLLM v1.97.0-rc.1

v1.97.0-rc.1Pre-release
Added 3
  • Add apply_user_budget_to_team_keys opt-in in proxy
  • Show user email or alias in usage data export in ui
  • Track turns per complexity tier in auto-router
Fixed 16
  • Pass SSE-KMS key through to the batch input-file S3 upload in bedrock
  • Stop indexing choices[0] on choiceless streaming chunks in anthropic adapter
  • Normalize /v1/completions and /v1/responses batch records in bedrock
  • Return the real status code when a credential update is rejected in proxy
  • Improve Headroom /v1/compress HTTP 404 diagnostics in proxy
  • Invalidate cached project object on project update and delete in proxy
Security 1
  • Respect AZURE_AUTHORITY_HOST and derive the Azure Monitor audience per cloud in azure_sentinel
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.97.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.97.0-rc.1/cosign.pub \
  ghcr.io/berriai/litellm:v1.97.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
New Contributors

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

View original

Upgraded? How did it go?

Discussion