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>
633 B
633 B
type, pr
| type | pr |
|---|---|
| Fixed | 3547 |
Installer migration no longer hangs /gsd:update on leftover GSD-looking files — non-TTY installer runs now default-resolve prompt-user migration actions by classification (stale SDK build artifacts under get-shit-done/sdk/{dist,src}/gsd-* default to remove; user-facing skills/gsd-*/SKILL.md defaults to keep) and log each resolution. Anything that cannot be safely defaulted still blocks, but the error message now groups blocked paths by reason, lists the documented choices, and names the GSD_INSTALLER_MIGRATION_RESOLVE env var as the non-interactive resolution surface. (#3541)