v1.83.11-nightly

LiteLLM Releases / 4/22/2026

📰 NewsDeveloper Stack & InfrastructureSignals & Early TrendsTools & Practical Usage

Key Points

  • LiteLLM Docker images are signed using Sigstore cosign, and releases use the same public key introduced in commit 0112e53.
  • Users are recommended to verify image authenticity with cosign using the pinned commit-hash-based public key for the strongest security assurance.
  • A convenience verification method is also provided that uses the release tag, which depends on tag protection rules.
  • The expected cosign verification output includes successful validation of cosign claims and signature verification against the specified public key.
  • The v1.83.11-nightly update includes at least a new proxy feature to add a --reload flag for Uvicorn hot reload (dev only), and other changes starting with audio support for Scaleway.

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.83.11-nightly

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.83.11-nightly/cosign.pub \
  ghcr.io/berriai/litellm:v1.83.11-nightly

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: v1.83.10-nightly...v1.83.11-nightly