v1.22.22

• Fixes a punycode warning.

• Fixes a hoisting issue when transitive dependencies themselves listed aliases as dependencies.

v1.22.21

Warning

This release is missing a couple of artifacts (the .msi/.rpm/.deb/.asc files); we're working on fixing this.

• Fixes an issue in the v1.22.20 when calling Yarn from a project subfolder, outside of a Corepack context.

• Added a SKIP_YARN_COREPACK_CHECK environment variable to skip the Corepack check.

v1.22.20

Warning

This release is missing a couple of artifacts (the .msi/.rpm/.deb/.asc files); we're working on fixing this.

• Important: 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 via the packageManager field. The message will explain that the project is intended to be used with Corepack.

• The yarn-error.log files won't be generated anymore, as we don't process non-critical 1.x bug reports (we however process all bugs reported on https://github.com/yarnpkg/berry; we just released the 4.0.2 release there).

• The yarn set version x.y.z command will now install the exact x.y.z version (prior to this change it used to first install the latest version, and only in a second step would it downgrade to x.y.z; this was causing issues when we bump the minimal Node.js version we support, as running yarn set version 3.6.4 wouldn't work on Node 16).

• Prevents crashes when reading from an empty .yarnrc.yml file.

v1.22.19

• Adds compatibility with WebAuthn on the npm registry

v1.22.18

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.

v1.22.17

Strangely this released disappeared from GitHub, re-adding it.

v1.22.16

v1.22.16

v1.22.15

• Fixes an issue on Windows where relative scripts would fail to execute

v1.22.14

• Fixes false positives that would happen on non-win32 platforms ("Potentially dangerous call to ...")

v1.22.13

• Fixes a potential security issue where packages could run scripts even with --ignore-builds set (Windows only)
• Fixes yarn init -y2 w/ Corepack
• yarn set version stable (and canary) will now defer to the stable & canary for upgrading the project