LiteLLM v1.100.0-dev.2

v1.100.0-dev.2Pre-release
Added 1
  • Configure deployment caller identity in Prometheus
Fixed 19
  • Map /v1/messages provider errors before failure logging in OTEL
  • Map upstream status codes for providers with no exception_type branch
  • Record ownership of streamed responses under managed ids in passthrough
  • Encrypt streamed responses ids on /openai/v1/responses and /responses aliases in proxy
  • Fail open on response_format instead of dropping it for unregistered models in together_ai
  • Honor DATABASE_DISABLE_PREPARED_STATEMENTS in componentized entrypoints in proxy

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.100.0-dev.2

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

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.100.0-dev.1...v1.100.0-dev.2

View original

Upgraded? How did it go?

Discussion