We were using v6 in a few of our enterprise repos and ran into an issue after the latest version was published.
Running self-installer...
npm warn Unknown user config "always-auth". This will stop working in the next major version of npm.
npm error Class extends value undefined is not a constructor or null
after poking around a bit it seems like #239 has caused it to start picking up the version of Node the runners come with (v24) instead of the version a previous step installed during setup (we have a custom internal action similar to actions/setup-node).
Our setup is
- Self-hosted GHE runner image
- Runner-bundled Node v24 (in
externals/node24/bin/, npm not co-located there)
- User-installed Node v22 via prior
setup-node-equivalent step (with its matched npm 10.x on PATH)
pnpm/action-setup invoked with version: 9
We've confirmed that v6.0.3 works fine and are pinned to that for now.
Based on a quick look at that change I suspect that appending instead of prepending here would get it working, but I haven't been able to setup a fork to validate (which actions we can run are pretty locked down).
We were using
v6in a few of our enterprise repos and ran into an issue after the latest version was published.after poking around a bit it seems like #239 has caused it to start picking up the version of Node the runners come with (v24) instead of the version a previous step installed during setup (we have a custom internal action similar to
actions/setup-node).Our setup is
externals/node24/bin/,npmnot co-located there)setup-node-equivalent step (with its matched npm 10.x on PATH)pnpm/action-setupinvoked withversion: 9We've confirmed that v6.0.3 works fine and are pinned to that for now.
Based on a quick look at that change I suspect that appending instead of prepending here would get it working, but I haven't been able to setup a fork to validate (which actions we can run are pretty locked down).