Update dependency yarn to ^1.22.18

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
yarn	^1.22.1 -> ^1.22.18

Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.

---

Release Notes

yarnpkg/yarn

v1.22.18

Compare Source

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

Compare Source

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

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

v1.22.10

• 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): https://github.com/yarnpkg/yarn/issues/8358

v1.22.7

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

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

v1.22.5

Compare Source

• 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

v1.22.4

Compare Source

Those versions didn't contain any changes and were just triggered by our infra while working on the tests.

---

Configuration

📅 Schedule: Branch creation - "on the 1st through 7th day of the month" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 Mend Renovate. View repository job log here.