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>
845 B
type, pr
| type | pr |
|---|---|
| Fixed | 3011 |
Actionable diagnostic when gsd-sdk is not on PATH after install — Windows users (and others on multi-shell setups) reported that the previous "GSD SDK files are present but gsd-sdk is not on your PATH" warning gave them no way to fix it: no path to look at, no shell-specific commands, no mention of the npx-cache caveat. New formatSdkPathDiagnostic({ shimDir, platform, runDir }) helper returns a typed IR with the resolved shim location, platform-specific PATH-export commands (PowerShell / cmd.exe / Git Bash on Windows; export PATH on POSIX), and an npx-specific note when running under an _npx cache segment (where the shim may be written to a temp dir that won't persist). The console renderer in bin/install.js emits the lines from the IR; tests assert on the typed fields directly. (#3011)