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

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 11, 2021

This PR contains the following updates:

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

v1.22.4

Compare Source

Those versions didn't contain any changes and were just triggered by our infra while working on the tests.

v1.22.1

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

Compare Source

v1.21.1

Compare Source

v1.21.0

Compare Source

v1.19.2

Compare Source

  • Folders like .cache won't be pruned from the node_modules after each install.

    #​7699 - Maël Nison

  • Correctly installs workspace child dependencies when workspace child not symlinked to root.

    #​7289 - Daniel Tschinder

  • Makes running scripts with Plug'n Play possible on node 13.

    #​7650 - Sander Verweij

  • Change run command to check cwd/node_modules/.bin for commands. Fixes run in workspaces.

    #​7151 - Jeff Valore

v1.19.1

Compare Source

Important: This release contains a cache bump. It will cause the very first install following the upgrade to take slightly more time, especially if you don't use the Offline Mirror feature. After that everything will be back to normal.

v1.19.0

Compare Source

Important: This release contains a cache bump. It will cause the very first install following the upgrade to take slightly more time, especially if you don't use the Offline Mirror feature. After that everything will be back to normal.

  • Fixes a potential vulnerability regarding how the build artifacts are stored

    Reported by ChALkeR, fixed by Maël Nison

v1.18.0

Compare Source

v1.17.3

Compare Source

v1.17.2

Compare Source

v1.17.1

Compare Source

v1.17.0

Compare Source

v1.16.0

Compare Source

v1.15.2

Compare Source

The 1.15.1 doesn't exist due to a release hiccup.

  • Reverts a behavior causing boggus interactions between PowerShell and yarn global

    #​6954 - briman0094

  • Fixes a bug where non-zero exit codes were converted to a generic 1 when running yarn run

    #​6926 - Kyle Fang

  • Fixes production / development reporting when running yarn audit

    #​6970 - Adam Richardson

v1.15.1

Compare Source

v1.15.0

Compare Source

v1.14.0

Compare Source

v1.13.0

Compare Source

v1.12.3

Compare Source

Important: This release contains a cache bump. It will cause the very first install following the upgrade to take slightly more time, especially if you don't use the Offline Mirror feature. After that everything will be back to normal.

  • Fixes an issue with yarn audit when using workspaces

    #​6625 - Jeff Valore

  • Uses NODE_OPTIONS to instruct Node to load the PnP hook, instead of raw CLI arguments

    Caveat: This change might cause issues for PnP users having a space inside their cwd (cf nodejs/node#24065)

    #​6479 - Maël Nison

  • Fixes Gulp when used with Plug'n'Play

    #​6623 - Maël Nison

  • Fixes an issue with yarn audit when the root package was missing a name

    #​6611 - Jack Zhao

  • Fixes an issue with yarn audit when a package was depending on an empty range

    #​6611 - Jack Zhao

  • Fixes an issue with how symlinks are setup into the cache on Windows

    #​6621 - Yoad Snapir

  • Upgrades inquirer, fixing upgrade-interactive for users using both Node 10 and Windows

    #​6635 - Philipp Feigl

  • Exposes the path to the PnP file using require.resolve('pnpapi')

    #​6643 - Maël Nison

v1.12.1

Compare Source

v1.12.0

Compare Source

v1.11.1

Compare Source

v1.11.0

Compare Source

v1.10.1

Compare Source

v1.10.0

Compare Source

v1.9.4

Compare Source

No changes, release process improvements

v1.9.2

Compare Source

Fixes a small Windows bug with yarn pack.

v1.9.1

Compare Source

No changes, purely for release processes.

v1.8.0

Compare Source

  • feat(cli): enable emoji on Hyper terminal (#​5875)

    Pig Fang - Mon, 11 Jun 2018 10:42:47 +0100

  • Make sure TarballFetcher error messages contain names of problematic files (#​5964)

    sth - Mon, 11 Jun 2018 10:37:48 +0100

  • Remove logic to skip updating of existing symlinks (#​5751)

    Wolfgang Beyer - Fri, 8 Jun 2018 23:47:07 +0100

  • Check for ENOENT, add tests (#​5938)

    Eelco Lempsink - Fri, 8 Jun 2018 16:41:14 +0100

  • fix(autoclean): Fixes autoclean when used with workspaces

    Maël Nison - Fri, 8 Jun 2018 16:38:47 +0100

  • fix(import): warn and normally resolve dep missing from package-lock.json (#​5947)

    Aram Drevekenin - Fri, 8 Jun 2018 16:11:34 +0100

  • chore: Better error handling and tests in TarballFetcher (#​5845)

    sth - Fri, 8 Jun 2018 11:39:50 +0100

  • add ability to publish non-interactively without version bumping (#​5748)

    Pei Jie - Wed, 6 Jun 2018 18:24:22 +0100

  • fix: don't use folder name to determine focused package name (fix #​5881) (#​5893)

    Bryan Wain - Tue, 5 Jun 2018 16:28:40 +0200

  • Replace nodejs dependency with nodejs-lts. (#​5925)

    Ilkka Halila - Tue, 5 Jun 2018 16:25:08 +0200

  • fix(deps): change cmd-shim to @​zkochan/cmd-shim (#​5927)

    Doma - Tue, 5 Jun 2018 16:23:18 +0200

  • feat(install): warn if a package-lock.json file exists

    Jeremy Morrell - Fri, 1 Jun 2018 18:09:37 +0200

  • fix(info): report empty npm response with infoFail again (#​5915)

    sth - Thu, 31 May 2018 17:23:09 +0100

  • fix(lockfile): remove yet-unreleased integrity field (#​5911)

    Aram Drevekenin - Wed, 30 May 2018 08:56:25 -0400

  • fix(info): handle 404 with non-empty body (#​5903)

    Aram Drevekenin - Tue, 29 May 2018 22:12:05 +0100

  • fix(github-resolver): support for semver hash (#​5858)

    Daniel Lenksjö - Tue, 29 May 2018 11:23:01 +0200

  • Update Debian package to "conflict" with cmdtest (#​5898)

    Daniel Lo Nigro - Mon, 28 May 2018 23:22:45 +0100

  • fix bin links for link: protocol (fixes #​5876) (#​5879)

    Bryan Wain - Fri, 25 May 2018 00:26:17 -0700

  • Support MSYS{2} bash in bin/yarn (#​5859)

    akrieger - Thu, 24 May 2018 09:52:31 -0700

  • ci(brew): Pass access token to Homebrew job (#​5862)

    Daniel Lo Nigro - Thu, 24 May 2018 12:59:31 +0100


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 changed the title chore(deps): update yarn to v1.22.10 chore(deps): update yarn to v1.22.17 Oct 18, 2021
@renovate renovate bot changed the title chore(deps): update yarn to v1.22.17 chore(deps): update yarn to v1.22.18 Mar 26, 2022
@renovate renovate bot changed the title chore(deps): update yarn to v1.22.18 chore(deps): update yarn to v1.22.19 Jun 18, 2022
@renovate renovate bot changed the title chore(deps): update yarn to v1.22.19 chore(deps): update yarn to v1.22.19 - autoclosed Apr 4, 2023
@renovate renovate bot closed this Apr 4, 2023
@renovate renovate bot deleted the renovate/yarn-1.x branch April 4, 2023 01:21
@renovate renovate bot changed the title chore(deps): update yarn to v1.22.19 - autoclosed chore(deps): update yarn to v1.22.19 Apr 4, 2023
@renovate renovate bot reopened this Apr 4, 2023
@renovate renovate bot restored the renovate/yarn-1.x branch April 4, 2023 11:26
@renovate renovate bot changed the title chore(deps): update yarn to v1.22.19 chore(deps): update yarn to v1.22.21 Nov 14, 2023
Copy link
Author

renovate bot commented Nov 14, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

@renovate renovate bot changed the title chore(deps): update yarn to v1.22.21 chore(deps): update yarn to v1.22.22 Mar 10, 2024
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