8616839cab
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>
862 B
type, pr
| type | pr |
|---|---|
| Fixed | 3493 |
extractCurrentMilestone preserves generic ## Phase Details heading — When a roadmap placed shared phase-detail bodies under a non-version-prefixed ## Phase Details heading AFTER a ### 📋 vX.Y+ (Planned) sibling, the entire Phase Details section fell outside the returned milestone slice. gsd-sdk query phase.insert N then reported "Phase N not found in ROADMAP.md" even though ### Phase N: was plainly present. PR #2455 (closing #2422) handled the version-prefixed variant (## v2.0 Phase Details) via the same-version continue branch; this fix extends the same intent to the generic-label variant by appending the trailing Phase Details block (up to the next real milestone boundary or EOF) to the active-milestone slice. The intervening planned-milestone content is skipped so it does not leak in. (#3493)