[Docs] Add release notes for v1.83.3-stable and v1.83.7.rc.1

[yuneng-berri]

Relevant issues

Summary

Adds release notes for two releases and documents the staging-PR resolution step in the release-notes runbook.

Changes

• Retitles the existing v1.83.3 preview file to v1.83.3-stable (same commit as the RC; title, slug, docker tag, pip version, and changelog compare link updated; content unchanged).
• Adds new v1.83.7.rc.1 preview release notes, built by expanding six staging PRs into their underlying commits, diffing model_prices_and_context_window.json against v1.83.3-stable, and categorizing ~55 PRs per the runbook. Includes a breaking-change warning for the reduced Prometheus LATENCY_BUCKETS default (Reduce default latency histogram bucket cardinality #25527).
• Updates cookbook/misc/RELEASE_NOTES_GENERATION_INSTRUCTIONS.md with a "Resolving Staging PRs" subsection explaining that GitHub release "What's Changed" entries like Litellm oss staging ... in #NNNNN must be clicked into, and their Commits tab used to extract underlying (#NNNNN) PRs as the real changelog source.

Testing

• Visual inspection of the rendered markdown against prior stable release notes (v1.83.0, v1.83.3 preview) for structural consistency.
• Verified all PR references use the full https://github.com/BerriAI/litellm/pull/NNNNN URL form.
• Verified commit hashes and full-changelog compare links against the GitHub release tags.

Type

📖 Documentation

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Apr 14, 2026 11:23pm

[codspeed-hq]

Merging this PR will not alter performance

✅ 16 untouched benchmarks

---

_{Comparing litellm_release_notes_v1_83_3_v1_83_7rc1 (3aae15f) with main (7b36cfc)}

[greptile-apps]

Greptile Summary

This PR adds release notes for v1.83.3-stable (promoting the existing RC file) and v1.83.7.rc.1 (new ~55-PR changelog), and extends the release-notes runbook with a "Resolving Staging PRs" guide. The documentation changes are well-structured and follow existing release notes conventions, with a few issues flagged in prior review threads (pip version, changelog base tag, duplicate entries) that remain open.

Confidence Score: 4/5

Safe to merge after addressing the pip RC version and A2A doc link issues; other concerns are low-impact.

The previously flagged pip-version issue (users would install wrong/nonexistent stable version from RC notes) remains open and is a real usability defect. The new A2A→MCP link misdirection and the orphaned RC slug are P2 concerns. All other changes are clean documentation updates.

docs/my-website/release_notes/v1.83.7.rc.1/index.md (pip version, A2A link); docs/my-website/release_notes/v1.83.3/index.md (orphaned RC slug)

Important Files Changed

Filename	Overview
docs/my-website/release_notes/v1.83.3/index.md	Promotes RC release to stable: updates title, slug (breaking old RC URL), Docker tag, pip version, and changelog compare link; also updates Ryan Crabbe's image URL to GitHub avatar.
docs/my-website/release_notes/v1.83.7.rc.1/index.md	New RC release notes with ~55 categorized PRs; pip install command uses stable version instead of RC, Full Changelog base tag uses old RC tag instead of canonical stable tag, duplicate PR entries for #25527 and #25530, and A2A section links to MCP docs instead of dedicated A2A docs.
cookbook/misc/RELEASE_NOTES_GENERATION_INSTRUCTIONS.md	Adds 'Resolving Staging PRs' subsection to the release notes runbook; includes git log command and new-contributor verification guidance.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[GitHub Release Page] -->|"What's Changed"| B{Entry type?}
    B -->|Staging PR| C["Click into staging PR\ne.g. #23686"]
    C --> D[Open Commits tab]
    D --> E["Extract (#NNNNN) PR suffixes"]
    B -->|Direct commit| F[Already a real PR]
    E --> G[Staging PR set]
    F --> G
    A2[git log prev..this --oneline] -->|"grep -oE '#[0-9]+'"| H[git log PR set]
    G --> I[Union of all PRs]
    H --> I
    I --> J{"PR in git log\nbut not in staging?"}
    J -->|Yes| K["gh pr view N\nCategorize manually"]
    J -->|No| L[Categorize into release notes sections]
    K --> L
    L --> M[New Contributors check\nvia gh api search]
    M --> N[Final release notes markdown]

Loading

_{Reviews (3): Last reviewed commit: "[Docs] Use GitHub avatar for Ryan Crabbe..." | Re-trigger Greptile}

[greptile-apps]

Pip version should be RC, not stable

The pip install command shows litellm==1.83.7 (stable), but this file is the "[Preview] v1.83.7.rc.1" release candidate. The v1.83.3 RC notes used litellm==1.83.3rc1, which was only changed to litellm==1.83.3 when the file was promoted to stable. A user following these instructions today would either install an incorrect (future stable) version if 1.83.7 happens to already exist on PyPI, or hit ERROR: No matching distribution found for litellm==1.83.7.

Suggested change

	</TabItem>
	</Tabs>
	pip install litellm==1.83.7rc1

[greptile-apps]

Changelog base tag inconsistency

The comparison base is v1.83.3.rc.1, but this PR simultaneously renames the previous release to v1.83.3-stable (updating its own compare link to use that tag). If both git tags resolve to the same commit the link still works, but for consistency the base should be the canonical tag name that was just established.

Suggested change

	**Full Changelog**: https://github.com/BerriAI/litellm/compare/v1.83.3.rc.1...v1.83.7.rc.1
	**Full Changelog**: https://github.com/BerriAI/litellm/compare/v1.83.3-stable...v1.83.7.rc.1

[greptile-apps]

Duplicate PR entries across sections

PR #25527 (Prometheus LATENCY_BUCKETS) and PR #25530 (S3 retry backoff) each appear twice — once under "AI Integrations > Logging" and again under "Performance / Loadbalancing / Reliability improvements." Cross-section referencing can help readers, but exact duplicate bullets with only minor wording differences add noise. Consider either keeping each PR in one section only, or adding a clear "see also" pointer rather than repeating the full entry.