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>
640 B
640 B
type, pr
| type | pr |
|---|---|
| Fixed | 3805 |
fast.md log_to_state no longer appends a malformed row when the STATE.md table uses the 5-column quick.md schema (#3805) — the workflow unconditionally wrote a hardcoded 4-cell row (| date | fast | task | ✅ |) into STATE.md; when quick.md Step 7 had already created a 5-column "Quick Tasks Completed" table the mismatched row broke the Markdown table. fast.md now reads the existing header, counts columns, and verifies the quick.md column names before appending a properly-formed 5-cell row. If the schema is unrecognized the write is skipped with a warning rather than corrupting the table.