Repository navigation
Source candidate replacing unpublished 1.38.6. Tag v1.38.6 stays in place. Exact-tag canonical CI passed on Linux and macOS and failed on Windows unit tests (10 failed, 6288 passed).
Fixed
- Ripgrep text output uses
/between path segments, so a match under a directory whose name contains a space stays onepath:line:textentry on Windows. - Command resolution on Windows follows PATHEXT. A
.cmdshim namedtest-commandis the executable; a POSIX shebang file with no extension is not. - A missing-file read keeps
code: ENOENTand the canonical path. Bun on Windows was reporting the 8.3 short path (RUNNER~1) instead. tool-counts:checkinvokesbun scripts/sync-tool-counts.ts --checkdirectly. On Windows,bun run file.ts --checknever delivered--check, so the aggregate rewrote the drift and exited 0 with an empty stdout. The gate test runs that same aggregate string throughcmd.exeso the exit code and the output are captured.- The range-isolation fixture leaves the temp directory before deleting it. Windows returns EBUSY when the process cwd is the directory being removed.
find-test-leaklocates__tests__beside the script path it was executed from and canonicalizes 8.3 and long temp paths. A copied script was still resolvingimport.meta.dirto the original repo.- Benchmark assertions compare
src/file.tsafter normalizing\, so a Windows absolute path still counts as that fixture.