26f6d4f2c5
Some checks are pending
Test Action / Test with default inputs (ubuntu-latest, 9.15.5) (push) Waiting to run
Test Action / Test with default inputs (windows-latest, 9.15.5) (push) Waiting to run
Test Action / Test with dest (macos-latest, 9.15.5) (push) Waiting to run
Test Action / Test with dest (ubuntu-latest, 9.15.5) (push) Waiting to run
Test Action / Test with dest (windows-latest, 9.15.5) (push) Waiting to run
Test Action / Test with standalone (ubuntu-latest) (push) Waiting to run
Test Action / Test with standalone (windows-latest) (push) Waiting to run
Test Action / Test version input is actually installed (10.33.0, macos-latest) (push) Waiting to run
Test Action / Test version input is actually installed (9.15.5, macos-latest) (push) Waiting to run
Test Action / Test with default inputs (macos-latest, 9.15.5) (push) Waiting to run
Test Action / Test packageManager field is respected (9.15.5, windows-latest) (push) Waiting to run
Test Action / Test with devEngines.packageManager (macos-latest, 9.15.5) (push) Waiting to run
Test Action / Test with devEngines.packageManager (macos-latest, >=9.15.0) (push) Waiting to run
Test Action / Test with devEngines.packageManager (ubuntu-latest, 9.15.5) (push) Waiting to run
Test Action / Test version input is actually installed (10.33.0, ubuntu-latest) (push) Waiting to run
Test Action / Test version input is actually installed (9.15.5, ubuntu-latest) (push) Waiting to run
Test Action / Test version input is actually installed (10.33.0, windows-latest) (push) Waiting to run
Test Action / Test version input is actually installed (9.15.5, windows-latest) (push) Waiting to run
Test Action / Test packageManager field is respected (10.33.0, macos-latest) (push) Waiting to run
Test Action / Test packageManager field is respected (9.15.5, macos-latest) (push) Waiting to run
Test Action / Test packageManager field is respected (10.33.0, ubuntu-latest) (push) Waiting to run
Test Action / Test packageManager field is respected (9.15.5, ubuntu-latest) (push) Waiting to run
Test Action / Test packageManager field is respected (10.33.0, windows-latest) (push) Waiting to run
Test Action / Test with devEngines.packageManager (ubuntu-latest, >=9.15.0) (push) Waiting to run
Test Action / Test with devEngines.packageManager (windows-latest, 9.15.5) (push) Waiting to run
Test Action / Test with devEngines.packageManager (windows-latest, >=9.15.0) (push) Waiting to run
Test Action / Test with run_install (global, macos-latest) (push) Waiting to run
Test Action / Test with run_install (null, macos-latest) (push) Waiting to run
Test Action / Test with run_install (global, ubuntu-latest) (push) Waiting to run
Test Action / Test with run_install (null, ubuntu-latest) (push) Waiting to run
Test Action / Test with run_install (global, windows-latest) (push) Waiting to run
Test Action / Test with run_install (null, windows-latest) (push) Waiting to run
* fix: use npm co-located with the action node binary * fix: resolve npm by absolute path; guard against unset PATH Follow-up to 5a9e198. Two refinements to the GHE self-hosted runner fix: - Spawn npm via `path.join(dirname(process.execPath), 'npm[.cmd]')` instead of relying on PATH lookup. This matches the original PR description and is robust against PATH-shadowed npm installations. - Avoid `"<dir>:undefined"` leaking into PATH when `process.env.PATH` is unset (rare, but possible in stripped environments). PATH still has the node directory prepended so npm's `#!/usr/bin/env node` shebang can resolve node on Linux/macOS. * fix: revert npm to PATH lookup; runner externals lacks npm Revert 42e75a1's switch to absolute-path npm resolution. The premise that npm is co-located with the action's node binary is false on GitHub-hosted runners: `process.execPath` points into `runner/externals/node24/bin/`, which contains node only — not npm. The absolute-path spawn produced ENOENT on Linux/macOS and "not recognized" on Windows. Go back to spawning `'npm'` and relying on PATH lookup, which works on standard runners (npm is on PATH from the runner image) and on the GHE self-hosted setup that motivated the original fix. Keep the node-directory prepend so npm's `#!/usr/bin/env node` shebang resolves, and keep the unset-PATH guard. --------- Co-authored-by: Zoltan Kochan <z@kochan.io>