Repository navigation
docs(changelog): cover the 0.9.0 release-branch backports - #20950
Conversation
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — 🟡 CONCERNSDesign-level review of Design-Verdict: CONCERNS This edits a section the immutability gate treats as shipped, and the only exception is the description's own argument; changelog.md records no in-flight carve-out. Watch
[DESIGN-REVIEWED] d905096 Description read[DESCRIPTION-READ] 6793435c86e036574bd6bb066a61fa7902f4b929c103f9da4ba1f111dd7e238f 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 |
Opus 5.5 Review — 🔴 changes requested (blocking)Reviewed Blocking: this PR edits the existing BLOCKING — CHANGELOG.md:181 [BLOCK-MERGE] d905096 Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — 🔴 changes requested (blocking)GPT 6.1 found at least one blocking issue that must be resolved before merging This comment is updated in place on each push. BLOCKING -- CHANGELOG.md:181 -- Standalone changelog edit requires a human override
Adjudication (Opus 5.5) — is blocking on each finding proportionate?The finding is anchored to F1, harm rung not weighed. Conditions confirmed: this PR's only change is 6 added lines in False positive or not applicable? A repository writer can comment: |
What
Completes the ## [0.9.0] section so it covers the three fixes backported to release/0.9.0 after the section was written: #19189 (self-update fetch), #19309 (KAS reserved crewmate ids) and #20631 (a waiting tool no longer stalls the others). One paragraph is added at the end of ### Notable fixes. Every existing line, the heading and every other section are unchanged: 6 lines added, 0 removed.
This PR deliberately edits the in-flight [0.9.0] section. It is not a factual correction of shipped history: 0.9.0 stable has not shipped, and the stable GitHub Release body is extracted from this section, so it must describe what ships. The changelog-history gate flags the change for that reason.
Commits covered
Range 13a24b1..a9ec7fc on release/0.9.0: 3 user-visible backports, written up here; the other 6 commits are tests, CI and the 0.8.0 date fix, with nothing to describe.
This PR has no tracking issue: release PRs take issue-gate: waived.