v1.83.14-stable

LiteLLM Releases / 5/2/2026

📰 NewsDeveloper Stack & InfrastructureTools & Practical UsageModels & Research

Key Points

  • LiteLLM v1.83.14-stable Docker images are signed with Sigstore/cosign, using the same signing key across releases.
  • The article recommends verifying image signatures with the pinned commit hash for stronger cryptographic assurance of the original signing key.
  • It also provides a convenience method to verify using the release tag, which is easier to read but depends on repository tag protection.
  • The “What’s Changed” section notes a fix to preserve tool_use input arguments in the Anthropic adapter during streaming, and another fix related to preserving role='assistant' in Azure streaming when include_usage is enabled.

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.14-stable

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.14-stable/cosign.pub \
  ghcr.io/berriai/litellm:v1.83.14-stable

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.13-nightly...v1.83.14-stable