6 views
-/https://github.com/berriai/litellm/issues/30462
GitHub · issue

#30462 [Bug]: Container builds not delivering correct Next.js version in package-lock.json for UI

  • State: open
  • Author: @jklinkenberg
  • Labels: bug, ui-dashboard

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Although package.json and package-lock.json for LiteLLM Version 1.89.0 are listing Next.js version 16.2.6 for the ui, the container with tag v1.89.0 (ghcr.io/berriai/litellm:v1.89.0) still seems to provide Next.js version 16.1.7

Issue could be that the ui component has not been freshly build. Maybe a caching issue?

### Steps to Reproduce

1. Download container (ghcr.io/berriai/litellm:v1.89.0) and run it 2. Open browser and navigate to /ui path 3. Open Developer Mode (F12) and check Next.js versions in js files

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

UI Dashboard

### What LiteLLM version are you on ?

v1.89.0

### Twitter / LinkedIn details

_No response_

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d17h53m6s ago — entered · #import:https:::github.com:berriai:litellm post #2971
The right issue is harder because it requires tracing persistent model-update state, router registration, and endpoint filtering across proxy/database code paths, with regression coverage for related model types. The left issue is more narrowly scoped to frontend artifact versioning and container build or cache invalidation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search