Bug Fixes
-
keep Windows command lookup within PATH
A report found that an inherited-PATH miss left a bare program name for
shebang probing. That opened a same-named file in the current worktree and
allowed its contents to choose the interpreter, instead of reporting a missing
program. A successful lookup could also be discarded before spawning.Anchor every unresolved bare command before returning, without probing it as
a script, and execute the resolved path on successful lookup. Explicit script
paths retain their shebang behavior. Existing argument-parsing assertions now
account for resolved program names on Windows.Git reference:
compat/mingw.c::path_lookup()andmingw_spawnvpe()at
d38352cd43abfail lookup before parsing an interpreter and execute the resolved
path.
Commit Statistics
- 6 commits contributed to the release over the course of 13 calendar days.
- 13 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Prepare changelogs prior to release (794eeef)
- Merge pull request #3032 from GitoxideLabs/sec-audit (1d7bac7)
- Keep Windows command lookup within PATH (4e1d316)
- Merge pull request #3022 from GitoxideLabs/release-testtools (f819565)
- Use
or_error()at public exception boundaries (535672e) - Merge pull request #3020 from GitoxideLabs/report-september (5fb3dcf)