chore: rebuild Admin UI bundle

[yuneng-berri]

TLDR

Problem this solves:

• Committed Admin UI bundle had drifted behind dashboard source
• Proxy serves stale pages until someone regenerates the export

How it solves it:

• Ran ui/litellm-dashboard/build_release_ui.sh on staging
• Commits only regenerated litellm/proxy/_experimental/out/ artifacts

User Flow

Before: an admin hitting the proxy's bundled UI gets pages built from older dashboard source

1. They start the proxy and open http://localhost:4000/ui/
2. The page loads assets under _next/static/TeJ852IBdcKgsOMzGKY73/
3. Recent dashboard work, including the newly added provider logos, is missing from what they see

After: the same URL serves the freshly exported bundle

1. They start the proxy and open http://localhost:4000/ui/
2. The page now loads assets under _next/static/0cE25rDXvGu3tj4HWOGKy/
3. Models & Endpoints, Keys, Logs and Teams all render with the current dashboard build, no console 404s

Relevant issues

Linear ticket

Pre-Submission checklist

• I have added meaningful tests
• The handful of test files covering my change pass locally, e.g. uv run pytest tests/test_litellm/<your_test_file>.py -v
• My PR passes all required CI/CD checks (e.g., lint, schema.d.ts sync check, etc.)
• 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

The first two are deliberately unchecked: every file in this PR is generated output from the Next.js export, so there is no source behavior to write tests against and no mapped test file to run. CI is unchecked because it has not reported yet at the time of opening

Screenshots / Proof of Fix

Base branch: litellm_internal_staging at 11cbe472ac
Artifact commit: 9b8d621b20f2d52ddc7288ba004876d0c7a03787
Node: v24.19.0 (from ui/litellm-dashboard/.nvmrc)
Build id: TeJ852IBdcKgsOMzGKY73 -> 0cE25rDXvGu3tj4HWOGKy

After (9b8d621)

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 matches the one in this diff: curl -s http://localhost:4000/ui/ | grep -o '_next/static/[A-Za-z0-9_-]*/_buildManifest.js' and expect 0cE25rDXvGu3tj4HWOGKy
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. Run git status --short and expect no output, showing the proxy did not overwrite the committed artifacts

Type

🚄 Infrastructure

Caveats (if any)

• Diff is ~800 content-hashed files, all generated

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

[greptile-apps]

Too many files changed for review (812 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-21ee3c (9b8d621) with litellm_internal_staging (490c9f9)¹}

Footnotes

1. No successful run was found on litellm_internal_staging (11cbe47) during the generation of this report, so 9036da5 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩