Skip to content

fix(container): update image ghcr.io/berriai/litellm (v1.103.1 ➔ v1.103.2) - #8074

Merged
drag0n141 merged 1 commit into
masterfrom
renovate/ghcr.io-berriai-litellm-1.x
Oct 1, 2026
Merged

drag0n141 merged 1 commit into
masterfrom
renovate/ghcr.io-berriai-litellm-1.x

Conversation

@drag0n141-bot

@drag0n141-bot drag0n141-bot Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
ghcr.io/berriai/litellm (source) patch v1.103.1 → v1.103.2

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v1.103.2

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.103.2

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.103.2/cosign.pub \
  ghcr.io/berriai/litellm:v1.103.2

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.103.1...v1.103.2


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 has been generated by Mend Renovate CLI.

@drag0n141-bot drag0n141-bot Bot added renovate/container type/patch area/kubernetes Changes made in the kubernetes directory labels Oct 1, 2026
@drag0n141-bot

drag0n141-bot Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor Author
--- kubernetes/apps/ai/litellm/app Kustomization: ai/litellm LiteLLMProxy: ai/litellm

+++ kubernetes/apps/ai/litellm/app Kustomization: ai/litellm LiteLLMProxy: ai/litellm

@@ -22,13 +22,13 @@

     valueFrom:
       secretKeyRef:
         key: LITELLM_MASTER_KEY
         name: litellm-secret
   generalSettings:
     health_check_endpoint: /v1/health
-  image: ghcr.io/berriai/litellm:v1.103.1@sha256:df15400b5b80925c45d3fd53f8f7a6c0eaa8a25a86833e1b358002e129018943
+  image: ghcr.io/berriai/litellm:v1.103.2@sha256:f63fb81b831b170ec16851e23c36ac5bf52ef106b271406429524a2ed730bbfd
   litellmSettings:
     cache: true
     cache_params:
       host: os.environ/REDIS_HOST
       port: os.environ/REDIS_PORT
       type: redis

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ghcr.io/berriai/litellm: v1.103.1 → v1.103.2

Verdict: Safe to merge

This is a patch release on the stable/1.103.x branch that backports three fixes from main:

  • CLI session key attribution (backport of upstream #40541, #43642, #43656): fixes key_alias/user_email showing as null for CLI session keys (from litellm-proxy login) on the /user/daily/activity/aggregated BI endpoint under high query load. Not applicable — this repo's litellm config (kubernetes/apps/ai/litellm/app/litellmproxy.yaml) has no CLI session/BI integration.
  • Anthropic safeguards passthrough (backport of upstream #42152, #42288): fixes the native /v1/messages endpoint dropping the safeguards field, which broke Claude Code's auto mode when pointed at a litellm gateway via ANTHROPIC_BASE_URL. Not applicable — consumers in this repo (e.g. kubernetes/apps/ai/hermes/app/resources/config.yaml) talk to litellm over the OpenAI-compatible /v1/chat/completions endpoint, not the native Anthropic Messages passthrough. The model: anthropic/... values in the LiteLLMModel CRDs just select litellm's internal provider adapter, they don't expose the native endpoint this fix targets.
  • Pass-through endpoint header forwarding (backport of upstream #43962): fixes Authorization header stripping on config-defined pass-through endpoints when STORE_MODEL_IN_DB=true. Not applicable — this deployment has no pass_through_endpoints configured and doesn't set STORE_MODEL_IN_DB.

No breaking changes, deprecations, or actionable items for this repo's usage. The image digest in the diff matches the new tag.

Sources consulted:

@drag0n141
drag0n141 merged commit 0b08ca5 into master Oct 1, 2026
11 checks passed
@drag0n141
drag0n141 deleted the renovate/ghcr.io-berriai-litellm-1.x branch October 1, 2026 07:44
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/patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant