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>
697 B
697 B
type, pr
| type | pr |
|---|---|
| Fixed | 3028 |
Installer no longer prints ✓ GSD SDK ready when the shim is unreachable from the user's runtime shells. The previous check used process.env.PATH from the install subprocess, which often differs from the user's later interactive shells (POSIX ~/.local/bin not in login shell, node-version-manager PATH shims). Added getUserShellPath() helper that probes $SHELL -lc 'printf %s "$PATH"' and isGsdSdkOnPath(pathString?) overload that accepts an explicit PATH; the install-time check now downgrades to the actionable ⚠ diagnostic from PR #3014 when install-PATH and user-shell-PATH disagree. Windows cross-shell support tracked separately. See #3020.