Update Yarn to v1.22.17

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
yarn	1.22.10 -> 1.22.17

---

Release Notes

yarnpkg/yarn

v1.22.17

Compare Source

v1.22.16

Compare Source

v1.22.15

Compare Source

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

v1.22.14

Compare Source

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

v1.22.13

Compare Source

• 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

Compare Source

Bogus release (published the wrong folder)

v1.22.11

Compare Source

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

---

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (1.22.17). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.