LiteLLM v1.101.0-dev.2

v1.101.0-dev.2Pre-release
Added 2
  • Slack alerts for per-user daily/monthly spend thresholds and spend anomaly detection
  • Fall back on anthropic safeguard refusals on /v1/messages in router
Fixed 17
  • Render the logs Tools panel with theme tokens in UI
  • Default max_idle_connection_lifetime to 60s on DB URLs in proxy
  • Follow tools/list pagination from upstream servers in MCP
  • Resolve router model aliases in /utils/supported_openai_params
  • Flatten top-level tool schema combinators on Azure chat completions
  • Route streamed responses-API output through the unified guardrail in Bedrock
Security 1
  • All LiteLLM Docker images are now signed with cosign for signature verification

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

View original

Upgraded? How did it go?

Discussion