Fold 1.5.23 into the 1.5.24 release notes - #206
Conversation
1.5.23 was tagged and built but never published: its Microsoft Store submission blocked 1.5.24's, and 1.5.24 supersedes it entirely. Its draft release is deleted, so users go straight from 1.5.22 to 1.5.24 and would otherwise never see what changed in between. - Cover both versions in the 1.5.24 notes, and compare against v1.5.22 rather than v1.5.23. - Note in the changelog that 1.5.23 was superseded, so the entry is not mistaken for a version anyone can install. The v1.5.23 tag is kept: it is real history, the changelog documents it, and deleting it would break the compare links that reference it.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 53 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Comment |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ceiling | e4624c0 | Commit Preview URL Branch Preview URL |
Aug 05 2026, 05:32 AM |
There was a problem hiding this comment.
Pull request overview
Updates release documentation so users upgrading directly from 1.5.22 → 1.5.24 still see the (unpublished) 1.5.23 changes, while keeping v1.5.23 as historical tag context.
Changes:
- Marked 1.5.23 as superseded and never published in
CHANGELOG.mdto prevent confusion. - Expanded 1.5.24 release notes to explicitly include the 1.5.23 content.
- Updated the “Full Changelog” compare link to
v1.5.22...v1.5.24.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| CHANGELOG.md | Notes that 1.5.23 was superseded and never published so readers don’t treat it as an installable release. |
| .github/release-notes-1.5.24.md | Clarifies 1.5.24 includes 1.5.23 content and updates the compare link to start from v1.5.22. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Docs only. No code, no version change.
1.5.23 was tagged and built but never published — its Microsoft Store submission blocked 1.5.24's, and 1.5.24 supersedes it entirely. Its draft release is now deleted, so users upgrade 1.5.22 → 1.5.24 directly and would otherwise never see what changed in between.
.github/release-notes-1.5.24.mdnow covers both versions, and compares againstv1.5.22instead ofv1.5.23.CHANGELOG.mdnotes that the 1.5.23 entry was superseded, so it isn't mistaken for a version anyone can install.The
v1.5.23tag is deliberately kept: it is real history, the changelog documents it, and deleting it would break compare links that reference it.