Back to Explore

BerriAI/litellm

GitHub
68 updates · last 90 days1 watchersOpen source

Last release: 2026-06-14

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

  • Active maintenance: Evidence suggests ongoing active development, with an upstream push on 2026-06-11 and many updates across 2026-06-04 to 2026-06-10, including multiple release candidates (rc) and stable patch lines.
  • Apparent cadence: Updates look high frequency over the last week (several version bumps in a few days, plus rc iterations), indicating an evolving project rather than maintenance mode.

AI summary generated 2026-06-11

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v1.88.2

    2026-06-14

    v1.88.2 is primarily a maintenance backport release, with release notes focusing on Docker image signature verification guidance and two backport PRs to stable/1.88.x. The changelog text does not enumerate user-facing behavioral changes, but the code diff shows several meaningful modifications across Helm configuration, A2A metadata handling, and OpenTelemetry logging behavior.

    BreakingFeatures
  • v1.87.3

    2026-06-14

    v1.87.3 release notes only mention verifying LiteLLM Docker image signatures (cosign) and a backport/chore PR. The code diff for this release contains multiple functional changes across the proxy database schema, caching and response transformation, cost accounting, guardrail exception handling, and Helm chart defaults.

    BreakingFeatures
  • v1.86.6

    2026-06-14

    v1.86.6 release notes focus on Docker image signing verification using cosign with a pinned public key. The only additional note is a backport/release chore description (backport 1.84.8 patches and dependency updates) without listing functional changes.

    Security
  • v1.89.0

    2026-06-14

    v1.89.0 focuses on adding capabilities for Gemini, Interactions, MCP, and guardrails, along with multiple provider and proxy fixes for streaming and request shaping. It also includes Prometheus metric enrichment and notable performance work to reduce per-chunk overhead on Anthropic and Bedrock streaming paths.

    BreakingFeatures
  • v1.84.8

    2026-06-13

    v1.84.8 release notes mainly document how to verify LiteLLM Docker image signatures with cosign, and that the release was cut from backports to stable/1.84.x (no functional change details). The actual code diff (from v1.87.2 to v1.84.8) shows multiple behavioral and security-relevant modifications that are not described in the release notes.

  • v1.87.2

    2026-06-11

    Release v1.87.2 provides guidance on verifying LiteLLM Docker image signatures with cosign. Beyond the release-note headline, the code diff shows a large set of operational and behavioral changes including DB schema/migrations, response transformation and caching logic, cost-calculation changes, and Helm chart deployment behavior.

    Breaking
  • v1.86.5

    2026-06-11

    v1.86.5 release notes only document backporting PRs into the stable/1.86.x branch and cutting the 1.86.5 tag. The notes additionally describe how to verify the LiteLLM Docker image signatures with cosign using a pinned public key commit. No functional or API changes are described in the release notes.

  • v1.85.5

    2026-06-11

    Release v1.85.5 is presented primarily as a Docker image signing/verification update using a pinned cosign key commit (0112e53). The documented code changes are limited to a backport set of PRs to stable/1.85.x, plus a version bump; the release notes do not describe functional changes.

    Features
  • v1.84.7

    2026-06-11

    Release v1.84.7, according to the notes, is a stable backport (from PRs #30064 and #30009) and includes instructions for verifying LiteLLM Docker image signatures with cosign. The provided code diff, however, shows multiple substantive behavioral and security-related code changes that are not described in the release notes.

    BreakingSecurity
  • v1.89.0-rc.2

    2026-06-10

    Release v1.89.0-rc.2 notes are essentially a meta change (patching v1.89.0-rc.1, plus a Docker image cosign verification how-to) and do not describe functional product changes. The code diff, however, shows substantial internal and configuration changes, including MCP server database schema extensions and new runtime behavior around env var loading, plus additions of new provider/model identifiers and gateway route allowlisting.

    BreakingFeatures
  • v1.84.6

    2026-06-09

    v1.84.6 release notes focus on verifying LiteLLM Docker image signatures using cosign, and mention a backport for CrowdStrike AIDR metadata capture plus an identity fix. The code diff shows substantially more than that, including security hardening around file handling, logging dispatch changes for streaming success handlers, and Gemini/Vertex tool call payload modifications.

    Security
  • v1.88.1

    2026-06-09

    v1.88.1 is primarily a dependency refresh, bumping pyjwt to 2.13.0 and overriding ws to 8.20.1, plus the usual release version chore. The release notes also add guidance for verifying LiteLLM Docker image signatures using cosign with a pinned commit hash/public key. The provided release notes do not mention the large amount of repository and CI/workflow churn that appears in the actual diff.

    Security
  • v1.88.0

    2026-06-06

    v1.88.0 focuses on improving streaming and payload correctness across multiple providers (notably Bedrock/Cohere and Deepseek), plus fixes in proxy behavior and caching/telemetry. It also adds new UI/API capabilities around Interactions and MCP, enriches Prometheus metrics, and introduces measurable streaming hot-path performance gains. Deployment-related Helm defaults and ServiceAccount behavior changed, and there are security-relevant notes about signed Docker images.

    BreakingSecurityFeatures
  • v1.89.0-rc.1

    2026-06-06

    v1.89.0-rc.1 focuses on correctness fixes across providers, proxy behavior, and observability, along with multiple CI and test reliability improvements. It also adds features related to OpenTelemetry baggage and proxy shutdown handling, plus various MCP and vector-store fixes.

    SecurityFeatures
  • v1.88.0-rc.3

    2026-06-05

    The release notes only document a process change: verifying LiteLLM Docker image signatures with cosign using a pinned immutable commit hash or the protected release tag. No code-level behavior changes are mentioned in the provided release notes.

  • v1.87.1

    2026-06-04

    v1.87.1 release notes mainly describe operational items around verifying LiteLLM Docker image signatures, plus generic release maintenance backports into the stable/1.87.x line. No functional changes, API changes, or migration steps are explicitly documented in the release notes beyond those backports.

  • v1.88.0-rc.2

    2026-06-04

    Release v1.88.0-rc.2 is accompanied by documentation on verifying LiteLLM Docker image signatures using cosign. The release notes claim this release is primarily a patch of v1.88.0-rc.1, with fixes related to session-token exemption handling (including GHSA-q775 hardening).

    Security
  • v1.86.4

    2026-06-04

    Release v1.86.4 is primarily a release backport, with notes indicating staged fixes were merged into the stable/1.86.x line and the release cut was corrected after a premature bump revert. The included release notes do not describe any concrete API, runtime, or container behavior changes.

    Breaking
  • v1.85.4

    2026-06-04

    v1.85.4 is a maintenance release backporting several “staged fixes”, but the release notes do not detail what changed. The code diff shows multiple behavior changes across Azure auth handling, Vertex AI Anthropic request shaping, proxy auth model resolution, batch model authorization, key generation org membership checks, and pass-through streaming logging/dedup behavior.

    BreakingSecurity
  • v1.84.5

    2026-06-04

    v1.84.5 release notes are minimal, describing only a backport of six staged fixes into stable/1.84.x. No specific functional changes are documented beyond the referenced PR/changelog link.

    Security