Consolidate the 1.5.24 changelog - #207
Conversation
1.5.23 was built but never published, so it should not stand as its own changelog section: nobody can install it, and a reader upgrading from 1.5.22 would have to stitch two entries together to see what they got. Folds everything into 1.5.24 as one complete entry, grouped Added / Fixed / Internal, and notes that it supersedes the unreleased 1.5.23. Also picks up the release-profile and provider fixes that shipped in the same window and had no user-facing entry.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ceiling | 80d0807 | Commit Preview URL Branch Preview URL |
Aug 05 2026, 05:47 AM |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 38 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. Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the project documentation by consolidating the unreleased 1.5.23 changelog entry into the published 1.5.24 entry, so readers upgrading from 1.5.22 see a single complete set of changes (including items shipped in the same window but previously lacking a user-facing entry).
Changes:
- Collapses the unreleased 1.5.23 notes into the 1.5.24 section and explicitly marks 1.5.24 as superseding 1.5.23.
- Re-groups and rewords the 1.5.24 notes under Added / Fixed / Internal, incorporating items referenced from #201.
Suppressed comments (1)
CHANGELOG.md:26
- Spelling is inconsistent with other entries in this changelog (which use “behavior”). Consider changing “undefined behaviour” to “undefined behavior” for consistency.
- Cost-scanner tests no longer mutate `CODEX_HOME`, `CLAUDE_CONFIG_DIR`, or `GROK_HOME`. Changing process environment while another thread reads it is undefined behaviour, and nine other modules read those variables constantly, so unrelated scans intermittently resolved the wrong home. One such failure also poisoned a shared mutex and cascaded into three more, which disguised a single fault as four. The scanner now takes an injected ambient home; the suite went from failing roughly one run in five to twelve consecutive clean runs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Fixed. The file is American English throughout — |
Docs only.
1.5.23 was built but never published, so it shouldn't stand as its own changelog section — nobody can install it, and a reader upgrading from 1.5.22 would have to stitch two entries together to work out what they actually got.
Everything is folded into a single 1.5.24 entry, grouped Added / Fixed / Internal, noting that it supersedes the unreleased 1.5.23. It also picks up the release-profile and provider fixes from #201, which shipped in this window with no user-facing entry.
Contents now covered: the expected-usage marker, the tray pace verdict, opt-in predictive warnings, Cursor on-demand in dollars (and no longer filtered out of the app window), removal of the always-0% Promotional meter, the Opus model-pool alert fix, cadence-keyed threshold alerts, the Devin percent-scale fix, LTO/strip release builds, and the cost-scanner env race.