Repository navigation
chore(version): port the final 0.8.0 CHANGELOG section to main - #18282
Conversation
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Check before merge that the maintainer's bypass of [DESIGN-REVIEWED] 2b3f015 Description read[DESCRIPTION-READ] 29fa175483f92f4e13eb60fbbd35333a3da6fb8df7029ae4edd20499c7448173 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
What
A verbatim copy of the
## [0.8.0] - 2026-09-27section ofCHANGELOG.mdfromrelease/0.8.0at 4d205da (the merge of #18276), replacing the earlier[0.8.0]section onmain. The section is 66 lines longer. No other section changes: the[0.7.2]section that exists only onmainstays in place, below[0.8.0].Why
mainmust carry the same release notes as the stable 0.8.0 release.docs/build/release.mdsays the section is written on the release branch first, then ported tomainverbatim, and thatmainis the recovery source for the changelog.Proof
Extract the
[0.8.0]section from each file (from its heading up to the next heading:[0.7.2]on this branch,[0.7.1]on the release branch) and diff them:The diff is empty.
git diff --stat origin/mainshowsCHANGELOG.md | 66 +and nothing else.Merging this
The changelog history gate is red by design. With
CHANGELOG_BASE_REF=origin/main,scripts/check_changelog_history.pyreports that[0.8.0]renders different notes than at the base ref, because a shipped section must not change. This change is the deliberate port of the final notes, so a maintainer bypasses that gate to merge. Without a base ref the script passes (no draft sections).Pattern harvest
Not generalizable: release notes port with no defect behind it.