16 views
-/https://github.com/berriai/litellm/issues/23941
GitHub · issue

#23941 LiteLLM upgrading guide

  • State: open
  • Author: @gfish213-tech
  • Labels: stale

I always facing issue when did the LiteLLM upgrade, especially on prisma side, always column missing and migration error. even i download the latest prisma schema also having issue to apply it into my current DB.

Do we have any proper guide to show us step by step how do we upgrade from 1 version to another which have new column or table added, we cannot afford to recreate DB every time new version upgrade.

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (4 events)
#0 of 0 · 31d19h23m28s ago — entered · #import:https:::github.com:berriai:litellm post #1693
-/https://github.com/berriai/litellm/issues/241234:1-/https://github.com/berriai/litellm/issues/23941⭐
The right issue is harder because it requires dependency upgrades, breaking API migration, compatibility handling, regression testing, and release validation; the left is primarily documentation and operational guidance.
#0 of 0 · 31d19h21m51s ago · #import:https:::github.com:berriai:litellm post #1719
-/https://github.com/berriai/litellm/issues/23941⭐3:1-/https://github.com/berriai/litellm/issues/25550
The upgrade work spans database migration behavior, version compatibility, deployment safety, and documentation validation, creating broader risk than a localized proxy response-filtering fix with focused tests.
#0 of 0 · 31d19h11m48s ago · #import:https:::github.com:berriai:litellm post #1874
-/https://github.com/berriai/litellm/issues/280334:1-/https://github.com/berriai/litellm/issues/23941⭐
The left issue is harder because it requires security-sensitive investigation, tracing budget/accounting enforcement across proxy flows, implementing a safe fix, and adding exploit-regression coverage. The right issue is primarily documentation and migration-process clarification, with comparatively limited implementation risk.
#0 of 0 · 31d19h10m2s ago — current · #import:https:::github.com:berriai:litellm post #1905
-/https://github.com/berriai/litellm/issues/313984:1-/https://github.com/berriai/litellm/issues/23941⭐
#31398 requires coordinated frontend, API/state, routing semantics, and safe live-switch behavior; #23941 is primarily documentation and migration-process clarification, so it carries substantially less implementation risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search