chore: rebuild Admin UI bundle from litellm_internal_staging

[yuneng-berri]

TLDR

Problem this solves:

• Shipped Admin UI bundle was last built 2026-08-08
• 223 dashboard source commits landed since, none served
• Nothing rebuilds the committed bundle automatically

How it solves it:

• Reran ui/litellm-dashboard/build_release_ui.sh on current staging
• Commit holds only regenerated litellm/proxy/_experimental/out/ artifacts

User Flow

Before: a proxy admin browsing the Admin UI sees the dashboard as it looked on 2026-08-08, so a week of shipped UI work is invisible to them

1. They start the proxy and open http://localhost:4000/ui/
2. The page loads its assets from _next/static/HynDchE8aLeEewsZVNDO8/
3. Every page renders the 2026-08-08 dashboard, so anything shipped after that date is missing

After: the same admin sees the dashboard as it stands on current staging

1. They start the proxy and open http://localhost:4000/ui/
2. The page loads its assets from _next/static/TeJ852IBdcKgsOMzGKY73/
3. Models & Endpoints, Keys, Logs and Teams render the current dashboard with no blank panels and no asset 404s in the console

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)

No tests are added here on purpose. Every file in this PR is generated output from the Next.js export, so there is no hand-written code to cover, and the dashboard's own tests already run against ui/litellm-dashboard/src, which this PR does not touch

Screenshots / Proof of Fix

Shared setup, run once per side after checking out the stated 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

Before (992a812)

1. curl -s http://localhost:4000/ui/ | grep -o '_next/static/[A-Za-z0-9_-]*/_buildManifest.js' prints the stale HynDchE8aLeEewsZVNDO8
2. Open http://localhost:4000/ui/ and click Models & Endpoints, Keys, Logs, Teams: the 2026-08-08 dashboard renders, without the UI work merged since
3. git status --short prints nothing, so the proxy served the committed bundle rather than regenerating one

After (b3077c9)

1. curl -s http://localhost:4000/ui/ | grep -o '_next/static/[A-Za-z0-9_-]*/_buildManifest.js' prints the new TeJ852IBdcKgsOMzGKY73
2. Open http://localhost:4000/ui/ and click the same four pages: the current dashboard renders, with no blank panels and no 404s in the browser console
3. git status --short prints nothing, so the proxy served this PR's committed bundle

Type

🚄 Infrastructure

Caveats (if any)

• 887 generated files; only the build id is worth reading
• Built from staging 992a8123ac on node v24.19.0

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 (887 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-1e15d9 (b3077c9) with litellm_internal_staging (74a1bed)¹}

Footnotes

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