yarnpkg/yarn (yarn)
### [`v1.22.22`](https://togithub.com/yarnpkg/yarn/releases/tag/v1.22.22)
[Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.21...v1.22.22)
> \[!WARNING]
> This release is missing a couple of artifacts (the .msi/.rpm/.deb/.asc files); we're working on fixing this.
- Fixes a punycode warning.
- Fixes a hoisting issue when transitive dependencies themselves listed aliases as dependencies.
### [`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.
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.
This PR contains the following updates:
1.22.19->1.22.22Release Notes
yarnpkg/yarn (yarn)
### [`v1.22.22`](https://togithub.com/yarnpkg/yarn/releases/tag/v1.22.22) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.21...v1.22.22) > \[!WARNING] > This release is missing a couple of artifacts (the .msi/.rpm/.deb/.asc files); we're working on fixing this. - Fixes a punycode warning. - Fixes a hoisting issue when transitive dependencies themselves listed aliases as dependencies. ### [`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.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.
This PR has been generated by Mend Renovate. View repository job log here.