[Infra] Fixing UI Build

[yuneng-jiang]

Relevant issues

Pre-Submission checklist

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

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🚄 Infrastructure

Changes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Building	Preview, Comment	Feb 26, 2026 6:30am

[greptile-apps]

Greptile Summary

This PR fixes a broken UI build caused by unresolved git merge conflict markers that were accidentally committed to main in ToolPolicies.tsx. The conflict was between the cursor/development-environment-setup-13a7 branch and main, affecting two sections:

• Import block (lines 1-17): Duplicate @tremor/react imports with conflict markers. The fix keeps the single-line import from main and re-sorts all imports alphabetically.
• PolicySelect styling (lines 50-65): An extra styles prop spread from the development branch. The fix removes it, keeping the simpler version from main.

No functional or behavioral changes — this is purely a conflict resolution to restore a compilable state.

Confidence Score: 5/5

• This PR is safe to merge — it only removes git merge conflict markers with no functional changes.
• The change is minimal and purely mechanical: it removes unresolved merge conflict markers (<<<<<<<, =======, >>>>>>>) and re-sorts imports. The resulting file is a clean, valid TSX file with no logic changes. The risk of regression is effectively zero.
• No files require special attention.

Important Files Changed

Filename	Overview
ui/litellm-dashboard/src/components/ToolPolicies.tsx	Removes unresolved git merge conflict markers from imports and a styling block, resolving the build failure. Imports are re-sorted alphabetically. No functional logic changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["ToolPolicies.tsx (before)"] -->|"Had unresolved merge conflict markers"| B["Build Failure"]
    A -->|"This PR: Remove conflict markers,\nkeep main branch version"| C["ToolPolicies.tsx (after)"]
    C -->|"Clean imports + no extra styling"| D["Build Succeeds"]

Loading

_{Last reviewed commit: 5a123f0}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}