-
Notifications
You must be signed in to change notification settings - Fork 38
chore(deps): update yarn to v1.22.22 #1669
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
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/yarn-1.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🚀 Deployed on https://6553cfb075121d05509239f2--pinochle.netlify.app |
🚀 Deployed on https://6553d0050a419d0604f12941--emberclear.netlify.app |
1e0c2ba
to
cb3e77f
Compare
cb3e77f
to
a533b78
Compare
a533b78
to
dec2e82
Compare
dec2e82
to
2135448
Compare
2135448
to
a85dfea
Compare
a85dfea
to
ccd4285
Compare
ccd4285
to
e185aa8
Compare
e185aa8
to
435c77d
Compare
435c77d
to
0bbf64f
Compare
0bbf64f
to
b826cd7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.22
Release Notes
yarnpkg/yarn (yarn)
v1.22.22
Compare Source
Fixes a punycode warning.
Fixes a hoisting issue when transitive dependencies themselves listed aliases as dependencies.
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 - "after 9pm on sunday" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.