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>
929 B
type, pr
| type | pr |
|---|---|
| Changed | 611 |
Update-check cache is now per-package and lineage-validated, and the installer cleans up leftover get-shit-done-cc installs — after migrating from get-shit-done-cc to @opengsd/gsd-core, a leftover old install in any runtime dir could write a higher latest into the shared update cache and cause a permanent false ⬆ /gsd:update. The cache now uses a per-package filename (gsd-update-check-<slug>.json) carrying a package_name lineage field that readers validate, so a different package can no longer poison the indicator (multi-runtime visibility preserved). The installer now auto-detects and removes leftover get-shit-done-cc artifacts across runtime config dirs on every install; a new --dry-run flag previews the cleanup plan without modifying anything. /gsd:update clears the cache for all 15 supported runtimes. See the new how-to: docs/cleanup-get-shit-done-cc.md.