You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3e4586e
Browse filesBrowse the repository at this point in the historyBrowse files
# Decision: Windows Insider Release Validation Environment
2
+
3
+
**By:** Surgeon
4
+
**Date:** 2026-05-04
5
+
6
+
## Context
7
+
8
+
Insider release `0.9.5-insider.2` was validated from Windows PowerShell. Default local environment introduced false negatives in release verification:
9
+
-`process.execPath` contained spaces (`C:\Program Files\nodejs\node.exe`), which broke `scheduler.test.ts`
10
+
- temp paths under the repo or user home caused `team-root`, `init`, and `upgrade` tests to discover a real `.squad/` unexpectedly
11
+
- one or two full-suite failures remained flaky timeout cases, but they passed on targeted rerun
12
+
13
+
## Decision
14
+
15
+
For Windows release validation, isolate the test environment before running the standard vitest command:
16
+
1. Put a no-space Node path first on `PATH` (junction `C:\src\squad\.nodebin -> C:\Program Files\nodejs`)
17
+
2. Set `TEMP` and `TMP` to `C:\src\squad-release-tmp` (outside the repo and home `.squad` tree)
18
+
3. Keep `SKIP_BUILD_BUMP=1`
19
+
4. If the full vitest run fails only on timeout-based flakes, rerun the failing file(s) to confirm there is no deterministic regression before blocking the release
20
+
21
+
## Rationale
22
+
23
+
This preserves the release checklist while removing machine-specific false failures. The decision is validation-only; it does not change published package contents or release semantics.
0 commit comments