LiteLLM v1.99.0-rc.1

v1.99.0-rc.1Pre-release
Added 2
  • Add router_model_name to auto-routed response bodies
  • Add per-key Savings tab to key detail page in UI
Fixed 23
  • Match group members by SSO identity or email before creating a placeholder
  • Match streamed Messages usage cost to the recorded spend
  • Price partial-stream spend rows at the real model and keep prompt and cache fields
  • Price gpt-image-2 per size and quality from request params for fal_ai
  • Populate team member emails missing from the roster snapshot
  • Forward provider response headers on Bedrock chat completions
Security 1
  • Hash raw API keys before persisting to spend logs

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

View original

Upgraded? How did it go?

Discussion