docs(changelog): move premature 1.0.0 entry out of release history#297
Open
khuepm wants to merge 1 commit into
Open
docs(changelog): move premature 1.0.0 entry out of release history#297khuepm wants to merge 1 commit into
khuepm wants to merge 1 commit into
Conversation
CHANGELOG.md carried a `## [1.0.0] - 2026-07-11` section wedged between [0.22.0] and [0.21.0]. 1.0.0 has never been tagged, so the file asserted a release that does not exist — and placed it before 0.22.0, 0.23.0 and 0.24.x, which do. It would also have broken the next real release. `/release` step 2 inserts the new section directly under `## [Unreleased]`, so cutting 1.0.0 would have produced two `## [1.0.0]` headings, and the awk extractor in that same step stops at the first match — the GitHub Release would have shipped the stale text. The prose is preserved in `.kiro/steering/v1-changelog-draft.md` alongside the other v1 release docs, with the staleness recorded so the RC-time rewrite starts from a known state rather than from scratch: it stops at 0.21.x (no 0.22 → 0.24.1 coverage), still lists CWE-521 as an open v1 fix, and describes the RBAC backfill as "verified" from a time when the repo had nothing to back that up. Verified after the edit: version headings are strictly descending by semver, no duplicate heading, the [0.20.0] → [0.21.0] join is intact, nothing links to a `CHANGELOG.md#1...` anchor, and the /release awk extractor still returns the right section for 0.24.1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes part of §5 in the v1.0.0 readiness checklist.
Vấn đề
CHANGELOG.mdcó section## [1.0.0] - 2026-07-11nằm kẹp giữa[0.22.0]và[0.21.0].1.0.0chưa bao giờ được tag, nên file đang khẳng định một bản release không tồn tại — và đặt nó trước 0.22.0, 0.23.0, 0.24.x là những bản có thật.Nghiêm trọng hơn, nó sẽ làm vỡ lần release thật kế tiếp:
/releasestep 2 chèn section mới ngay dưới## [Unreleased], nên khi cắt 1.0.0 sẽ có hai heading## [1.0.0], và đoạnawkextract ở cùng step đó dừng ở match đầu tiên → GitHub Release sẽ lấy đúng bản text stale.Thay đổi
[1.0.0]khỏi lịch sử release trongCHANGELOG.md(-77 dòng)..kiro/steering/v1-changelog-draft.md, cạnh các doc v1 khác (v1-release-criteria.md,v1-scope-classification.md), kèm ghi chú những chỗ đã stale để lần viết lại ở RC không bắt đầu từ số 0:backfill/role-policies.ts+ CLI +upgrade-path.e2e.test.tstrong CIDocs-only, không đụng code.
Kiểm chứng sau khi sửa
[0.20.0]→[0.21.0]nguyên vẹn, không thừa/thiếu dòng trắngCHANGELOG.md#1...awkextractor của/releasevẫn trả về đúng section cho0.24.1