Repository navigation
fix(container): update image ghcr.io/berriai/litellm (v1.103.1 ➔ v1.103.2) - #8074
Merged
Merged
Conversation
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 |
There was a problem hiding this comment.
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): fixeskey_alias/user_emailshowing asnullfor CLI session keys (fromlitellm-proxy login) on the/user/daily/activity/aggregatedBI 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
safeguardspassthrough (backport of upstream#42152,#42288): fixes the native/v1/messagesendpoint dropping thesafeguardsfield, which broke Claude Code's auto mode when pointed at a litellm gateway viaANTHROPIC_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/completionsendpoint, not the native Anthropic Messages passthrough. Themodel: anthropic/...values in theLiteLLMModelCRDs 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): fixesAuthorizationheader stripping on config-defined pass-through endpoints whenSTORE_MODEL_IN_DB=true. Not applicable — this deployment has nopass_through_endpointsconfigured and doesn't setSTORE_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:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.103.1→v1.103.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
BerriAI/litellm (ghcr.io/berriai/litellm)
v1.103.2Compare 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:
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:
Expected output:
What's Changed
Full Changelog: BerriAI/litellm@v1.103.1...v1.103.2
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 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.
This PR has been generated by Mend Renovate CLI.