Skip to content

fix(container): update image ghcr.io/berriai/litellm-database (v1.103.0 → v1.103.2) - #1586

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

gtw2 merged 1 commit into
mainfrom
renovate/ghcr.io-berriai-litellm-database-1.x

Conversation

@banjo-bot

@banjo-bot banjo-bot Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

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

Release Notes

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

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

v1.103.1

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

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

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

Full Changelog: BerriAI/litellm@v1.103.0...v1.103.1


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

banjo-bot Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor Author

Verdict: Safe to merge

Reviewed the patch bump v1.103.0 → v1.103.2 (spans v1.103.1 and v1.103.2). The diff itself only changes the image tag/digest in kubernetes/apps/llm/litellm/app/litellmproxy.yaml.

Checked every backported fix listed in the two releases against this repo's LiteLLM config (kubernetes/apps/llm/litellm/app/*.yaml):

No removed/renamed flags or env vars affect this config, and no comment-documented tuning decisions in this repo's manifests reference anything touched by these releases.

Sources consulted:

🤖 Generated with Claude Code

@gtw2
gtw2 merged commit 6dbcd83 into main Oct 2, 2026
7 checks passed
@banjo-bot
banjo-bot Bot deleted the renovate/ghcr.io-berriai-litellm-database-1.x branch October 2, 2026 23:24
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.

1 participant