chore(ui): rebuild committed admin dashboard bundle for rc release

[yuneng-berri]

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)

Screenshots / Proof of Fix

There is no functional change to demonstrate; this is a deterministic regeneration of the committed admin dashboard bundle produced by ui/litellm-dashboard/build_release_ui.sh (Next.js output: export build, then copy into litellm/proxy/_experimental/out)

The diff is confined entirely to that path:

$ git diff --name-only origin/litellm_internal_staging..HEAD | grep -v '^litellm/proxy/_experimental/out/'
(no output)
$ git diff --name-only origin/litellm_internal_staging..HEAD | wc -l
761

Type

🚄 Infrastructure

Changes

Rebuilds the committed Next.js export of the admin dashboard under litellm/proxy/_experimental/out for the upcoming release candidate, so the PyPI wheel ships the current UI (the wheel serves this committed bundle while the Docker image rebuilds the UI from source)

There are no source edits in this PR; the diff is entirely regenerated build output, so the churn is the Next.js build ID directory rename and chunk hash changes propagated across the exported *.html, *.js, and *.css files

[greptile-apps]

Too many files changed for review. (761 files found, 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_/litellm-dashboard-rc-ui-6f3b09 (6b69af4) with litellm_internal_staging (e7f4144)}

[Normanyadav]

Fix ready for review.

This updates the fix branch with corrected region-handling logic in _select_model_name_for_cost_calc. The core change:

1. Source-model branch (hidden_params.model): Region is only appended when the model name ends with a / — meaning the caller explicitly wants a provider-scoped lookup. Otherwise region is skipped.
2. Custom-pricing branch: When known provider prefix is present, region IS incorporated to match pricing table keys (provider/region/model).
3. Tests updated to assert the corrected behavior across all paths.