Skip to content

feat(container): update image ghcr.io/berriai/litellm-database (v1.103.2 → v1.104.0) - #1629

Merged
gtw2 merged 1 commit into
mainfrom
renovate/ghcr.io-berriai-litellm-database-1.x
Oct 4, 2026
Merged

feat(container): update image ghcr.io/berriai/litellm-database (v1.103.2 → v1.104.0)#1629
gtw2 merged 1 commit into
mainfrom
renovate/ghcr.io-berriai-litellm-database-1.x

Conversation

@banjo-bot

@banjo-bot banjo-bot Bot commented Oct 4, 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-database (source) minor v1.103.2 → v1.104.0

Release Notes

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

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

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekend"
  • 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 CLI.

banjo-bot[bot]
banjo-bot Bot commented Oct 4, 2026
View reviewed changes
Comment thread kubernetes/apps/llm/litellm/app/litellmproxy.yaml
# restore cannot resurrect a model that was deleted from git.
applyMode: file
image: ghcr.io/berriai/litellm-database:v1.103.2@sha256:bf6d8e366f41dfe44bffad59d996f4753710e0529e5ff648c2305829835c2ab7
image: ghcr.io/berriai/litellm-database:v1.104.0@sha256:fbe28229d2d02181c0a7d9df9599de614b491f3d897d2d7da18404f088310218

@banjo-bot banjo-bot Bot Oct 4, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

v1.104.0 (backported to v1.103.3 too) flips ENFORCE_PRISMA_MIGRATION_CHECK to default true: a failed Prisma migration at boot now exits 1 instead of letting the pod start in a degraded state (BerriAI/litellm#44205, #44206). This deployment runs replicas: 2 against a shared postgres17 DB with no ENFORCE_PRISMA_MIGRATION_CHECK or USE_V2_MIGRATION_RESOLVER override here, so it's relying entirely on upstream defaults for safe concurrent migration on rollout. The v2 resolver is also now default (#42105) with its own replica-coordination fix (#40932), which is what makes concurrent migration from 2 replicas safe in the first place — but crossing this enforcement default-flip for the first time is exactly where a pre-existing partially-applied migration (e.g. the two SpendLogs index migrations rewritten in #44205) would now block startup instead of being tolerated. Worth watching the rollout for CrashLoopBackOff; if it happens, the fix is upstream's SpendLogs index runbook + prisma migrate resolve --applied <name>, not a config change here.

@banjo-bot

banjo-bot Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor Author

Verdict: Safe to merge

Reviewed the litellm-database bump v1.103.2 → v1.104.0 in kubernetes/apps/llm/litellm/app/litellmproxy.yaml (only file changed). Checked both the v1.104.0 and the intermediate v1.103.3 upstream release notes (the latter is a pure backport/chore release) against this repo's config: 2 replicas, shared postgres17 DB, Redis-backed router/cache, SSO via Authentik, store_model_in_db: false.

Breaking changes:

  • [litellm] v1.103.2 ➔ v1.104.0: ENFORCE_PRISMA_MIGRATION_CHECK now defaults to true, so a failed Prisma migration at boot exits 1 instead of starting the pod in a degraded state, introduced in v1.104.0 (backported to v1.103.3). Affects kubernetes/apps/llm/litellm/app/litellmproxy.yaml:11 (replicas: 2 against a shared DB, no override set). This pairs with the v2 migration resolver becoming the default in the same release (feat(proxy): default to the v2 migration resolver BerriAI/litellm#42105) plus its replica-coordination fix (#40932), which together are what make concurrent-replica migration startup safe — but it's the first upgrade to cross the enforcement default-flip, and a pre-existing partially-applied migration (e.g. the two SpendLogs index migrations rewritten in #44205) would now block pod startup instead of being silently tolerated. Fix: not a config change, just watch the rollout for CrashLoopBackOff; if it happens, see the upstream SpendLogs index runbook and prisma migrate resolve --applied <name>, or temporarily set ENFORCE_PRISMA_MIGRATION_CHECK=false to confirm that's the cause.
  • [litellm] v1.103.2 ➔ v1.104.0: proxy now refuses to start with an unset, empty, or publicly-known master key (feat(proxy)!: refuse to start with an unset, empty, or publicly known master key BerriAI/litellm#42019), introduced in v1.104.0. Affects kubernetes/apps/llm/litellm/app/litellmproxy.yaml via apiAccess.masterKeyRef → the litellm Secret's LITELLM_MASTER_KEY, sourced from 1Password. Not verifiable from the repo, but worth a quick check that the stored value isn't a known placeholder like sk-1234 (which upstream's own shipped examples used until #42011) before merging.

Sources consulted:

@banjo-bot

banjo-bot Bot commented Oct 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Note

No rendered changes.

konflate 0.6.4 · rendered 42ed61f · full diff →

@gtw2
gtw2 merged commit fc74346 into main Oct 4, 2026
8 checks passed
@banjo-bot
banjo-bot Bot deleted the renovate/ghcr.io-berriai-litellm-database-1.x branch October 4, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

area/kubernetes type/minor

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@gtw2