-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hotfixes for the 1.22.20 #9009
Hotfixes for the 1.22.20 #9009
Conversation
@arcanis Hello it seems like latest version of yarn brings regression, it cannot find nearest package.json file. So having package.json in root of the project and trying to run
Downgrade to |
Can you give me a reproduction? According to your post the following should crash, but doesn't for me:
|
Dockerfile
|
Sorry for bothering. #7939 |
Fixes #8793
Fixes #8965
Fixes #9005
Punycode is now embed within the bundle, as it has been deprecated by Node.js and will be removed in a future version.
A message will be displayed when Yarn 1.22 notices that the local project has a
package.json
file referencing a non-1.x Yarn release. The message will explain that the project is intended to be used with Corepack.I removed the
yarn-error.log
generation. Given that we don't process non-critical 1.x bug reports, they are now mostly an annoyance.The
yarn set version x.y.z
command will now install the exactx.y.z
version (prior to this change it used to first install the latest version, and only in a second step would it downgrade tox.y.z
; this was causing issues when we bump the minimal Node.js version we support, as runningyarn set version 3.6.4
wouldn't work on Node 16).Prevents crashes when reading from an empty
.yarnrc.yml
file.