docs: reset the changelog after the v1.1.0 release - #374
Conversation
v1.1.0 shipped every entry that was sitting under Unreleased, so the section now describes work that is already released. Empty each Unreleased subsection and add the v1.1.0 archive link, so the next cycle starts from a clean slate. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Argus reviewAuto-review is off for this repo. Tick the box below to run a review on this PR.
Estimated cost
Tip: you can also comment |
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
|
Merging as just docs are updated |
1 participant
Summary
v1.1.0 shipped on 17 August 2026 and carried every entry that was sitting under
## Unreleased. Compare the v1.1.0 release notes againstCHANGELOG.mdonmain: the two lists are identical. TheUnreleasedsection therefore describes released work.This PR resets it.
What changed
Unreleasedsubsection (Added,Improved / Modified,Fixed,Dependencies). The 23 removed lines are exactly the entries reproduced in the v1.1.0 release notes.v1.1.0to the top of Past Release Notes, matching how v1.0.4 and earlier are archived.Net:
CHANGELOG.md, +1 / -23. No other file is touched.Why now
The v1.0.3 and v1.0.4 releases each left their entries in
Unreleased, which is what #372 had to clean up after the fact. Resetting at release time keeps that from recurring.