When Yarn 1.22.8 hit the NPM registry, GitHub Actions started installing it when running npm install -g yarn, and we started seeing failures.
Command
> [email protected] preinstall /opt/hostedtoolcache/node/12.16.3/x64/lib/node_modules/yarn
> :; (node ./preinstall.js >& /dev/null || true)
sh: 1: Syntax error: Bad fd number
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] preinstall: `:; (node ./preinstall.js >& /dev/null || true)`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
What is the current behavior?
npm install -g yarn fails when running the preinstall script.
What is the expected behavior?
npm install -g yarn successfully runs the preinstall script.
Steps to Reproduce
npm install -g yarnEnvironment
12.16.31.22.8 We had the same problem on our build server inside a docker container. We had to run npm install -g [email protected] and it worked, so I guess there is something in the latest version.
Seems it's fixed now
@gonzaloaune Can confirm, seems to be fixed.
We're still experiencing the issue with the latest version (as of writing) v1.22.9. Seems fishy since latest tag in this repo is v1.22.5 - where does the latest 4 patch versions come from?
Resolved with the 1.22.10.
Just as @laander asked, where does the last 5 patch come from ? Are they released from specific commits ?
They are tracked on npm:
https://www.npmjs.com/package/yarn
Maybe just not tagged on github I guess?
Going to close as duplicate of https://github.com/yarnpkg/yarn/issues/8358, which has more details (basically, the tags don't reflect at the moment the releases due to an infra problem. Those commits were published on the 1.22-stable branch.).
Most helpful comment
We had the same problem on our build server inside a docker container. We had to run
npm install -g [email protected]and it worked, so I guess there is something in the latest version.