LiteLLM v1.100.0-dev.1

v1.100.0-dev.1Pre-release
Added 3
  • Support Entra ID / OAuth auth on every Azure AI Foundry route
  • Per-team New Relic trace routing via team callbacks
  • Gate patching of SDK internals in tests as TQ008
Fixed 17
  • Keep the conversation when chaining previous_response_id on the bridge
  • Add soft_budget, tags, and soft_budget_alerting_emails to litellm_team in Terraform
  • Theme the created-key box to follow dark mode
  • Restore the public model name tooltip layout in the add model flow
  • Render team and org tpm/rpm limits of 0 as 0 instead of Unlimited
  • Repoint the key detail URL to the rotated hash after regenerating

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

View original

Upgraded? How did it go?

Discussion