LiteLLM is a GitHub-hosted project for working with and routing language model requests (as suggested by the project name). It’s useful for developers who want a single integration point to use LLMs through LiteLLM.
Project status
- Actively maintained, with an upstream push and multiple updates on 2026-11-05.
- The apparent cadence is very frequent, with updates across patch, development, and release-candidate versions on most days in the supplied recent history.
AI summary generated
Recent updates
v1.110.0-dev.2
v1.110.0-dev.2 adds proxy, UI, guardrail, cost-catalog, and Redis capabilities while fixing issues across routing, streaming, provider integrations, and authentication. The release also signs its Docker image with cosign and marks the Responses SSE event-framing change as breaking.
BreakingSecurityFeaturesv1.108.3
LiteLLM 1.108.3 (LTS) fixes three reported issues involving Bedrock requests with an empty api_base, large MCP tool results, and duplicate model-level post_call guardrail checks. The diff also changes dependency constraints and removes several automation and CI workflows that are not described in the release notes.
v1.110.0-dev.1
LiteLLM v1.110.0-dev.1 adds provider and accounting capabilities, updates model pricing and metadata, and includes fixes across routing, proxy behavior, streaming, usage accounting, and integrations. The release notes identify several compatibility-sensitive changes and document Docker image signature verification; the visible code diff also reveals unannounced CI and developer-workflow changes.
BreakingSecurityFeaturesv1.108.2
v1.108.2 is an LTS maintenance release containing backported fixes for audio transcription, routing, Bedrock, Vertex AI, MCP, and the Responses API. The image-signing instructions are also included. The visible code diff contains broader changes to MCP request handling, Bedrock structured outputs, and message redaction behavior that the release notes describe only at a high level or do not mention.
BreakingFeaturesv1.108.1
v1.108.1 documents Docker image signature verification, CI coverage on stable, rc, and lts branches, and several backported fixes, including a pass-through credential selection fix. The supplied code diff also shows significant Helm, batch-cost polling, managed-object storage, Docker image, and CI changes that are not detailed in the release notes. The diff compares v1.107.0-rc.3 to v1.108.1, rather than v1.108.0 to v1.108.1, so it does not establish which of those changes were introduced specifically in v1.108.1.
Securityv1.107.0-rc.3
v1.107.0-rc.3 backports GitHub Copilot per-user credential fixes and adds support for GHE.com tenants through an optional `github_copilot_host` credential field. The release notes say no upgrade action is needed, but the diff also changes internal credential APIs and invalidates user connections when a credential's GitHub host changes.
SecurityFeaturesv1.106.7
v1.106.7 removes the Lens beta from the LiteLLM proxy package and Helm charts, and adds `/v1/videos` support for custom providers registered through `custom_provider_map`. The diff also contains undocumented model-pricing schema additions, a vector-store metadata cleanup utility, and container dependency changes.
BreakingFeaturesv1.108.0
v1.108.0 adds provider and proxy capabilities, including Vertex AI Interactions, Bing grounding search, Azure AI OAuth, and routing options, alongside a large set of provider, billing, security, and UI fixes. The release also signs its Docker images with cosign and documents how to verify them. The supplied release notes and diff are both truncated, so this analysis is limited to the changes visible in the provided material.
BreakingSecurityFeaturesv1.109.0-rc.1
v1.109.0-rc.1 is a broad release covering provider support, routing, streaming, pricing and usage accounting, proxy behavior, and model catalog updates. It also changes several explicitly flagged interfaces and behaviors, and publishes a signed Docker image with instructions for verifying it using cosign.
BreakingSecurityFeaturesv1.109.0-dev.2
v1.109.0-dev.2 includes a broad set of provider, routing, Responses API, proxy, UI, and pricing fixes, alongside new providers and quota, accounting, and activity-reporting features. The release notes identify several behavior changes as breaking; the visible diff also shows unannounced CI and contributor-process changes, but it contains only 23 of the 300 changed files, so a complete code-to-notes audit is not possible from this excerpt.
BreakingFeaturesv1.108.0-rc.1
v1.108.0-rc.1 documents Docker image signatures verifiable with cosign and says the release brings the 1.108.0 release candidate in line with v1.106.x patch fixes. The visible diff primarily changes CI and integration-test infrastructure; it does not show confirmed public LiteLLM API or runtime behavior changes.
Securityv1.106.6
v1.106.6 backports a proxy fix for gzip response handling, scoping compression correctly and moving compression off the event loop. The release also documents cosign signatures for LiteLLM Docker images and provides commands to verify them.
SecurityFeaturesv1.105.7
The release notes describe a proxy gzip fix that scopes compression and moves it off the event loop, plus instructions for verifying signed Docker images. The supplied diff also shows many substantial changes not described in those notes, but it compares v1.106.5 to v1.105.7 rather than v1.105.6 to v1.105.7, so it cannot reliably establish which differences were introduced specifically by this release.
SecurityFeaturesv1.109.0-dev.1
LiteLLM v1.109.0-dev.1 is a large development release with provider and API additions, routing and billing fixes, a new Admin Chat UI, and extensive MCP, agent, and guardrail updates. The release notes also call out several behavior changes requiring configuration or caller updates, including token counting, Gemini parameters, Anthropic token limits, authorization, and image verification.
BreakingSecurityFeaturesv1.106.5
v1.106.5 changes rejected-request logging and GCS logger configuration, with the release notes stating that no upgrade action is required. The supplied diff excerpt also shows substantial CI and test-infrastructure changes that are not described in the release notes; it does not include the implementation hunks for the two documented logging changes.
Breakingv1.105.6
The release notes describe two logging and observability changes: rejected-request failure logs retain core request fields, tags, and guardrail details, and the GCS logger uses the proxy-configured bucket and credentials. However, the supplied diff compares v1.104.8 to v1.105.6, while the release notes describe v1.105.5 to v1.105.6, so the 300-file diff includes changes that cannot reliably be attributed to this release.
Featuresv1.104.8
v1.104.8 documents two logging and observability changes: rejected-request failure logs retain only core request fields, tags, and guardrail details, and the GCS logger uses the bucket and credentials configured on the proxy. The release notes say no upgrade action is needed. The supplied diff compares v1.103.10 to v1.104.8, rather than the release's stated v1.104.7 to v1.104.8, and is truncated, so most additional changes shown cannot be reliably attributed to this release.
v1.103.10
The release notes describe two logging and observability changes: rejected-request failure logs retain only core request fields, tags, and guardrail details, and the GCS logger uses the proxy-configured bucket and credentials. The supplied code diff is much broader than those notes, but it compares v1.106.4 to v1.103.10 rather than v1.103.9 to v1.103.10, so its extra changes cannot reliably be attributed to this release.
v1.106.4
v1.106.4 fixes a proxy startup ImportError when the remote model cost map is unreachable and addresses image-scan findings involving brotli, a root CA, and unused lockfile packages. The release notes say no upgrade action is needed. The supplied diff is cumulative from v1.105.5, rather than v1.106.3, and is truncated, so not all changes can be attributed to this release.
v1.105.5
v1.105.5 documents two deployment fixes: preventing a proxy startup ImportError when the remote model cost map is unreachable, and resolving image-scan findings involving brotli, a CA certificate, and unused lockfile packages. The supplied diff also shows substantial CI, release-automation, and deployment changes not described in the release notes; however, it is truncated and compares v1.104.7 to v1.105.5 rather than the release-notes baseline of v1.105.4.
Features