chore: rebuild Admin UI bundle

[yuneng-berri]

TLDR

Problem this solves:

• Committed Admin UI bundle is stale vs dashboard source
• Proxy serves that bundle; nothing rebuilds it automatically

How it solves it:

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

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

  Every file in this PR is generated output from next build; there is no hand-written code here to test. The dashboard's own test suite already covers the source that produced it, so adding tests against build artifacts would assert nothing

• 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)

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 demonstrating is that a running proxy serves this committed bundle rather than a local rebuild; the served build id should match the one introduced in this diff

1. Start the proxy at this commit

   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 new one (VCvPhLLOUp92Yx-E-CVlV, replacing 8bC_aTV0H1nUtrFDXkfaB)

   curl -s http://localhost:4000/ui/ | grep -o '_next/static/[A-Za-z0-9_-]*/_buildManifest.js'
   

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. Re-run git status --short and confirm it prints nothing, showing the proxy did not overwrite the committed artifacts

Type

🚄 Infrastructure

Changes

Regenerated the Next.js static export the proxy serves from litellm/proxy/_experimental/out/. Nothing else; no source file is touched

• Base branch: litellm_internal_staging, built from ceaf556b2e7eab737517fc4e494816e4b4359c71
• Artifact commit: 8569df8bb6968aa0b78899d7b5aabadd9383f934
• Node version: v20.20.2
• Build id: 8bC_aTV0H1nUtrFDXkfaB -> VCvPhLLOUp92Yx-E-CVlV
• 459 files changed, all under litellm/proxy/_experimental/out/

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. (459 files found, 100 file limit)

Bypass the limit by tagging @greptile-apps to review.

[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-9536bb (8569df8) with litellm_internal_staging (68b1e03)¹}

Footnotes

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