Update changelog#107
Conversation
The changelog stopped at v2.3.5 even though releases continued through v2.4.13. Add entries for the missing releases using the existing Keep a Changelog structure and project tone. Move the Cursor SDK migration notes out of Unreleased and into v2.4.7, where the changes shipped. Keep the BREAKING section limited to the auth migration because the backing commit explicitly marked it as breaking. The new entries summarize release-tagged changes from v2.3.6 through v2.4.13, including SDK migration, Windows support, MCP/tool-loop fixes, model refresh controls, session resume, and runner pool hardening. Co-authored-by: openai/gpt-5.5-medium <noreply@openai.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthrough
ChangesChangelog Release Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
Upstream released v2.4.14 after the changelog update branch was opened. Add the missing entry while keeping the branch limited to CHANGELOG.md. Summarize the new request timing markers, runtime status visibility, and quota-banner fix. No BREAKING section is added because the release range contains no explicit breaking-change marker. Co-authored-by: openai/gpt-5.5-medium <noreply@openai.com>
Noticed that the CHANGELOG.md file hasn't been updated in a while, so I've considered updating it.
This plugin looks very promising, thank you! But I am also tracking some of the performance issues previously reported, and scanning the changelog makes easy to see how critical it is to update the plugin to get any improvements.
[AI disclaimer: this pull request contains changes generated by an LLM under the supervision of an adult.]