Zoltan Kochan f9d6871a3d 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.		2026-04-30 22:24:36 +02:00
..
index.js	fix: revert npm to PATH lookup; runner externals lacks npm	2026-04-30 22:24:36 +02:00