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>
630 B
630 B
type, pr
| type | pr |
|---|---|
| Fixed | 3130 |
update.md npx invocations hardened against cache-stale and Bash-tool token-routing failures — the previous npx -y get-shit-done-cc@latest form had two failure modes: (1) npx serving a cached older version instead of @latest, and (2) Bash-tool wrappers misrouting the @ token, producing Unknown command: "get-shit-done-cc@latest". All three sibling invocations (local, global, unknown/fallback) now use npx -y --package=get-shit-done-cc@latest -- get-shit-done-cc — the --package= flag forces a fresh registry fetch and the -- separator prevents token misrouting. Closes #3130.