Skip to main content

2 posts tagged with "release"

View All Tags

LiteLLM version support: focusing on the four most recent stable lines

Yuneng Jiang
Senior SWE @ LiteLLM

Starting Monday, June 29, 2026, LiteLLM will only actively support the four most recent stable minor lines. Here's what's changing and what it means for you.

Why we're doing this​

Maintaining older lines means carrying every fix back to keep them all in parity. That overhead grows with the number of lines we keep alive, not the number of fixes we make. Our focus is ensuring the most up-to-date product offerings are stable and working for you. Because of this, LiteLLM is focusing on the four most recent stable minor lines going forward.

How the rolling window works​

This shift in focus takes effect Monday, June 29, 2026.

A minor line is a release series written as 1.89.x, covering every patch in it: 1.89.0, 1.89.1, 1.89.2, and any later ones. We support the four most recent lines and every patch inside each of them.

Today the four supported lines are 1.89.x, 1.88.x, 1.87.x, and 1.86.x. Everything 1.85.x and earlier has reached end of life and will no longer actively receive updates. The window rolls forward: when 1.90.x ships, 1.86.x rolls out and the supported set becomes 1.90.x, 1.89.x, 1.88.x, and 1.87.x. With a new line about every week, that works out to roughly a month of coverage per line.

What this means for you​

To stay supported, pin to a line and take its patches, then move up before it ages out. Patching within a line is a drop-in; moving up a line is where you'd check the release notes for changes. Enterprise customers who need longer coverage can reach out, and for rare high-severity issues we'll use our judgment and may patch outside the window.

How to stay current​

The best way to stay up to date on these changes is to bookmark our release notes. We update it as new versions ship, so you can see the latest stable line and the three behind it that are still supported.

LiteLLM release versioning is changing: standard names, MINOR for weekly, PATCH for hotfixes

Yuneng Jiang
Senior SWE @ LiteLLM

Last Updated: May 2026

main-stable is deprecated — migrate to :latest by June 30, 2026

The legacy main-stable Docker tag still advances each week so existing deployments keep working, but we plan to stop publishing it on June 30, 2026 (end of Q2). Going forward, :latest is the canonical rolling pointer to the newest stable image — it advances automatically when each stable ships and matches the standard Docker convention.

main-stable carries over from the previous naming scheme and doesn't fit modern conventions: it mixes "main" (typically a development branch) with "stable" (a release channel), and has no PyPI counterpart.

Migration:

  • Rolling stable (Docker) → ghcr.io/berriai/litellm:latest
  • Reproducible pin (Docker) → ghcr.io/berriai/litellm:1.84.0
  • Reproducible pin (PyPI) → pip install litellm==1.84.0

This banner will be updated with reminders as the cutover approaches.

LiteLLM release version names are changing. Two pain points have been driving this:

1. The -stable and -nightly suffixes aren't standard.

Versions like v1.83.3-stable and v1.83.0-nightly don't match PEP 440 (PyPI) or SemVer 2.0 (Docker / Helm) conventions. Users expecting standard version strings get confused, and tooling that classifies versions has to special-case the suffix.

2. Weekly releases were bumping PATCH, leaving no room for actual hotfixes.

Under the old model, each scheduled weekly release bumped the PATCH number: 1.83.0 -> 1.83.1 -> 1.83.2 -> 1.83.3. When a real hotfix was needed for 1.83.3, the next PATCH (1.83.4) was already reserved for the following week's release. The workaround on Docker was v1.83.3-stable.patch.1 - but PyPI doesn't accept that syntax, so a hotfix that needed both a Docker image and a Python wheel had no clean way to ship.