v1.22.20

ocrmypdf/OCRmyPDFv1.22.20Nov 14, 2023by arcanis

AI Summary

This release updates Yarn 1.x behavior by embedding deprecated Punycode, changing error logging, and fixing crashes related to empty configuration files.

Key Highlights

Punycode is now embedded within the bundle as it has been deprecated by Node.js
Displays a message when Yarn 1.22 detects a non-1.x Yarn version via the packageManager field
yarn-error.log files are no longer generated for non-critical 1.x bugs
The yarn set version command now installs the exact specified version instead of installing the latest first
Prevents crashes when reading an empty .yarnrc.yml file

New Features

Warning message for projects using non-1.x Yarn versions
Exact version installation behavior for yarn set version
Fix for crashes on empty .yarnrc.yml files

Full Release Notes

> [!WARNING]
> This release is missing a couple of artifacts (the .msi/.rpm/.deb/.asc files); we're working on fixing this.

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