Closed ScriptedAlchemy closed 3 years ago
Latest commit: 5b6a257dbca73670ef98db1a81bd3cfd7a40ef1f
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
As this PR has been closed unmerged, Renovate will now ignore this update (1.22.11). 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.
This PR contains the following updates:
1.22.10
->1.22.11
Release Notes
yarnpkg/yarn
### [`v1.22.11`](https://togithub.com/yarnpkg/yarn/blob/master/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: 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.
This PR has been generated by Renovate Bot.