docs: drop released v1.2.0 entries from Unreleased and archive v1.2.0 [no ci] - #433
Conversation
… [no ci] The changelog was not reset after v1.2.0 shipped on 27 August 2026, so Unreleased still carried the eight entries reproduced in that release: three under Fixed and five under Other. Left as-is, the 1.2.1 release notes would announce all of it again. Those entries are removed and v1.2.0 joins the Past Release Notes list, which stopped at v1.1.0. Unreleased now holds only work merged after the v1.2.0 tag (#377, #378, #419, #427), which is what 1.2.1 will ship. Co-Authored-By: Claude Fable 5.1 <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: Repository: qBraid/pyqasm/.coderabbit.yaml Review profile: CHILL Plan: Advanced 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 only |
Summary
v1.2.0 shipped on 27 August 2026, but
CHANGELOG.mdwas never reset afterwards. Compare the v1.2.0 release notes against## Unreleasedonmain: the threeFixedentries and the fiveOtherentries (#412, #411, #414, #413, #383) are already published there. The Past Release Notes list also stops at v1.1.0.Without this fix, the 1.2.1 release notes generated from
Unreleasedwould re-announce all eight entries.What changed
Unreleasedentries that shipped in v1.2.0.Fixedis now empty;Otherkeeps only the two ci: cancel superseded runs and trim the PR wheel matrix #419 entries.v1.2.0to the top of Past Release Notes, matching how v1.1.0 and earlier are archived.Net:
CHANGELOG.md, +1 / -8. No other file is touched.Unreleasednow holds exactly the work merged after the v1.2.0 tag (#377, #378, #419, #427), which is what 1.2.1 will ship.Follow-up
After 1.2.1 is published, a second
[no ci]PR should emptyUnreleasedand archive v1.2.1, so this does not recur.🤖 Generated with Claude Code