chore(deps): update dependency yarn to v1.22.21 #276
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.22.10
->1.22.21
Release Notes
yarnpkg/yarn (yarn)
v1.22.21
Compare Source
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 exactx.y.z
version (prior to this change it used to first install the latest version, and only in a second step would it downgrade tox.y.z
; this was causing issues when we bump the minimal Node.js version we support, as runningyarn 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
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
v1.22.14
Compare Source
v1.22.13
Compare Source
--ignore-builds
set (Windows only)yarn init -y2
w/ Corepackyarn set version stable
(andcanary
) will now defer to the stable & canary for upgrading the projectv1.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 makesyarn init -2
compatible with Corepack. The behaviour ofyarn 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).
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.