Put the unreleased entries back in the right sections - #370
Conversation
Sixteen ordinary bug fixes had drifted under ### Security. That is my doing: resolving twenty-odd CHANGELOG conflicts today merged bullets by position without regard for the heading above them, so entries kept landing in whichever section the conflict happened to open in. Shipping that would have told everyone this release fixed seventeen security issues. It fixed one: the Gemini missing-home token write, which is the entry that created the section. Each bullet was put back where the commit that introduced it had it, and the section order matches 1.5.33: Added, Security, Fixed, Internal. No bullet text changed and none was lost - still twenty.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ceiling | 8c561c6 | Commit Preview URL Branch Preview URL |
Aug 22 2026, 09:43 PM |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe unreleased changelog adds a ChangesUnreleased changelog organization
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized documentation-only changelog reordering with no product or security code impact; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
1 participant
Why this matters before a release
The unreleased section currently reads:
Cutting 1.5.35 from that would announce seventeen security fixes. There is one:
Gemini treats a missing home directory as not logged in— the entry that created the section, because it stopped live OAuth tokens being written into a checked-in fixture.This is my fault. Landing 21 PRs today meant resolving twenty-odd CHANGELOG conflicts, and my resolution merged bullets by position without regard for the heading above them. Entries kept landing in whichever section the conflict happened to open in, and
### Securitysat at the top of the drift.What
Every bullet restored to the section the commit that introduced it had it in — recovered from
git log -Sper bullet, not from my judgement of what looks security-ish. Section order matches 1.5.33: Added, Security, Fixed, Internal.No bullet text changed, and none was lost — still 20.
Three entries (#351, #354, #355) were introduced after the drift began, so history could not place them cleanly. Their PR diffs add no
### Securityheading and none is a security fix, so they sit under Fixed.Note
Low Risk
Documentation-only CHANGELOG reordering; no product or security code changes.
Overview
Fixes a merge-conflict mix-up in the Unreleased notes that had put seventeen bullets under Security.
Section order is now Added, Security, Fixed, Internal. The Gemini missing-home-directory credential fallback stays the only Security entry. The other sixteen notes (plus the mid-scan price-fingerprint item that had been under Internal) move to Fixed. Bullet text is unchanged.
Reviewed by Cursor Bugbot for commit 8c561c6. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Move unreleased changelog fix entries back under the
### FixedsectionReorganizes CHANGELOG.md by adding a
### Fixedsubsection under the Unreleased heading and relocating the price-change-scan fix bullet into it. Removes a duplicate### Fixedsubsection and stray blank lines that appeared after the### Internalsection.Macroscope summarized 8c561c6.
Summary by CodeRabbit