Remove legacy changelog and deprecation files#6311
Conversation
- Delete `CHANGELOG.md` and `CHANGELOG_MODEL.md`. - Update `CONTRIBUTING.md` and `AGENTS.md` to remove instructions and references related to maintaining the changelog.
…nges. - Delete `DEPRECATIONS.md`, which previously tracked SDK deprecation timelines and migration paths. - Update `AGENTS.md` to direct documentation of deprecations and behavioral shifts to release notes via PR labels instead of the deprecated file. - Update the developer checklist to prioritize PR labeling (e.g., `pr:breaking-change`) for user-visible changes.
PR checklist ✅All required conditions are satisfied:
🎉 Great job! This PR is ready for review. |
SDK Size Comparison 📏
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
💤 Files with no reviewable changes (2)
WalkthroughThese changes shift release notes management from manual changelog files toward a PR/release-label-based system. The CHANGELOG_MODEL.md template file is entirely removed, and documentation references to CHANGELOG.md and DEPRECATIONS.md are removed from contribution guidelines and agent instructions. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|



Goal
Remove manually-maintained
CHANGELOG.md,CHANGELOG_MODEL.md, andDEPRECATIONS.mdfiles that are no longer needed now that release notes are auto-generated via.github/release.yamland PR labels.Implementation
CHANGELOG.md,CHANGELOG_MODEL.md, andDEPRECATIONS.mdCONTRIBUTING.mdto remove references to the deleted filesAGENTS.mdto:DEPRECATIONS.mdreferences from API stability and documentation guidanceTesting
.github/release.yamlis still in place and correctly configured for auto-generated release notesSummary by CodeRabbit