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 #1574

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 6, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
yarn 1.22.4 -> 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.

v1.22.19

Compare Source

  • Adds compatibility with WebAuthn on the npm registry

v1.22.18

Compare Source

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

Compare Source

Strangely this released disappeared from GitHub, re-adding it.

v1.22.16

Compare Source

v1.22.15

Compare Source

  • Fixes an issue on Windows where relative scripts would fail to execute

v1.22.14

Compare Source

  • Fixes false positives that would happen on non-win32 platforms ("Potentially dangerous call to ...")

v1.22.13

Compare Source

  • 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

Compare Source

Bogus release (published the wrong folder)

v1.22.11

Compare Source

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

v1.22.10

v1.22.7

This release doesn't change anything and was caused by a publish issue.

v1.22.6

  • Running yarn init with the -2 flag won't print the set version output anymore.

  • A new preinstall check will ensure that npm install -g yarn works even under Corepack. It doesn't have any effect on other setups.

v1.22.5

Compare Source

  • Headers won't be printed when calling yarn init with the -2 flag

    Maël Nison

  • Files with the .cjs extension will be spawned by yarnPath using `execPath

    #​8144 - bgotink

  • Generates local yarn verions as .cjs files when calling yarn set version

    #​8145 - bgotink

  • Sorts files when running yarn pack to produce identical layout on Windows and Unix systems

    #​8142 - Merceyz


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

Rebasing: Whenever PR is behind base branch, 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 4 times, most recently from b533eab to 0b504ab Compare July 22, 2024 08:35
@renovate renovate bot force-pushed the renovate/yarn-1.x branch 5 times, most recently from 5311a11 to 0e0258f Compare July 26, 2024 10:39
@renovate renovate bot force-pushed the renovate/yarn-1.x branch 4 times, most recently from cb425e3 to aafe27d Compare August 6, 2024 21:12
@renovate renovate bot force-pushed the renovate/yarn-1.x branch from aafe27d to 0d0ce1d Compare August 13, 2024 14:50
@renovate renovate bot force-pushed the renovate/yarn-1.x branch from 0d0ce1d to 52f9311 Compare August 23, 2024 01:03
@renovate renovate bot force-pushed the renovate/yarn-1.x branch 4 times, most recently from 4f1d416 to 4be3520 Compare September 19, 2024 13:18
@renovate renovate bot force-pushed the renovate/yarn-1.x branch from 4be3520 to cf134fb Compare September 26, 2024 22:21
@renovate renovate bot force-pushed the renovate/yarn-1.x branch from cf134fb to 0b86cd4 Compare October 4, 2024 01:18
@renovate renovate bot force-pushed the renovate/yarn-1.x branch from 0b86cd4 to 0de9f48 Compare November 11, 2024 10:36
@renovate renovate bot force-pushed the renovate/yarn-1.x branch from 0de9f48 to 1a38f27 Compare December 7, 2024 02:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants