Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update yarn to v1.22.22 #518

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 1, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
yarn 1.22.19 -> 1.22.22 age adoption passing confidence

Release Notes

yarnpkg/yarn (yarn)

v1.22.22

Compare Source

[!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

Compare Source

[!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

Compare Source

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

  • 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 - "before 7am on the first day of the month" in timezone GMT, Automerge - 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/yarn-1.x branch from 58ea66f to 7c8672b Compare April 1, 2024 00:55
@renovate renovate bot changed the title chore(deps): update yarn to v1.22.21 chore(deps): update yarn to v1.22.22 Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants