Fix: Add blog as incident report

[Sameerlite]

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	Ready	Preview, Comment	Feb 17, 2026 4:02am

[greptile-apps]

Greptile Summary

This PR rewrites the existing Claude Code beta headers blog post from a how-to/configuration guide into an incident report format. The content now documents an incident where Claude Code sent unsupported Anthropic beta headers to non-Anthropic providers (Bedrock, Azure AI, Vertex AI), causing invalid beta flag errors.

• The blog post slug, title, description, and tags are updated to reflect the incident report format, consistent with the existing model_cost_map_incident blog post
• Technical content is restructured into standard incident report sections: Summary, Background, Root Cause, Timeline, Remediation, and Resolution Steps
• The embedded mermaid diagrams illustrating old vs. new behavior are preserved
• Issue found: The incident date in the header ("February 13, 2026") conflicts with the timeline dates ("Feb 15-16, 2026")

Confidence Score: 4/5

• This PR is safe to merge — it only modifies a documentation blog post with no code changes.
• The PR only changes a single blog post markdown file, converting it from a guide to an incident report. There are no code changes, no risk to runtime behavior, and the structure follows the existing incident report convention. The one issue found is a date inconsistency that should be corrected for accuracy.
• The date inconsistency in docs/my-website/blog/claude_code_beta_headers/index.md (line 22 vs lines 71-75) should be resolved before merge.

Important Files Changed

Filename	Overview
docs/my-website/blog/claude_code_beta_headers/index.md	Rewrites the blog post from a how-to guide into an incident report format. Contains a date inconsistency between the incident header (Feb 13) and the timeline (Feb 15-16).

Flowchart

flowchart TD
    A[Original Blog Post] -->|slug: claude_code_beta_headers| B[How-To Guide Format]
    B --> C[Step-by-step configuration instructions]
    B --> D[Code examples for adding headers]
    B --> E[Contributing guide]

    A -->|PR Changes| F[Incident Report Format]
    F -->|slug: claude-code-beta-headers-incident| G[Incident Summary & Timeline]
    F --> H[Root Cause Analysis]
    F --> I[Remediation Table]
    F --> J[Resolution Steps for Users]

Loading

_{Last reviewed commit: 53728b4}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Inconsistent incident date

The incident date listed here is "February 13, 2026", but the timeline section (lines 71-75) places all events on February 15-16, 2026. These dates should be reconciled — either the header date should be updated to February 15, or the timeline dates need correcting.