yarnpkg/yarn
### [`v1.22.18`](https://togithub.com/yarnpkg/yarn/releases/v1.22.18)
[Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.17...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`](https://togithub.com/yarnpkg/yarn/releases/v1.22.17)
[Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.16...v1.22.17)
Strangely this released disappeared from GitHub, re-adding it.
### [`v1.22.16`](https://togithub.com/yarnpkg/yarn/compare/v1.22.15...v1.22.16)
[Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.15...v1.22.16)
### [`v1.22.15`](https://togithub.com/yarnpkg/yarn/releases/v1.22.15)
[Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.14...v1.22.15)
- Fixes an issue on Windows where relative scripts would fail to execute
### [`v1.22.14`](https://togithub.com/yarnpkg/yarn/releases/v1.22.14)
[Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.13...v1.22.14)
- Fixes false positives that would happen on non-win32 platforms ("Potentially dangerous call to ...")
### [`v1.22.13`](https://togithub.com/yarnpkg/yarn/releases/v1.22.13)
[Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.12...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`](https://togithub.com/yarnpkg/yarn/releases/v1.22.12)
[Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.11...v1.22.12)
Bogus release (published the wrong folder)
### [`v1.22.11`](https://togithub.com/yarnpkg/yarn/blob/HEAD/CHANGELOG.md#12211)
[Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.10...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](https://togithub.com/nodejs/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](https://yarnpkg.com/getting-started/migration#why-should-you-migrate)).
Configuration
📅 Schedule: "every weekend" in timezone America/Los_Angeles.
🚦 Automerge: Disabled due to failing status checks.
♻ 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 contains the following updates:
1.22.10->1.22.18Release Notes
yarnpkg/yarn
### [`v1.22.18`](https://togithub.com/yarnpkg/yarn/releases/v1.22.18) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.17...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`](https://togithub.com/yarnpkg/yarn/releases/v1.22.17) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.16...v1.22.17) Strangely this released disappeared from GitHub, re-adding it. ### [`v1.22.16`](https://togithub.com/yarnpkg/yarn/compare/v1.22.15...v1.22.16) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.15...v1.22.16) ### [`v1.22.15`](https://togithub.com/yarnpkg/yarn/releases/v1.22.15) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.14...v1.22.15) - Fixes an issue on Windows where relative scripts would fail to execute ### [`v1.22.14`](https://togithub.com/yarnpkg/yarn/releases/v1.22.14) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.13...v1.22.14) - Fixes false positives that would happen on non-win32 platforms ("Potentially dangerous call to ...") ### [`v1.22.13`](https://togithub.com/yarnpkg/yarn/releases/v1.22.13) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.12...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`](https://togithub.com/yarnpkg/yarn/releases/v1.22.12) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.11...v1.22.12) Bogus release (published the wrong folder) ### [`v1.22.11`](https://togithub.com/yarnpkg/yarn/blob/HEAD/CHANGELOG.md#12211) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.10...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](https://togithub.com/nodejs/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](https://yarnpkg.com/getting-started/migration#why-should-you-migrate)).Configuration
📅 Schedule: "every weekend" in timezone America/Los_Angeles.
🚦 Automerge: Disabled due to failing status checks.
♻ 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.