[Feature]: Proper release/github images

[kreatoo]

The Feature

Seperate dev, nightly and stable releases to seperate GitHub images

Motivation, pitch

Right now the GitHub images are a mess. There are multiple types of images (nightly, dev and pip-dev whatever that is), it is really hard to parse using tools like Renovate and is not semver compatible at all.

Not to mention GitHub releases which have dev releases as latest and not marked as pre-release.

Are you a ML Ops Team?

No

Twitter / LinkedIn details

No response

[tlecomte]

Addressing this would help a lot when using bots such as Renovate or Dependabot to update Docker images automatically. Right now LiteLLM requires a manual configuration using regexes (for example with https://docs.renovatebot.com/modules/versioning/regex/) to parse the tags. Following semver would nicely allow for transparent support.

(we actually also had to fix Renovate to support underscores in image tags: renovatebot/renovate#35896)

[krrishdholakia]

What would the new docker images look like? it seems like the semvar incompatibility is caused by the additional -[tag] at the end?

[krrishdholakia]

Moving to discussion for now

[tobiasge]

I would like to see tags on the images that make following the versions easier. For example when v1.70.0 is released the image get's tagged with v1.70.0, v1.70 and v1. When v1.70.1 is released that new image will be tagged with v1.70.1, v1.70 and v1.

[kreatoo]

Instead of using tags to distinguish every type of release, we could just do
ghcr.io/berriai/litellm
ghcr.io/berriai/litellm-nightly
and
ghcr.io/berriai/litellm-dev.

Example;

Instead of ghcr.io/berriai/litellm:main-v1.69.1-nightly, it would be ghcr.io/berriai/litellm-nightly:v1.69.1
or
Instead of ghcr.io/berriai/litellm:main-v1.67.0-stable, we could do ghcr.io/berriai/litellm:v1.67.0
and so on.

I don't know if the main- part is needed but if so we could name it like ghcr.io/berriai/litellm-main-nightly

Atleast that is what I have thought of for now, open to suggestions, thanks!

[krrishdholakia]

This is a pretty nice approach.

The change would be here -

litellm/.github/workflows/ghcr_deploy.yml

Line 117 in 61d7704

${{ github.event.inputs.release_type == 'stable' && format('{0}/berriai/litellm:main-{1}', env.REGISTRY, github.event.inputs.tag) || '' }},

A PR here is welcome!

[krrishdholakia]

probably do both for now, for backwards compatibility

[tlecomte]

For the Docker images, I believe it would be even nicer for dependency management bots to avoid the 'v' prefix

[krrishdholakia]

@tlecomte curious, do you have any good reference docker images I can look at for understanding best practices here?

[tlecomte]

Good question.

Renovate docs for Docker mentions "SemVer-like" versions here: https://docs.renovatebot.com/modules/versioning/docker/

Their unit tests only check versions without any prefix: https://github.com/renovatebot/renovate/blob/main/lib/modules/versioning/docker/index.spec.ts but I don't know exactly if that means that they don't support prefixes at all.

Dependabot docs refer to support for prefixes, but with dashes as a separator: https://github.com/dependabot/dependabot-core/blob/main/docker/README.md#semver

[kreatoo]

Hey! Forgot to send this here, I opened a PR, see here: #10927