Repository navigation
docs(changelog): cover the 0.8.0 release-branch backports - #18276
Conversation
Design Review (Fable 5) — ✅ PASSDesign-level review of Design-Verdict: PASS Before overriding the red Changelog History Gate, spot-check the six paragraphs against the 86-commit range; the body's coverage claim is the only unverified input. [DESIGN-REVIEWED] b3c9316 |
GPT 5.6 Review — 🔴 changes requested (blocking)GPT 5.6 found at least one blocking issue that must be resolved before merging This comment is updated in place on each push. BLOCKING -- CHANGELOG.md:469 -- rewrites shipped 0.8.0 release notes
Adjudication (Opus 5) — is blocking on each finding proportionate?Line 469 is Harm rung: UNBOUNDED-class by rule anchor — mutation of already-shipped release history, silent in the artifact a user has installed ( [ADJUDICATION] b3c9316 total=1 uphold=1 downgrade=0 False positive or not applicable? A repository writer can comment: |
Opus 5 Review — 🔴 changes requested (blocking)Reviewed Shipped [BLOCK-MERGE] b3c9316 BLOCKING — CHANGELOG.md:469 66 lines are inserted inside the already-shipped [OPUS-REVIEWED] b3c9316 Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
What
Completes the
## [0.8.0] - 2026-09-27section ofCHANGELOG.mdso it covers the backports that landed onrelease/0.8.0after the section was written. Six new paragraphs are added at the end of### Notable fixes: Sessions that start and resume, Kiro Crew's own tools, Subagents and memory under load, Config files and Windows, Security and scheduled jobs, and Dashboard and desktop. Every existing line of the section, its heading and every other section are unchanged; the diff is 66 added lines and 0 removed.This PR deliberately edits the in-flight
[0.8.0]section after it was written. It is not a factual correction of shipped history: 0.8.0 stable has not shipped, and the stable GitHub Release body is extracted from this section, so it must describe what ships.Why
The section was written at the branch cut (64e850b). About 86 commits landed on the branch after it and none were described, so the stable release notes would have omitted every fix delivered across the insider builds, including the owner gates on app and scheduled-job routes, the subagent memory admission changes, the UTF-8 byte order mark fixes for Windows, and the bundled kiro-cli move to 2.27.1.
Commits covered
86 commits, range
64e850b9d607f51cd9659d71c21a324dae249ce5..f92ad888d737223906a62c5234cc1cfe8859c6ed(76 user-visible and accounted for in the section, 10 skipped below). Each one was read; fixes too small to earn a line under the three-sentence budget are folded into the nearest outcome or cut deliberately.Cut by budget (user-visible but minor): #15579 (lock waits on workspace settings writes), #15634 parts (watchdog clock, log chain lock, mise probe, mission control ledger read, lessons contradiction rule), #16829 (pipe consumer not cancelled while its producer is quiet), #16265 (memory profile reads under a symlinked home), #15581 and #15314 (read-only spec refusal text and roster).
Commits skipped
Merging this
v0.8.0-insider.16, tagged on the merge commit.[0.8.0] renders DIFFERENT notes than it did at the base ref).scripts/check_changelog_history.pyhas no label, trailer or flag that clears it. The documented override is a human one: this body states the edit is deliberate, and a maintainer must review the added lines, approve, and merge with the red Changelog History Gate check knowingly bypassed. Thechangelog-is-written-at-version-bump-onlyreview rule allows the edit only when the PR body says so, which this body does.mainverbatim, as the release process requires.Pattern harvest
Not generalizable: release notes update with no defect behind it.