msd-core/.changeset/archived/windows-npm-shell-fix.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

462 B

Raw Blame History

type, pr

type	pr
Fixed	3102

Windows update-check no longer silently fails — gsd-check-update-worker now passes shell: true only on Windows, allowing execFileSync('npm', ...) to resolve npm.cmd via PATHEXT. POSIX path (Linux/macOS) is unchanged. Without this fix, the worker failed with ENOENT, latest stayed null, update_available became null, and the statusline ⬆ /gsd-update indicator never rendered for Windows users. Fixes #3103.

462 B Raw Blame History

462 B

Raw Blame History