github BerriAI/litellm v1.86.0

4 hours ago

Note

Two things to be aware of about the non-root image in this release:

  • Dockerfile build patch. The non-root Dockerfile failed to build at the v1.86.0 tag, and a patch was applied to produce ghcr.io/berriai/litellm-non_root:v1.86.0. The non-root image was built from commit a13cd212c82f00d73456a375dd0d89cef85244a8.
  • No cosign attestation. The non-root image was published without a cosign signature. If you run cosign verify on images before deploying, this image will not pass verification and you will not be able to upgrade to it.

The ghcr.io/berriai/litellm:v1.86.0 and ghcr.io/berriai/litellm-database:v1.86.0 images are signed normally. v1.86.1 ships early next week with signed builds of all three images.


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.86.0

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

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.85.0...v1.86.0

Don't miss a new litellm release

NewReleases is sending notifications on new releases.