CHANGELOG promotion was a manual operator step that was never run, so 463 fragments for work already shipped in <=1.3.1 accumulated in .changeset/. Their notes were already hand-curated into the dated [1.2.0]/[1.3.0]/[1.3.1] CHANGELOG sections (#690 backfill, PR #694). Rendering them now would duplicate and mis-attribute shipped work. Move them to .changeset/archived/ (read non-recursively by all changeset tooling, so never rendered), keeping only the 3 genuinely-unreleased fragments at the top level. Prep for wiring `render` into the release finalize job (#690 follow-up). Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
405 B
405 B
type, pr
| type | pr |
|---|---|
| Fixed | 640 |
gsd-tools query summary-extract no longer drops snake_case requirements_completed — the reader now accepts both the kebab requirements-completed and the snake requirements_completed key forms (the snake form is what the tool's own JSON output and the milestone audit --pick emit), so a round-tripped requirements field is no longer silently read back as empty.