[Docs] store_model_in_db Release Docs

[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

📖 Documentation

Changes

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Feb 22, 2026 2:11am

[greptile-apps]

Greptile Summary

This documentation-only PR adds three things: (1) a new doc page for the store_model_in_db UI setting, (2) a corresponding entry in the v1.81.14 release notes, and (3) a blog post for a past SERVER_ROOT_PATH incident report. The sidebar is updated to include the new doc page.

• The new ui_store_model_db_setting.md page has two broken "Related Documentation" links — ui_overview.md and models_and_endpoints.md do not exist in the repository and will produce 404s in the published docs.
• The release notes insertion disrupts the existing section structure — the "Store Model in DB" section is placed immediately before "Eval results", which was a subsection of the guardrails section and now appears orphaned under the wrong heading.
• The SERVER_ROOT_PATH incident report blog post is well-structured with clear root cause analysis, timeline, and remediation details.

Confidence Score: 3/5

• Documentation-only PR with no code changes, but contains broken links and a misplaced release notes section that will affect the published docs.
• Score of 3 reflects that while this is a docs-only PR (no runtime risk), there are two broken documentation links that will produce 404 errors for readers, and the release notes structure is disrupted by the new section placement. These issues should be fixed before merging to avoid a poor documentation experience.
• docs/my-website/docs/proxy/ui_store_model_db_setting.md (broken related documentation links) and docs/my-website/release_notes/v1.81.14.md (misplaced section breaks guardrails structure)

Important Files Changed

Filename	Overview
docs/my-website/docs/proxy/ui_store_model_db_setting.md	New documentation page for store_model_in_db UI setting. Contains two broken "Related Documentation" links (ui_overview.md and models_and_endpoints.md don't exist) and unused Tabs/TabItem imports.
docs/my-website/release_notes/v1.81.14.md	Release notes updated with Store Model in DB feature entry. The new section is inserted in a position that disrupts the existing guardrails section structure, causing "Eval results" to appear under the wrong heading.
docs/my-website/blog/server_root_path/index.md	Well-written incident report blog post documenting the SERVER_ROOT_PATH regression. Includes clear timeline, root cause analysis, remediation steps, and CI workflow details. No issues found.
docs/my-website/sidebars.js	Sidebar entry added for the new ui_store_model_db_setting page under the "Models" category. Placement is appropriate alongside existing model-related UI docs.
docs/my-website/img/ui_store_model_in_db.png	Screenshot image for the store_model_in_db UI feature documentation. File exists and is referenced correctly.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Admin UI: Models + Endpoints"] --> B["Click Settings Icon"]
    B --> C["Toggle store_model_in_db"]
    C -->|Enabled| D["Model definitions stored in DB"]
    C -->|Disabled| E["Models read from config only"]
    D --> F["No proxy restart needed"]
    E --> F
    F --> G["Setting takes effect immediately"]

    style D fill:#d4edda,stroke:#28a745
    style E fill:#fff3cd,stroke:#ffc107
    style G fill:#d1ecf1,stroke:#0dcaf0

Loading

_{Last reviewed commit: cb4b638}

[greptile-apps]

_{5 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Broken links to non-existent docs

Two of the three "Related Documentation" links point to files that do not exist in the repository:

• ./ui_overview.md — no file at docs/my-website/docs/proxy/ui_overview.md
• ./models_and_endpoints.md — no file at docs/my-website/docs/proxy/models_and_endpoints.md

Only ./config_settings.md exists. These broken links will cause 404 errors in the published docs. Either create the referenced pages, or update these links to point to existing documentation pages.

[greptile-apps]

New section misplaced before "Eval results"

The "## Store Model in DB Settings via UI" section is inserted immediately before ### Eval results (line 70), which was originally a subsection under the guardrails / "3 New Built-in Guardrails" section. As a result, "Eval results" now appears to be a subsection of "Store Model in DB Settings via UI" rather than the guardrails section where it belongs.

Consider moving this new section either after the "Eval results" table (after the paragraph ending on what was previously line 79) or to a different location in the release notes where it won't break the guardrails section's structure.

[greptile-apps]

Unused imports

Tabs and TabItem are imported but never used in this document. Remove these unused imports to keep the file clean.

Suggested change

	import Tabs from '@theme/Tabs';
	import TabItem from '@theme/TabItem';