Skip to content

chore: rebuild Admin UI bundle for rc/1.105.0 - #45927

Merged
yuneng-berri merged 1 commit into
rc/1.105.0from
litellm_ui_bundle_rc_1_105_0
Oct 11, 2026
Merged

yuneng-berri merged 1 commit into
rc/1.105.0from
litellm_ui_bundle_rc_1_105_0

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

TLDR

Problem this solves:

How it solves it:

  • Regenerates litellm/proxy/_experimental/out/ from rc/1.105.0 at f15af9b
  • Built with node v24.19.0, build id D71LJvOQXwPCetSwmWfOo -> vrifX6k3UPQnwaiDi5xVQ

User Flow

Before: an admin on a proxy built from rc/1.105.0 still gets the v1.105.0-rc.3 dashboard

  1. They open https://litellm-domain/ui/ and the page loads build D71LJvOQXwPCetSwmWfOo
  2. The UI changes from feat(guardrails): backport the decision model guardrail to rc/1.105.0 (#45663) #45894, feat(decisions): backport the decisions and Jev follow-ups to rc/1.105.0 without the playground #45905 and feat(ui): backport decision auto-router setup to 1.105 #45915 are missing, for example the regrouped Add Auto Router setup

After: the same admin gets the dashboard built from the current rc/1.105.0 source

  1. They open https://litellm-domain/ui/ and the page loads build vrifX6k3UPQnwaiDi5xVQ
  2. The UI changes from feat(guardrails): backport the decision model guardrail to rc/1.105.0 (#45663) #45894, feat(decisions): backport the decisions and Jev follow-ups to rc/1.105.0 without the playground #45905 and feat(ui): backport decision auto-router setup to 1.105 #45915 are there

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/unit/<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)

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 PR is one commit (919f027) of generated output, so there are no tests to add. The checks below confirm the build id swap and that nothing outside the bundle directory changed

Before (f15af9b)

  1. git show origin/rc/1.105.0:litellm/proxy/_experimental/out/index.html | grep -oE 'D71LJvOQXwPCetSwmWfOo|vrifX6k3UPQnwaiDi5xVQ' | sort | uniq -c prints 1 D71LJvOQXwPCetSwmWfOo

After (919f027)

  1. git show origin/litellm_ui_bundle_rc_1_105_0:litellm/proxy/_experimental/out/index.html | grep -oE 'D71LJvOQXwPCetSwmWfOo|vrifX6k3UPQnwaiDi5xVQ' | sort | uniq -c prints 1 vrifX6k3UPQnwaiDi5xVQ
  2. git grep -l D71LJvOQXwPCetSwmWfOo origin/litellm_ui_bundle_rc_1_105_0 -- litellm/proxy/_experimental/out | wc -l prints 0, so no file still carries the old build id
  3. git diff --name-only origin/rc/1.105.0...origin/litellm_ui_bundle_rc_1_105_0 | grep -vc '^litellm/proxy/_experimental/out/' prints 0 across the 335 changed files

Type

🚄 Infrastructure

Link to Devin session: https://app.devin.ai/sessions/095b0afb290b4c4d97bcd1bd6bd33a4e
Open in Devin Desktop: https://app.devin.ai/desktop/session/095b0afb290b4c4d97bcd1bd6bd33a4e?variant=devin

@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

  • Disable automatic comment, CI, and merge conflict monitoring

@yuneng-berri
yuneng-berri merged commit 80b9556 into rc/1.105.0 Oct 11, 2026
6 checks passed
@yuneng-berri
yuneng-berri deleted the litellm_ui_bundle_rc_1_105_0 branch October 11, 2026 06:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant