You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
feat(proxy): resolve Cursor thinking/fast model-name suffixes on /cursor/chat/completions by @mateo-berri in #35554
fix(team-callbacks): actually stop logging when disable_logging is called by @yucheng-berri in #35520
refactor(lint): drop redundant !s f-string conversion flags and fix displaced import-group comments by @mateo-berri in #35546
What changed? Patch bump (v1.96.0 → v1.96.2) of ghcr.io/berriai/litellm-database in kubernetes/apps/ai/litellm/app/deployment.yaml (both the db-migrate initContainer and the litellm container), plus the paired grafanadashboard.yaml dashboard-source URL tag (Renovate-linked via the # renovate: datasource=docker depName=... comment).
Breaking change / deprecation flagged upstream?v1.96.2's release notes (gh api repos/BerriAI/litellm/releases/tags/v1.96.2) show it's a backport-only release on top of v1.96.0: it cherry-picks upstream PR #36011, fix(proxy)!: apply request-parameter checks consistently across body, path and form inputs — a security fix (closes an SSRF-adjacent gap where path/form-supplied destinations and connection tests could bypass request-parameter/credential checks that only covered request bodies before). The ! marks it conventional-commits-breaking, but three admin opt-outs are preserved for anyone relying on the old permissive behavior. (v1.96.1 itself was burned by a PyPI storage failure and re-cut as v1.96.2 with identical content — no separate git tag exists for .1.)
Does this repo touch the affected behavior? No. configmap.yaml sets no model_list (models live in the DB per store_model_in_db: true) and doesn't use any of the three preserved opt-outs (path-based deployment overrides, bracket-notation form metadata, or per-model connection-test credential sharing). The stricter default behavior is a net positive here, not a regression risk.
Manifest/dashboard-URL agreement? Both deployment.yaml image refs and the grafanadashboard.yaml URL consistently point to v1.96.2 — no drift, no leftover pins. Independently verified raw.githubusercontent.com/BerriAI/litellm/v1.96.2/.../grafana_dashboard.json returns HTTP 200, and gh api repos/BerriAI/litellm/tags confirms a real v1.96.2 git tag exists (this pairing has drifted before on past litellm PRs — not the case here).
Verdict: merge — clean patch bump carrying an upstream security fix, no behavior in this repo depends on what changed, and the dashboard-URL/image-tag pairing is verified in sync.
Note on the task title vs. actual PR content: the title given to me (v1.96.0 ➔ v1.96.2, patch bump) is stale — Renovate has since rebased this same PR/branch to v1.96.0 ➔ v1.97.0 (minor). The commit and PR body on GitHub confirm v1.97.0 is what's actually being merged, so the review below is against that.
What changed?ghcr.io/berriai/litellm-databasev1.96.0 → v1.97.0 — minor bump. Touches deployment.yaml (both db-migrate initContainer and litellm container image) and grafanadashboard.yaml's dashboard URL tag.
Breaking changes/deprecations? No. Best-available changelog for this range (v1.97.0-rc.1's "What's Changed") is all fix/feat/test/ci entries — no !: breaking-change markers. Nothing touches Prisma/migrations, DISABLE_SCHEMA_UPDATE, auth env vars, or the /health/readiness and /health/liveliness probe paths this repo relies on.
Does this repo call the changed behavior? Checked deployment.yaml and configmap.yaml — nothing in the changelog intersects store_model_in_db, the db-migrate prisma flow, or probe endpoints used here.
Manifest/lockfile agreement?deployment.yaml's two image refs and grafanadashboard.yaml's Renovate-tracked URL all consistently bump to v1.97.0 — no drift between them. However, independently verified against upstream (per [[litellm_dashboard_url_tag_drift]] memory — this bug has now recurred a third time): ghcr.io/berriai/litellm-database:v1.97.0 pulls fine (ghcr manifest 200), but the git tag v1.97.0does not exist yet on BerriAI/litellm — only v1.97.0-dev.1/2 and v1.97.0-rc.1 pre-release tags, with v1.98.0-dev.2 already published ahead of it. Confirmed directly: raw.githubusercontent.com/BerriAI/litellm/v1.97.0/cookbook/.../grafana_dashboard.json → 404. Merging as-is will break grafana-operator's reconcile of the GrafanaDashboard CR.
Verdict: hold — the container image bump itself is safe (no breaking changes, nothing in this repo touches the affected code paths), but the grafanadashboard.yaml URL bump to v1.97.0 404s because BerriAI hasn't cut that git tag yet. Merge only after either (a) reverting/pinning the dashboard URL to v1.96.0 (last known-good tag) while still bumping the image, or (b) waiting for Renovate to catch up once BerriAI actually cuts the v1.97.0 git tag.
Kylin · task t_7207282f
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
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.96.0→v1.97.0Release Notes
BerriAI/litellm (ghcr.io/berriai/litellm-database)
v1.97.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: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.