msd-core/.changeset/archived/fix-3406-detect-stale-sdk-shadow.md at 9e2ef2c94dea3f1267deba570c9a423fb38c2f85

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

482 B

Raw Blame History

type, pr

type	pr
Fixed	3641

Install-time warning when a stale @open-gsd/sdk shadows the bundled gsd-sdk shim — global installs now run npm ls -g @open-gsd/sdk and, if the standalone 0.1.0 package is present (it never received query subcommand support), print a clear remediation block before the install completes. Detection is fail-closed: any npm/exec error silently returns no-stale. Gated by GSD_SKIP_STALE_SDK_CHECK=1 for CI/test environments. Resolves #3406.

482 B Raw Blame History

482 B

Raw Blame History