NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #295 most downloaded on PyPI
Library to easily interface with LLM API providers
Latest stable
1.110.2
Last release today
21 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
4 versions withdrawn
withdrawn after publishing
3 years old
1340 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
feat(proxy): log keys and teams still on the deprecated empty models defaults at boot by @paveln83 in #50720
All LiteLLM Docker images are signed with cosign. This release is signed with the key introduced in commit e82a3c6.
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 published signing key:
cosign verify \
--key https://raw.githubusercontent.com/BerriAI/litellm/e82a3c646908ba0a6ee0beddc4310d7a6cac4065/cosign.pub \
ghcr.io/berriai/litellm:v1.111.0-dev.1Verify 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.111.0-dev.1/cosign.pub \
ghcr.io/berriai/litellm:v1.111.0-dev.1Expected 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
Note truncated.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
cosign verify \ --certificate-identity https://github.com/BerriAI/project-releaser/.github/workflows/release.yml@refs/heads/main \ --certificate-oidc-
cosign verify \
--certificate-identity https://github.com/BerriAI/project-releaser/.github/workflows/release.yml@refs/heads/main \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
ghcr.io/berriai/litellm:v1.110.2Same command for litellm-database, litellm-non_root and the docker.io/litellm/* images
11 PRs. 8 fixed. No action needed to upgrade
temperature=1 returning 400 on Claude models that removed sampling params on Anthropic, Vertex AI and Azure AI, broken since v1.110.0-rc.2 (#52341)/v1/chat/completions and /v1/messages unless store: false (#52906) Also in 1.106.12, 1.108.13, 1.109.3/v1/messages ignoring the deployment's custom prices, broken since v1.109.0 (#52313)jwt_issuer taking 5 minutes to apply when litellm_jwtauth.issuers is set, broken since v1.103.0 (#52350) Also in 1.108.13, 1.109.3/key/info letting a key with no user read other userless keys by hash or alias (#52838, #52925) Also in 1.106.12, 1.108.13, 1.109.3Backport #52463 · Backport #52469 · Backport #52690 · Backport #52751 · Backport #52920 · Backport #52938 · Full changelog
cosign verify \ --certificate-identity https://github.com/BerriAI/project-releaser/.github/workflows/release.yml@refs/heads/main \ --certificate-oidc-
cosign verify \
--certificate-identity https://github.com/BerriAI/project-releaser/.github/workflows/release.yml@refs/heads/main \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
ghcr.io/berriai/litellm:v1.110.1Same command for litellm-database, litellm-non_root and the docker.io/litellm/* images
3 PRs. 1 fixed, 2 changed. No action needed to upgrade
/v1/chat/completions or /v1/messages with store: false (#52658)curl but keeps wget and nc (#52595)feat(model-catalog): read successor_model, the provider's recommended replacement for a deprecating row by @kerry-berri in #49791
cosign verify \
--certificate-identity https://github.com/BerriAI/project-releaser/.github/workflows/release.yml@refs/heads/main \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
ghcr.io/berriai/litellm:v1.110.0Note truncated.
cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/e82a3c646908ba0a6ee0beddc4310d7a6cac4065/cosign.pub \ ghcr.io/berriai/litellm:
cosign verify \
--key https://raw.githubusercontent.com/BerriAI/litellm/e82a3c646908ba0a6ee0beddc4310d7a6cac4065/cosign.pub \
ghcr.io/berriai/litellm:v1.110.0-rc.3Same command for litellm-database, litellm-non_root and the docker.io/litellm/* images
7 PRs. 6 fixed, 1 changed. No action needed to upgrade
None or crashing when the endpoint comes from HUGGINGFACE_API_BASE (#51449)1p5b or 0p6b billing at double the up-to-4B rate (#51451)"fallbacks": "default", broken since v1.110.0-dev.1 (#51502)Backport #51514 · Backport #51854 · Backport #51858 · Full changelog
All LiteLLM Docker images are signed with cosign . This release is signed with the key introduced in commit e82a3c6 .
All LiteLLM Docker images are signed with cosign. This release is signed with the key introduced in commit e82a3c6.
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 published signing key:
cosign verify \
--key https://raw.githubusercontent.com/BerriAI/litellm/e82a3c646908ba0a6ee0beddc4310d7a6cac4065/cosign.pub \
ghcr.io/berriai/litellm:v1.110.0-rc.2Verify 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.110.0-rc.2/cosign.pub \
ghcr.io/berriai/litellm:v1.110.0-rc.2Expected 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
Full Changelog: v1.110.0-rc.1...v1.110.0-rc.2
All LiteLLM Docker images are signed with cosign . This release is signed with the key introduced in commit e82a3c6 .
All LiteLLM Docker images are signed with cosign. This release is signed with the key introduced in commit e82a3c6.
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 published signing key:
cosign verify \
--key https://raw.githubusercontent.com/BerriAI/litellm/e82a3c646908ba0a6ee0beddc4310d7a6cac4065/cosign.pub \
ghcr.io/berriai/litellm:v1.110.0-rc.1Verify 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.110.0-rc.1/cosign.pub \
ghcr.io/berriai/litellm:v1.110.0-rc.1Expected 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
Full Changelog: v1.110.0-dev.2...v1.110.0-rc.1
All LiteLLM Docker images are signed with cosign . This release is signed with the key introduced in commit e82a3c6 .
All LiteLLM Docker images are signed with cosign. This release is signed with the key introduced in commit e82a3c6.
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 published signing key:
cosign verify \
--key https://raw.githubusercontent.com/BerriAI/litellm/e82a3c646908ba0a6ee0beddc4310d7a6cac4065/cosign.pub \
ghcr.io/berriai/litellm:v1.110.0-dev.2Verify 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.110.0-dev.2/cosign.pub \
ghcr.io/berriai/litellm:v1.110.0-dev.2Expected 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
Full Changelog: v1.110.0-dev.1...v1.110.0-dev.2
One column per quarter.