chore: rebuild Admin UI bundle for rc/1.103.0

[yuneng-berri]

TLDR

Problem this solves:

• rc/1.103.0's committed Admin UI bundle still ships the top-N usage UI
• revert(usage): remove the top-N key cap and global spend rollup code from rc/1.103.0 #43326 reverted that UI source, but the bundle is only rebuilt by hand

How it solves it:

• Rebuilds litellm/proxy/_experimental/out/ from rc/1.103.0 with build_release_ui.sh
• One commit, generated artifacts only

User Flow

Before: an admin on the rc sees Usage page notes about a top-N key cap that the backend no longer applies

1. The admin opens http://localhost:4000/ui/?page=usage on a proxy running rc/1.103.0
2. The served bundle still carries the top-N notes, such as "Only the 100 highest-spend keys of N are loaded"

After: the served UI matches the reverted source

1. The admin opens http://localhost:4000/ui/?page=usage on the same proxy
2. The page loads every key with no top-N notes

Pre-Submission checklist

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

• 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. Leave the suites (make test-unit-*, make test-unit) to CI: it finishes in ~15 minutes where a laptop takes an hour or more
• 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 (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

Every file is generated build output, so there are no tests to add. Base is rc/1.103.0, not main, because this bundle ships with that release line

Build details:

• Built from rc/1.103.0 at 4d087891010e30b30689a873f51d11de7c575804, which includes the revert in revert(usage): remove the top-N key cap and global spend rollup code from rc/1.103.0 #43326
• Artifact commit 71274a1739871c39bbd49c4110ffb4787aec7c63, node v24.19.0
• Build id changes from kXnLzJ6ylsRPmgSkCkCKM to RvBoD6No6gfcqg-cP5_LO
• The top-N note text ("highest-spend keys") appears in 3 files of the old bundle and 0 of the new one

Type

🚄 Infrastructure

Caveats (if any)

Low

• Live proxy screenshots are not captured yet
  • Check that curl -s http://localhost:4000/ui/ | grep -o '_next/static/[A-Za-z0-9_-]*/_buildManifest.js' returns the new build id

[greptile-apps]

Confidence Score: 5/5

[Low risk] Rebuilds the admin dashboard UI bundle.

The PR appears safe to merge; no actionable failure was established in the rebuilt Admin UI output.

Summary

Rebuilds the committed Admin UI output for rc/1.103.0 so the served Usage page reflects the reverted source. The export updates its build ID, page references, and generated chunks.

_{Reviews (1) · Last reviewed commit: "chore: update Next.js build artifacts (2..."}