v1.83.7.rc.1

LiteLLM Releases / 4/12/2026

📰 NewsDeveloper Stack & InfrastructureTools & Practical Usage

Key Points

  • LiteLLM Docker images for version v1.83.7.rc.1 are signed using Sigstore cosign, and the article provides two ways to verify the image signature (recommended verification by pinned commit hash, and convenience verification by release tag).
  • The release signing uses a consistent public key introduced at a specific GitHub commit, enabling verification that signatures match the intended key.
  • The update includes a breaking change to Prometheus monitoring: the default LATENCY_BUCKETS (latency histogram boundaries) are reduced from 35 to 18.
  • Existing Prometheus dashboards or PromQL SLO queries that reference specific histogram le values (e.g., le="1.5" or le="9.5") will lose their series after upgrading, requiring review and updates.
  • The changelog highlights at least one additional fix focused on improving input validation on LiteLLM proxy management endpoints.

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

⚠️ Breaking Changes

Prometheus default latency histogram buckets reduced (#25527)

The default LATENCY_BUCKETS has been reduced from 35 to 18 boundaries. If you have existing Prometheus dashboards or PromQL SLO queries that reference specific le values (e.g. le="1.5", le="9.5"), those series will no longer exist after upgrading. Review and update any affected queries or dashboard panels.


What's Changed

New Contributors

Full Changelog: v1.83.6-nightly...v1.83.7.rc.1