v1.86.6
BerriAI/litellmv1.86.6Jun 14, 2026by github-actions[bot]
AI Summary
This release focuses on security and maintenance for Docker images, introducing cryptographic verification using Cosign, and backporting patches to the stable 1.86.x line.
Key Highlights
- Docker images are now signed with Cosign for cryptographic verification.
- Backport of 1.84.8 patches and dependencies to stable/1.86.x.
- Instructions provided for verifying signatures using pinned commit hashes or release tags.
New Features
- Cosign signature verification support for LiteLLM Docker images.
Full Release Notes
## Verify Docker Image Signature All LiteLLM Docker images are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). Every release is signed with the same key introduced in [commit `0112e53`](https://github.com/BerriAI/litellm/commit/0112e53046018d726492c814b3644b7d376029d0). **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: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \ ghcr.io/berriai/litellm:v1.86.6 ``` **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: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/v1.86.6/cosign.pub \ ghcr.io/berriai/litellm:v1.86.6 ``` 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 * chore(release): backport 1.84.8 patches + #30220 deps to stable/1.86.x and cut 1.86.6 by @yuneng-berri in https://github.com/BerriAI/litellm/pull/30403 **Full Changelog**: https://github.com/BerriAI/litellm/compare/v1.86.5...v1.86.6