build(deps): bump yarn from 1.22.4 to 1.22.21

[dependabot]

Bumps yarn from 1.22.4 to 1.22.21.

Release notes

Sourced from yarn's releases.

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

No release notes provided.

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

v1.22.12

Bogus release (published the wrong folder)

v1.22.11

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.

... (truncated)

Changelog

Sourced from yarn's changelog.

Changelog

Please add one entry in this file for each change in Yarn's behavior. Use the same format for all entries, including the third-person verb. Make sure you don't add more than one line of text to keep it clean. Thanks!

1.22.11

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).

1.22.10 (and prior)

• Tweak the preinstall check to not cause errors when Node is installed as root (as a downside, it won't run at all on Windows, which should be an acceptable tradeoff): yarnpkg/yarn#8358

1.22.7

This release doesn't change anything and was caused by a publish issue.

1.22.6

• Running yarn init with the -2 flag won't print the set version output anymore.

• A new preinstall check will ensure that npm install -g yarn works even under Corepack. It doesn't have any effect on other setups.

1.22.5

• Headers won't be printed when calling yarn init with the -2 flag

  Maël Nison

• Files with the .cjs extension will be spawned by yarnPath using `execPath

  #8144 - bgotink

• Generates local yarn verions as .cjs files when calling yarn set version

  #8145 - bgotink

• Sorts files when running yarn pack to produce identical layout on Windows and Unix systems

  #8142 - Merceyz

Commits

• 1c6b097 v1.22.21
• a847238 Fixes the projectRoot detection
• efdccc1 Hotfixes for the 1.22.20 (#9009)
• 015b20b v1.22.19
• 5b2ac04 Adds support for npm-notice during OTP requests
• 751c895 v1.22.18
• 64e931d Fixes url.resolve join
• 2d73345 v1.22.17
• ac3d011 Removes the remaining message
• efa4cbb v1.22.16
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.