msd-core/.changeset/archived/3033-sdk-flag-wired.md at 837991d5a298695ee8c69b10d1fdb1d8e6b41084

Files

Tom Boucher 8616839cab chore: archive 463 shipped changeset fragments before wiring render (#714 )

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>

2026-06-05 14:53:17 -04:00

561 B

Raw Blame History

type, pr

type	pr
Fixed	3033

--sdk flag now wired into SDK deployment — hasSdk was parsed in bin/install.js but never passed to installSdkIfNeeded, so npx get-shit-done-cc@latest --sdk silently skipped SDK deployment and produced a misleading "✓ GSD SDK ready" message. installSdkIfNeeded now accepts forceSdk: true (set when --sdk is passed), which bypasses the local-install soft-skip and runs the full shim-link path so gsd-sdk is materialized on PATH. The #2678 soft-skip for local installs without --sdk is preserved. (#3033)

561 B Raw Blame History

561 B

Raw Blame History