This repository has been archived by the owner on Mar 10, 2024. It is now read-only.
Update Yarn to v1.22.22 #50
Open
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
renovate
bot
force-pushed
the
renovate/yarn-1.x
branch
from
ad02207
to
d1d4ceb
Compare
⚠ Artifact update problemRenovate 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:
The artifact failure details are included below: File name: pnpm-lock.yaml |
renovate
bot
force-pushed
the
renovate/yarn-1.x
branch
from
d1d4ceb
to
7d738e2
Compare
renovate
bot
force-pushed
the
renovate/yarn-1.x
branch
from
7d738e2
to
11197b3
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.17->1.22.22Release Notes
yarnpkg/yarn (yarn)
v1.22.22Compare Source
Fixes a punycode warning.
Fixes a hoisting issue when transitive dependencies themselves listed aliases as dependencies.
v1.22.21Compare 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_CHECKenvironment variable to skip the Corepack check.v1.22.20Compare 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
packageManagerfield. The message will explain that the project is intended to be used with Corepack.The
yarn-error.logfiles 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.zcommand will now install the exactx.y.zversion (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.4wouldn't work on Node 16).Prevents crashes when reading from an empty
.yarnrc.ymlfile.v1.22.19Compare Source
v1.22.18Compare Source
Node 17.7.0 had a regression in
url.resolvewhich 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.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.
This PR has been generated by Mend Renovate. View repository job log here.