Skip to content

feat(container): update image ghcr.io/berriai/litellm (v1.97.0 → v1.99.1) - #1894

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-berriai-litellm-1.x
Open

feat(container): update image ghcr.io/berriai/litellm (v1.97.0 → v1.99.1)#1894
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ghcr.io-berriai-litellm-1.x

Conversation

@renovate

@renovate renovate Bot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
ghcr.io/berriai/litellm (source) minor v1.97.0v1.99.1

Release Notes

BerriAI/litellm (ghcr.io/berriai/litellm)

v1.99.1

Compare Source

Docker-only release

This release ships container images only. There is no PyPI package for 1.99.1.

pip install litellm==1.99.1 will not resolve — install the images below, or stay on 1.99.0 on PyPI. The git tag and this release exist so the images are traceable to an exact commit.

Image Tags
ghcr.io/berriai/litellm · docker.io/litellm/litellm 1.99.1, v1.99.1
ghcr.io/berriai/litellm-database · docker.io/litellm/litellm-database 1.99.1, v1.99.1
ghcr.io/berriai/litellm-non_root · docker.io/litellm/litellm-non_root 1.99.1, v1.99.1

This is the newest stable image, so the rolling latest and main-stable image tags now point at 1.99.1.

It carries one fix on top of 1.99.0: OpenTelemetry v2 spans now emit cache token counts (gen_ai.usage.cache_creation.input_tokens and gen_ai.usage.cache_read.input_tokens) alongside the cache cost that was already reported. If you compute spend from OTel token counts rather than from LiteLLM's own cost fields, prompt-caching workloads were previously under-counted.


Verify Docker Image Signature

All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53.

Verify using the pinned commit hash (recommended):

A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \
  ghcr.io/berriai/litellm:v1.99.1

Verify using the release tag (convenience):

Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/v1.99.1/cosign.pub \
  ghcr.io/berriai/litellm:v1.99.1

Expected output:

The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - The signatures were verified against the specified public key

What's Changed

Full Changelog: BerriAI/litellm@v1.99.0...v1.99.1

v1.99.0

Compare Source

Verify Docker Image Signature

All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53.

Verify using the pinned commit hash (recommended):

A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \
  ghcr.io/berriai/litellm:v1.99.0

Verify using the release tag (convenience):

Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/v1.99.0/cosign.pub \
  ghcr.io/berriai/litellm:v1.99.0

Expected output:

The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - The signatures were verified against the specified public key

What's Changed

Note

PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions github-actions Bot added the area/kubernetes Changes made in the kubernetes directory label Aug 22, 2026
@renovate
renovate Bot force-pushed the renovate/ghcr.io-berriai-litellm-1.x branch from 4b9969e to 7759080 Compare September 1, 2026 12:02
@renovate renovate Bot changed the title feat(container): update image ghcr.io/berriai/litellm (v1.97.0 → v1.98.0) feat(container): update image ghcr.io/berriai/litellm (v1.97.0 → v1.99.0) Sep 1, 2026
@renovate
renovate Bot force-pushed the renovate/ghcr.io-berriai-litellm-1.x branch from 7759080 to 5eac731 Compare September 2, 2026 05:39
@renovate renovate Bot changed the title feat(container): update image ghcr.io/berriai/litellm (v1.97.0 → v1.99.0) feat(container): update image ghcr.io/berriai/litellm (v1.97.0 → v1.99.1) Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/kubernetes Changes made in the kubernetes directory renovate/container type/minor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants