Litellm dev 04 11 2026 p1

[krrish-berri-2]

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/test_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

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-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:

Screenshots / Proof of Fix

Type

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Apr 12, 2026 1:40am

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[greptile-apps]

Greptile Summary

This is a documentation-only PR that reorganizes the benchmarks page (moving machine specs and result tables to the top for better first-impression impact) and updates navigation in sidebars.js and the README header link.

Confidence Score: 5/5

Safe to merge — documentation-only changes with no code impact.

All findings are P2 style suggestions (link label wording, sidebar grouping). No code, logic, or security changes are involved.

docs/my-website/sidebars.js — the load-testing docs are now split across two sidebar locations.

Important Files Changed

Filename	Overview
README.md	Updates the "Website" header link to point to /ai-gateway instead of the site root.
docs/my-website/docs/benchmarks.md	Reorganizes content order — moves machine specs, configuration, and benchmark result tables to the top, and adds a benchmarking script link.
docs/my-website/sidebars.js	Removes the "Load Testing" category; benchmarks becomes a standalone top-level item while load_test_advanced/sdk/rpm are moved to the "Extras" section, splitting previously grouped docs.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Sidebar Navigation] --> B[Routing]
    A --> C["benchmarks (standalone)"]
    A --> D[Contributing]
    A --> E[Extras]
    E --> F[data_retention]
    E --> G[security_encryption_faq]
    E --> H[migration_policy]
    E --> I[load_test_advanced]
    E --> J[load_test_sdk]
    E --> K[load_test_rpm]
    E --> L[Projects built on LiteLLM]
    style C fill:#f9f,stroke:#333
    style I fill:#ffa,stroke:#333
    style J fill:#ffa,stroke:#333
    style K fill:#ffa,stroke:#333

Loading

_{Reviews (1): Last reviewed commit: "docs: readme tweak" | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 16 untouched benchmarks

---

_{Comparing litellm_dev_04_11_2026_p1 (973986a) with main (12c1467)}

[greptile-apps]

"Website" link points to a product page, not the site root

The link label is Website but the destination is now https://www.litellm.ai/ai-gateway — a specific product page. Visitors clicking "Website" typically expect the homepage. Consider either updating the label to AI Gateway or keeping the URL as the site root (https://www.litellm.ai/).

[greptile-apps]

Load-testing docs split across two unrelated locations

benchmarks is now a standalone top-level item while load_test_advanced, load_test_sdk, and load_test_rpm land in the "Extras" section alongside data-retention and security pages. Users looking for load-testing material will have to search in two different parts of the sidebar. Keeping them together (either as a flat group at the top level or as siblings in "Extras") would avoid the split.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!