Node 17.7.0 had a regression in url.resolve which broke Yarn, causing network errors. This release fixes that, although the regression also got fixed on the Node side starting from 17.7.1, so as long as you keep your Node up-to-date it'll be fine.
- Fixes false positives that would happen on non-win32 platforms ("Potentially dangerous call to ...")
- Fixes a potential security issue where packages could run scripts even with
--ignore-buildsset (Windows only) - Fixes
yarn init -y2w/ Corepack yarn set version stable(andcanary) will now defer to the stable & canary for upgrading the project
This version fixes a problem where Yarn wasn't forwarding SIGTERM to the binary spawned via yarnPath. It also makes yarn init -2 compatible with Corepack. The behaviour of yarn init (without -2) doesn't change.
Remember that Yarn 1.x won't receive further functional improvements. We recommend you to switch to the recently-released 3.0, and to ping us on Discord if you find issues when migrating (also check our Migration Guide).
(and prior)
Please check the changelog for details: https://github.com/yarnpkg/yarn/blob/master/CHANGELOG.md
For technical reasons, no prebuilt artifacts will be generated for this release. Please use npm install -g yarn to install it.