docs: add Semgrep & OOM fixes section to v1.81.12 release notes

[AlexsanderHamir]

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

🆕 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	Building	Preview, Comment	Feb 16, 2026 7:40pm

[greptile-apps]

Greptile Summary

Documentation-only change that adds a new "Add Semgrep & fix OOMs" entry to the v1.81.12 release notes. The PR adds a bullet point in the Key Highlights section and a dedicated subsection describing the out-of-memory fixes (bounded asyncio.Queue() with configurable LITELLM_ASYNCIO_QUEUE_MAXSIZE) and the new Semgrep rule for detecting unbounded-memory patterns. References PR #20912.

• Adds highlight bullet linking to the new dedicated section and the original PR
• Adds a ## Add Semgrep & fix OOMs section with a clear description of the OOM fix and Semgrep rule
• PR Add semgrep & Fix OOMs #20912 is also already referenced under the "Performance / Loadbalancing / Reliability improvements" section, so this promotes the change to Key Highlights for greater visibility

Confidence Score: 5/5

• This is a minimal documentation-only change to release notes with no code changes — safe to merge.
• The PR modifies a single documentation file (release notes), adding well-formatted content that is consistent with the existing document structure. There are no code changes, no test requirements, and no risk of runtime impact.
• No files require special attention.

Important Files Changed

Filename	Overview
docs/my-website/release_notes/v1.81.12.md	Adds a new "Semgrep & fix OOMs" entry to Key Highlights and a dedicated section describing the OOM fix and Semgrep rule addition from PR #20912. No issues found.

Flowchart

flowchart TD
    A["v1.81.12 Release Notes"] --> B["Key Highlights Section"]
    A --> C["Performance Section"]
    B --> D["NEW: Add Semgrep & fix OOMs bullet"]
    D --> E["Links to dedicated section"]
    D --> F["Links to PR #20912"]
    A --> G["NEW: Add Semgrep & fix OOMs Section"]
    G --> H["Bounded asyncio.Queue with\nLITELLM_ASYNCIO_QUEUE_MAXSIZE"]
    G --> I["Semgrep rule for\nunbounded-memory patterns"]
    C --> J["Existing PR #20912 reference"]

Loading

_{Last reviewed commit: 3f6a8c5}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}