LiteLLM release versioning is changing: standard names, MINOR for weekly, PATCH for hotfixes
Last Updated: May 2026
main-stable is deprecated — migrate to :latest by June 30, 2026The 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.