Skip to content

chore(version): port the final 0.8.0 CHANGELOG section to main - #18282

Merged
bolichen97 merged 1 commit into
mainfrom
chore/port-0.8.0-changelog-to-main
Oct 9, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
chore/port-0.8.0-changelog-to-main

Conversation

@KiroCrewCaptain

Copy link
Copy Markdown
Collaborator

What

A verbatim copy of the ## [0.8.0] - 2026-09-27 section of CHANGELOG.md from release/0.8.0 at 4d205da (the merge of #18276), replacing the earlier [0.8.0] section on main. The section is 66 lines longer. No other section changes: the [0.7.2] section that exists only on main stays in place, below [0.8.0].

Why

main must carry the same release notes as the stable 0.8.0 release. docs/build/release.md says the section is written on the release branch first, then ported to main verbatim, and that main is 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:

git show 4d205dadc142500dd3f0e89de28ce70304b72d7c:CHANGELOG.md > release-CHANGELOG.md
diff <(awk '/^## \[0.8.0\]/{p=1} /^## \[0.7.2\]/{p=0} p' CHANGELOG.md) <(awk '/^## \[0.8.0\]/{p=1} /^## \[0.7.1\]/{p=0} p' release-CHANGELOG.md)

The diff is empty. git diff --stat origin/main shows CHANGELOG.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.py reports 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.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 9, 2026
@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ⏭️ skipped

Revision 2b3f0151636c6f6d254c70bd4d8bcfd884e25fe4 ships no reviewable capability (docs, tests or generated files only), so there is nothing to inventory. Advisory — does not block merge.

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 2b3f0151636c6f6d254c70bd4d8bcfd884e25fe4 touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Advisory — does not block merge.

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 2b3f0151636c6f6d254c70bd4d8bcfd884e25fe4 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check before merge that the maintainer's bypass of check_changelog_history.py covers only the [0.8.0] hunk the description's diff proof shows to be verbatim.

[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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 2b3f0151636c6f6d254c70bd4d8bcfd884e25fe4 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 2b3f015

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 2b3f0151636c6f6d254c70bd4d8bcfd884e25fe4: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 2b3f0151636c6f6d254c70bd4d8bcfd884e25fe4 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 2b3f015

Verdict parsed from the review's SHA-scoped output markers for commit 2b3f0151636c6f6d254c70bd4d8bcfd884e25fe4.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 2b3f0151636c6f6d254c70bd4d8bcfd884e25fe4: <one-sentence reason>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 9, 2026
@bolichen97
bolichen97 marked this pull request as ready for review October 9, 2026 05:44
@bolichen97
bolichen97 requested a review from a team as a code owner October 9, 2026 05:44
@bolichen97
bolichen97 requested a review from buluoray October 9, 2026 05:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants