chore(deps): update dependency yarn to v1.22.21

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
yarn	`1.22.10` -> `1.22.21`

Release Notes

yarnpkg/yarn (yarn)

### [`v1.22.21`](https://togithub.com/yarnpkg/yarn/releases/tag/v1.22.21) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.20...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`](https://togithub.com/yarnpkg/yarn/releases/tag/v1.22.20) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.19...v1.22.20) - **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](https://nodejs.org/api/corepack.html). - 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`](https://togithub.com/yarnpkg/yarn/releases/tag/v1.22.19) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.18...v1.22.19) - Adds compatibility with WebAuthn on the npm registry ### [`v1.22.18`](https://togithub.com/yarnpkg/yarn/releases/tag/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/tag/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/tag/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/tag/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/tag/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/tag/v1.22.12) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/1.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/1.22.10...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](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: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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, check this box

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

streamich / nano-css

chore(deps): update dependency yarn to v1.22.21 #276

Release Notes

Configuration