Repository navigation
feat(container): update image ghcr.io/berriai/litellm (v1.103.2 ➔ v1.104.0) - #8117
Conversation
drag0n141-bot
Bot
added
renovate/container
type/minor
area/kubernetes
--- 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.2@sha256:f63fb81b831b170ec16851e23c36ac5bf52ef106b271406429524a2ed730bbfd
+ image: ghcr.io/berriai/litellm:v1.104.0@sha256:625981c83410a3ea68eb0697590a57ec1d764d634514d54fa5db0591077ee839
litellmSettings:
cache: true
cache_params:
host: os.environ/REDIS_HOST
port: os.environ/REDIS_PORT
type: redis |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
litellm: v1.103.2 → v1.104.0
Verdict: Safe to merge
This is a minor version bump of the ghcr.io/berriai/litellm proxy image (intermediate release v1.103.3 was fix/maintenance-only, no breaking changes).
The one notable breaking change in v1.104.0 is feat(proxy)!: refuse to start with an unset, empty, or publicly known master key (blocks unset/empty keys and the documented default sk-1234, exits with code 3 if violated). This repo's LITELLM_MASTER_KEY is sourced from 1Password via kubernetes/apps/ai/litellm/app/externalsecret.yaml and injected via secretKeyRef in kubernetes/apps/ai/litellm/app/litellmproxy.yaml, so it is already a real, non-default secret — this check should pass without any changes.
Other v1.104.0 changes (password policy/breached-password detection, native Rust caching/secret-manager backends, new model pricing, telemetry flag removal) don't intersect with anything configured in kubernetes/apps/ai/litellm/app/ (no telemetry flags, no password-auth UI usage, no affected cache/secret backends in use here).
Sources consulted:
- https://github.com/BerriAI/litellm/releases/tag/v1.104.0
- https://github.com/BerriAI/litellm/releases/tag/v1.103.3
- BerriAI/litellm#42019
🤖 Generated with Claude Code
1 participant
This PR contains the following updates:
v1.103.2→v1.104.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
BerriAI/litellm (ghcr.io/berriai/litellm)
v1.104.0Compare 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
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.