chore: rebuild Admin UI bundle for the 2026-08-08 release

[yuneng-berri]

TLDR

Problem this solves:

• The proxy serves a committed UI bundle nothing rebuilds automatically
• That bundle is a week stale, from 2026-08-01
• 93 dashboard source commits landed since it was cut
• Admins see last week's UI, not current source

How it solves it:

• Regenerates litellm/proxy/_experimental/out/ from staging HEAD
• One commit, generated output only, no source edits
• Build id moves VCvPhLLOUp92Yx-E-CVlV to HynDchE8aLeEewsZVNDO8
• First bundle built on node 24, matching the pinned toolchain

User Flow

Before: a proxy admin opening the Admin UI gets the bundle exported on 2026-08-01, so a week of dashboard work is invisible to them even though it is merged

1. They start the proxy and open http://localhost:4000/ui/
2. The page loads assets under _next/static/VCvPhLLOUp92Yx-E-CVlV/
3. They click through Cost Optimization, MCP Servers, Hooks, Playground and Guardrails
4. Each page renders as it did on 2026-08-01, missing changes merged in the week since
5. Reaching the same pages on the dev server at http://localhost:3000 shows different, newer screens for the same proxy

After: the same admin gets the dashboard as it exists on staging today, and the served UI matches the dev server

1. They start the proxy and open http://localhost:4000/ui/
2. The page loads assets under _next/static/HynDchE8aLeEewsZVNDO8/
3. They click through the same pages and see the current versions of each
4. Panels render with no blank regions and the browser console logs no 404s for chunks
5. The proxy-served UI and the dev server now agree

Relevant issues

Linear ticket

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have added meaningful tests
• My PR passes all CI/CD checks (e.g., lint, format, unit tests)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

On the first box: every file here is Next.js export output, so there is no hand-written code to test. The check that matters is that a running proxy serves this exact bundle, which is what the proof below exercises

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

Screenshots / Proof of Fix

The thing worth proving is that the proxy serves this committed bundle rather than a local rebuild, so run these against a checkout of this branch with no dev server involved

1. Start the proxy: python litellm/proxy/proxy_cli.py --config litellm/proxy/dev_config.yaml --detailed_debug --reload --use_v2_migration_resolver 2>&1 | tee litellm.log
2. Confirm the served build id is the one in this diff: curl -s http://localhost:4000/ui/ | grep -o '_next/static/[A-Za-z0-9_-]*/_buildManifest.js', which should print HynDchE8aLeEewsZVNDO8 and not VCvPhLLOUp92Yx-E-CVlV
3. Open http://localhost:4000/ui/ and click through Models & Endpoints, Keys, Logs and Teams, watching for blank panels or 404s in the browser console
4. Visit http://localhost:4000/ui/?page=logs directly and confirm the table renders
5. Run git status --short afterwards and confirm it prints nothing, showing the proxy did not overwrite the committed artifacts

Type

🚄 Infrastructure

Changes

Regenerated litellm/proxy/_experimental/out/ by running ui/litellm-dashboard/build_release_ui.sh on this branch. 710 files, all of them Next.js export output: content-hashed chunks, the per-route HTML, and the build-id directory rename. No source file is touched

Provenance, so a reviewer can reproduce it:

• Base: litellm_internal_staging at 97a59c8c90
• Artifact commit: 84d63cbdcff2b3cbf7b2434c43f7405d3b123358
• Node: v24.19.0, npm 11.17.0, Next.js 16.2.11 with Turbopack

Worth flagging: the previous bundle was built on node v20.20.2, and this is the first one built on node 24. The dashboard's .nvmrc pins 24.19.0 and its engines now require node >=24.14.1 with engine-strict=true, so node 20 can no longer install the dependencies at all. That toolchain move, not just a week of source drift, is part of why the diff is broad

The one build warning is pre-existing and unrelated: Turbopack does not encode AVIF, so public/assets/logos/enkrypt_ai.avif is emitted unoptimized

Final Attestation

• The tests check the right things, including the edge cases, and regressions in the respective real-world customer use-cases are not possible after this PR

Left unchecked deliberately: this PR adds no tests, because it adds no hand-written code. The regression surface is the dashboard itself, and the click-through in the proof section is how it gets covered

[greptile-apps]

Too many files changed for review (710 files, 100 file limit).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[codspeed-hq]

Merging this PR will not alter performance

✅ 31 untouched benchmarks

---

_{Comparing litellm_/release-ui-build-528a42 (84d63cb) with litellm_internal_staging (97a59c8)}