--- snapshot-1780472081+++ snapshot-1780558486@@ -2,11 +2,19 @@ Release notes from litellm -2026-06-03T00:31:21Z tag:github.com,2008:Repository/671269505/v1.86.3 2026-06-03T01:40:43Z +2026-06-04T03:44:41Z tag:github.com,2008:Repository/671269505/v1.84.5 2026-06-04T04:11:46Z + +v1.84.5 + +

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

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

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

Full Changelog: v1.84.4...v1.84.5

github-actions[bot] tag:github.com,2008:Repository/671269505/v1.86.3 2026-06-03T01:40:43Z v1.86.3 -

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

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

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

Full Changelog: v1.86.2...v1.86.3

github-actions[bot] tag:github.com,2008:Repository/671269505/v1.85.3 2026-06-02T02:30:54Z +

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

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

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

Full Changelog: v1.86.2...v1.86.3

github-actions[bot] tag:github.com,2008:Repository/671269505/v1.85.4 2026-06-04T05:16:40Z + +v1.85.4 + +

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

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

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

Full Changelog: v1.85.3...v1.85.4

github-actions[bot] tag:github.com,2008:Repository/671269505/v1.85.3 2026-06-02T02:30:54Z v1.85.3 @@ -34,12 +42,4 @@ v1.86.2 -

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

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

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

Full Changelog: v1.86.1...v1.86.2

github-actions[bot] tag:github.com,2008:Repository/671269505/v1.85.2 2026-05-27T08:20:26Z - -v1.85.2 - -

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

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

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

Full Changelog: v1.85.1...v1.85.2

github-actions[bot] tag:github.com,2008:Repository/671269505/v1.84.3 2026-05-27T17:44:32Z - -v1.84.3 - -

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

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

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

Full Changelog: v1.84.1...v1.84.3

github-actions[bot]+

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

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

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

Full Changelog: v1.86.1...v1.86.2

github-actions[bot]