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: The source has ongoing GitHub updates, including multiple builds and release-candidate iterations in the last several days (latest push on 2026-09-17, with v1.102.0-rc.2 and v1.103.0-dev.1 the day before).
- Apparent cadence: Updates appear to run on a daily to near-daily rhythm recently, with frequent dev builds and release candidates (v1.101.0, v1.102.0-rc.1, v1.102.0-dev.2, v1.102.0-rc.2, v1.103.0-dev.1 all clustered between 2026-09-10 and 2026-09-16).
AI summary generated
Recent updates
v1.103.0-dev.2
v1.103.0-dev.2 focuses on wiring and correctness changes across guardrails, router/proxy behavior, streaming token accounting, and several CI and E2E harness improvements. The release notes also include operational guidance for verifying LiteLLM Docker image signatures via cosign using a pinned commit hash. A documented “fix!” indicates a budget re-check behavior change on router fallback targets.
BreakingSecurityFeaturesv1.102.0-rc.2
This release backports fixes related to request parameter leakage and how parameters are forwarded when routing between different LiteLLM OpenAI-compatible APIs. The code changes focus on tightening which kwargs get sent to upstream endpoints and altering how `extra_headers` is handled when an experimental base HTTP handler is enabled.
v1.103.0-dev.1
v1.103.0-dev.1 adds operational hardening (documented cosign Docker image signature verification) plus a large set of fixes and feature tweaks across the proxy, responses pipeline, MCP, auth, UI, and CI. The visible release notes emphasize targeted bug fixes (spend logs, budgeting, guardrails, logging) and a few user-facing additions such as file management support, proxy limits, and management endpoints.
SecurityFeaturesv1.101.0
v1.101.0 is a large maintenance release focused on proxy correctness and observability (OTel and tracing), plus many targeted fixes across Bedrock, Anthropic, Guardrails, UI, and E2E test stability. The release notes also include a security-oriented update describing cosign-based Docker image signature verification for LiteLLM images.
SecurityFeaturesv1.102.0-rc.1
v1.102.0-rc.1 is a release candidate focused on fixes and performance improvements across LiteLLM proxy routing, caching, MCP (Model Context Protocol) OAuth and OpenAPI handling, and streaming spend accounting. The release notes also call out OCR adapter work (adding multiple providers/adapters and routing native requests through core), along with several UI and operational improvements.
SecurityFeaturesv1.102.0-dev.2
v1.102.0-dev.2 focuses on a broad set of fixes and some targeted features across MCP, proxy/routing, spend tracking, guardrails, UI, Terraform, and various model-provider adapters. The release notes also include Docker image signature verification instructions using cosign with a pinned public key. Overall, the changes described are primarily bug fixes and behavior corrections, with no explicit breaking-change callouts in the notes.
SecurityFeaturesv1.100.1
Release v1.100.1 is primarily a set of backports, including a router change intended to prevent retry breadcrumbs from retaining earlier requests. The code diff also includes substantial Docker build changes, notably switching the image Python runtime from python3 to python-3.13, and a refactor of how retry breadcrumbs are stored and limited.
Breakingv1.101.0-rc.2
v1.101.0-rc.2 release notes focus on verifying LiteLLM Docker image signatures with cosign. The code diff, however, includes substantial OpenTelemetry (OTel) tenant trace destination fan-out and request-scoped routing logic changes, plus container build and dependency-list adjustments that are not mentioned in the release notes.
Featuresv1.102.0-dev.1
This dev release focuses on policy engine improvements for streaming responses and multiple proxy/router fixes, with additional platform work across MCP, pricing/cost maps, and the UI. It also includes a supply-chain related note about verifying LiteLLM Docker image signatures with cosign.
SecurityFeaturesv1.100.0
v1.100.0 release includes a large set of fixes and feature work across the API bridge, proxy routing, CI, observability, and UI. The release notes also highlight Docker image signing with cosign and instruct how to verify images using a pinned commit hash or the release tag.
BreakingSecurityFeaturesv1.101.0-rc.1
v1.101.0-rc.1 release notes primarily document integrity guidance for LiteLLM Docker images, instructing users to verify cosign signatures using a pinned commit hash or the release tag. The release notes also list a large set of fixes across proxy behavior, spend tracking, guardrails, vector stores, credential redaction, routing retries, and various provider-specific adjustments.
Featuresv1.101.0-dev.2
v1.101.0-dev.2 mainly focuses on operational trust via cosign signature verification for LiteLLM Docker images, plus a large set of targeted fixes across proxy, router, UI, guardrails, MCP, and various provider integrations. The included Rust code diff also shows a broader internal refactor in the ai-gateway layer (audio transcription moved into core, OCR lifecycle restructuring), alongside a standardized error type.
SecurityFeaturesv1.99.1
v1.99.1 is a Docker-only release, with image tags (including latest and main-stable) updated to point to 1.99.1. The documented functional change is an OpenTelemetry v2 improvement: spans can now include cache token counts in addition to cache cost.
v1.97.1
v1.97.1 is a Docker-only maintenance release intended to refresh base-image and dependency pins. The release notes emphasize Docker hardening and Python 3.13 pinning, claiming no LiteLLM behavior change on top of the 1.97 line.
Securityv1.101.0-dev.1
v1.101.0-dev.1 includes a broad mix of proxy, model capability, UI, and routing fixes, plus new proxy endpoints for token counting and improvements around streaming and configuration handling. The release notes also document CI changes like auto-closing duplicate issues and provide instructions for verifying LiteLLM Docker image signatures with cosign.
SecurityFeaturesv1.99.0
v1.99.0 focuses on improving a wide range of proxy, Bedrock, UI, guardrails, and adapter behaviors, plus instructions for verifying Docker image signatures with cosign. The release notes are heavily detail-oriented around specific API and UI fixes, but the provided diff also shows infrastructure-level Docker build changes that are not mentioned.
SecurityFeaturesv1.99.0-rc.2
v1.99.0-rc.2 is a release candidate focused on backported UI and e2e fixes, plus an Anthropic bridge fix. The release notes also include instructions for verifying LiteLLM Docker image signatures with cosign.
v1.100.0-rc.1
v1.100.0-rc.1 is a release candidate focused on correctness fixes across Anthropic reasoning_effort behavior, router and proxy routing/cost accounting, and spend tracking attribution. It also adds several new API surface areas and UI improvements, plus Rust-side performance work in the Python bridge. The release notes also include instructions for verifying LiteLLM Docker image signatures using cosign.
Featuresv1.100.0-dev.2
v1.100.0-dev.2 is a broad internal and product release covering proxy behavior, cost tracking, caching, and various CI and developer workflow improvements. The release notes list many targeted fixes across specific providers and endpoints, plus some UI refactors and observability changes. The code diff also reveals a few behavioral changes that are not reflected in the provided release notes, most notably around logging configuration parsing.
BreakingFeaturesv1.100.0-dev.1
v1.100.0-dev.1 focuses on correctness and routing behavior fixes across the LiteLLM proxy and multiple provider bridges, along with CI reliability improvements (including e2e record/replay and Postgres test coverage). The included diff excerpts also show CI instrumentation changes (coverage now includes the enterprise package) and a small runtime addition to logging configuration via a new global flag. No clear end-user API-breaking changes are visible in the provided code diff excerpts beyond the two explicitly marked breaking items in the release notes.
BreakingSecurityFeatures