Repository navigation
Changelog: v0.5.3 back to unreleased (one release when everything is done) - #850
Conversation
…until the release The owner decided (2026-10-19) there is no release until everything is done, and the CHANGELOG keeps one unreleased section. #828 dated v0.5.3 and wrote its generated Features, Fixes, Security and guardrails and Guardrail changes lists. An unreleased section is all hand-written: test/changelog.test.ts checks that the release keeps every line of one. With only the heading undated, that test failed, listing #828's generated lines as lines the release would drop. Those lines are generated output: main's changelogSection, fed the PRs they name, writes the same 123 lines in the same order. `node scripts/release.mjs changelog 0.5.3` writes them again when the owner cuts the release. The hand-written notes (148 lines) and an empty closing "### Guardrail changes" heading stay, so the release keeps every hand-written line. Test (fails without): none new; no code changes. test/changelog.test.ts "an unreleased section is all hand-written" fails with the heading undated and the lists kept, and passes on this tree. Signed-off-by: Jayden Vasquez <jaydenvasquez1711@gmail.com>
Evaluator verdict: PASSHead 54b3eb1, base 71316eb. Independent review. I didn't write this PR. Merge condition (not a change to the PR): CI on 54b3eb1 is red in one job, What the owner decision asked for (2026-10-19: no release until everything is done, one unreleased section)
Regeneration check (measured)I ran main's
Tests on the head (measured, in my worktree, built with
|
… issue-811 Signed-off-by: Jayden Vasquez <jaydenvasquez1711@gmail.com> # Conflicts: # CHANGELOG.md
…v0.5.3 Main 2ce7726 (#850) has one unreleased section again, `## v0.5.3 (unreleased)`, and no release until everything is done (the owner's decision). CHANGELOG.md conflicted at the top, where this branch had `## v0.5.4 (unreleased)` above the released heading. Resolved by dropping the v0.5.4 section and putting its two #726 bullets in v0.5.3 (unreleased): the existing-install step at the end of "Upgrading (from v0.5.2)", and the guardrail note at the end of the last "Guardrail changes: what each one does", above the closing empty "### Guardrail changes". `git diff origin/main -- CHANGELOG.md` is those two added lines only. Every other path is main's, merged automatically. Signed-off-by: Jayden Vasquez <jaydenvasquez1711@gmail.com>
… the voice and Siri removal notes move into v0.5.3 The owner folded the unreleased notes into one v0.5.3 (unreleased) section: the Removals bullet moves there, above its closing Guardrail changes heading, and the v0.5.4 section goes. Signed-off-by: Jayden Vasquez <jaydenvasquez1711@gmail.com>
…s fold into v0.5.3 Brings #769's fold: main 2ce7726 (#850) has one unreleased section, `## v0.5.3 (unreleased)`, and no release until everything is done (the owner's decision). The release that ships set-policy is now 0.5.3. CHANGELOG.md conflicted at the top, where this branch had `## v0.5.4 (unreleased)`. Resolved by dropping that section and putting every #726 entry in v0.5.3 (unreleased): the three Upgrading bullets, the set-policy sudoers note under After install, and the full guardrail note (it replaces #769's shorter one) above the closing empty "### Guardrail changes". A correction, made on purpose: v0.5.3's After-install bullet "No sudoers rule is added, so no machine-helper rerun" is removed. It is false once this PR is in v0.5.3, which adds set-policy's sudoers rules. The set-policy note takes its place and keeps its other true sentences (the owner terminal's rule removed by the dashboards.sh rerun; the three claude-account lines granting nothing). docs/releasing.md step 9: the 0.5.3 entry says yes (set-policy, #726), and the 0.5.4 line is gone. Otherwise `git diff origin/main -- CHANGELOG.md docs/releasing.md` is additions inside v0.5.3 only. Signed-off-by: Jayden Vasquez <jaydenvasquez1711@gmail.com>
…738-claude-runtime Signed-off-by: Jayden Vasquez <jaydenvasquez1711@gmail.com> # Conflicts: # CHANGELOG.md # test/init.test.ts
…-783-weakening-hold Signed-off-by: Jayden Vasquez <jaydenvasquez1711@gmail.com> # Conflicts: # CHANGELOG.md
…se lists it from the PR title Main's v0.5.3 section is unreleased again (#850). It holds only hand-written upgrade and guardrail notes, and the generated PR lists come back at the release. A test-only change has no upgrade or guardrail note to write. Test (fails without): none; this changes CHANGELOG.md only, back to main's text before #850. Signed-off-by: Jayden Vasquez <jaydenvasquez1711@gmail.com>
Main (#850) dropped the generated Features/Fixes/Security lists from the unreleased v0.5.3 section. The bullet for this PR moves to "Guardrail changes: what each one does", above the closing "### Guardrail changes", and names the PR (#852). Signed-off-by: Jayden Vasquez <jaydenvasquez1711@gmail.com>
Intent: The owner decided on 2026-10-19 that nothing is released until everything is done, and that the CHANGELOG keeps one unreleased section. #828 dated that section as
## v0.5.3 (2026-10-19). This PR puts it back to## v0.5.3 (unreleased).package.jsonstays at 0.5.3.Risk class: docs-only. Only
CHANGELOG.mdchanges. It isn't in.worklane/review.yamlorsrc/review.ts(measured:grep -rn CHANGELOG .worklane src/review.tsfinds nothing).What changed
## v0.5.3 (unreleased)again.### Features,### Fixes,### Security and guardrails, and the PR lines under### Guardrail changes(122 lines). An empty### Guardrail changesheading stays after the hand-written notes, as the closing heading the release keeps them above.Why the lists went (measured)
test/changelog.test.ts"an unreleased section is all hand-written, so the release keeps every line of it, under any heading" failed: 7 pass, 1 fail.- Pin the engine to v0.5.2 (#578).The release regenerates them (measured)
scripts/lib/changelog.mjswas run in memory, with no writes. Fed the 108 PRs the removed lines name (titles, numbers, and guardrail files from the removed lines),changelogSection('0.5.3', …)writes exactly the removed block: 123 lines, identical and in the same order.groupOfputs every PR in the group it was listed under.node scripts/release.mjs changelog 0.5.3writes them again when the owner cuts the release.How it was verified
All measured, in the worktree, against
origin/main71316eb.git diff --stat origin/main -- CHANGELOG.md: 1 insertion, 123 deletions. The one added line is the heading. The deleted lines are the old heading and the 122 generated lines.withSection(text, '0.5.3', changelogSection('0.5.3', …))in memory: all 148 hand-written lines are kept, with both 0 and 1 PR. The only other line, the empty### Guardrail changesheading, is kept too.node --import ./dist/test/isolate.js --test dist/test/changelog.test.js dist/test/comment-policy-cli.test.js: 15 pass, 0 fail. That includes all 10 changelog tests.owner-terminal-removed:PATHto<bin>:/usr/bin:/binwith stand-ins for sudo, bash and id only, so CI runs them.--test-name-pattern="one placeholder version"), and it spawns nothing: 1 pass.test/release.test.tswasn't run locally (it signs throwaway tags). CI runs it.npm run check:denylist: 1309 files clean.Adversarial pass
comment-policy-clipasses 5 of 5. An "(unreleased)" section isn't a release, and 0.5.3 is the next release after 0.5.2.Package size
No change: 0 bytes (measured).
CHANGELOG.mdisn't in the package:npm pack --dry-run --jsonlists no CHANGELOG entry (473 entries).New dependencies
None.