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>
561 B
561 B
type, pr
| type | pr |
|---|---|
| Fixed | 643 |
Wave-cleanup no longer refuses merge-back for an orchestrator running from a non-primary worktree — the two execute-phase wave-cleanup guards now pin to the dispatch-time orchestrator root persisted in WAVE_WORKTREE_MANIFEST, instead of git worktree list's first entry (always the main checkout). A per-phase-lane orchestrator with workflow.use_worktrees: true is no longer cd'd off its own branch into the #3174 branch-drift assertion at cleanup. Byte-identical for a primary-worktree orchestrator. Follow-up to #590.