Skip to content

feat(container-image): update ghcr.io/berriai/litellm-non_root ( v1.92.0 → v1.94.1 ) - #1467

Open
robottoms-up[bot] wants to merge 1 commit into
masterfrom
renovate/ghcr.io-berriai-litellm-non_root-1.x
Open

feat(container-image): update ghcr.io/berriai/litellm-non_root ( v1.92.0 → v1.94.1 )#1467
robottoms-up[bot] wants to merge 1 commit into
masterfrom
renovate/ghcr.io-berriai-litellm-non_root-1.x

Conversation

@robottoms-up

@robottoms-up robottoms-up Bot commented Jul 19, 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-non_root (source) minor v1.92.0v1.94.1

Release Notes

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

v1.94.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.94.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.94.0/cosign.pub \
  ghcr.io/berriai/litellm:v1.94.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 America/New_York)

  • 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 these updates again.


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

This PR has been generated by Mend Renovate.

@robottoms-up

robottoms-up Bot commented Jul 19, 2026

Copy link
Copy Markdown
Contributor Author
Kustomization diff
@@ spec.values.controllers.litellm.containers.app.image.tag @@
# helm.toolkit.fluxcd.io/v2/HelmRelease/ai/litellm
! ± value change
- v1.92.0@sha256:4e8b7e8e978907fce0270de3e8b4c5ab022a215630b8e1534ac42e3a8a67694e
+ v1.94.1@sha256:9c42998e8f82b1f99af2ce18939a510732a481e03ef49032af1f03098fc76dd7

HelmRelease diff
@@ spec.template.spec.containers.app.image @@
# apps/v1/Deployment/ai/litellm
! ± value change
- ghcr.io/berriai/litellm-non_root:v1.92.0@sha256:4e8b7e8e978907fce0270de3e8b4c5ab022a215630b8e1534ac42e3a8a67694e
+ ghcr.io/berriai/litellm-non_root:v1.94.1@sha256:9c42998e8f82b1f99af2ce18939a510732a481e03ef49032af1f03098fc76dd7

Diff created by flateWorkflow run

@robottoms-up
robottoms-up Bot force-pushed the renovate/ghcr.io-berriai-litellm-non_root-1.x branch from 59cefdc to 22c0c14 Compare July 28, 2026 21:03
@robottoms-up robottoms-up Bot changed the title feat(container-image): update ghcr.io/berriai/litellm-non_root ( v1.92.0 → v1.93.0 ) feat(container-image): update ghcr.io/berriai/litellm-non_root ( v1.92.0 → v1.94.0 ) Jul 28, 2026
@robottoms-up
robottoms-up Bot force-pushed the renovate/ghcr.io-berriai-litellm-non_root-1.x branch from 22c0c14 to 85a7e63 Compare July 31, 2026 00:03
@robottoms-up robottoms-up Bot changed the title feat(container-image): update ghcr.io/berriai/litellm-non_root ( v1.92.0 → v1.94.0 ) feat(container-image): update ghcr.io/berriai/litellm-non_root ( v1.92.0 → v1.94.1 ) Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants