docs(changelog): v0.2.0 says what moved and what a copy must read - #66
Merged
Conversation
The release route writes the changelog section during development and dates it when the tag is cut, so a dateless heading is the visible sign that a release is prepared but not out. This release skipped the first half: eleven commits landed since v0.1.0 without a section accruing, so this commit writes the section and dates it in one go, minutes before the tag. The route is unchanged for the next one, and doing both here is the honest record of what happened rather than a staged dateless heading nobody would have read. What the section says is aimed at a reader who already holds a copy. The two splits get the most room, because they are the only things in this release that can collide with edits someone made to their own copy: checks/check.mjs into three files with the suites mirroring them, and COMPLIANCE.md handing this project's answers to docs/compliance/REGISTER.md. Both name the entry point that did not move, so nobody rewires what still works. The evidence drill leads, since it is the one thing here that changes what a green tick means. Counts stay out, per SC-11: index.html and progress.mjs derive them from the directories that own them, and a third typed copy is the one that goes stale. Traces-to: SC-9
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.
What changed and why
The v0.2.0 section of
CHANGELOG.md, dated, so the release can be tagged. Nothing else is inthis diff.
Eleven commits landed since v0.1.0 and no changelog section accrued along the way, so this one
commit writes the section and dates it minutes before the tag rather than staging a dateless
heading nobody would read.
docs/operations/deploy.mdstep 3 is otherwise followed exactly:branch, date, PR, rebase merge, then tag the merge commit.
The section is written for someone who already holds a copy. The two splits get the most room,
because they are the only changes here that can collide with edits made to a copy:
checks/check.mjsinto three files with the suites mirroring them, andCOMPLIANCE.mdhandingthis project's own answers to
docs/compliance/REGISTER.md. Both name the entry point that didnot move, so nobody rewires what still works. The evidence drill leads, being the one thing in
this release that changes what a green tick means. Counts stay out per SC-11.
Verified by
The full close-out pass on
f4b34bf, before this commit and again after it:node checks/check.mjs: green, enforcement reports hooks, CI and adapter hooks armed.cockpit-path 11, cockpit 21, drill 11.
node checks/drill.mjs --require-walk: PASSED, a fresh copy reached a governed first commitin 3.2s, 119 files with the symlink intact and 4 files blanked.
deliversection 0 re-checked on the head that ships: CI green onf4b34bf, privatevulnerability reporting enabled,
mainprotected withgateandtracerequired andadministrators included, no blocking row in
docs/compliance/REGISTER.md, spec 010 atdone.Not verifiable before merge: the release page and the tarball smoke checks in
deploy.md, whichneed the tag. They run straight after the merge, and their results go in the handoff.