Open
Conversation
5b7c3eb to
7c95b5e
Compare
7c95b5e to
58c9d58
Compare
58c9d58 to
2275281
Compare
2275281 to
218e333
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.17.3->^1.22.17Release Notes
yarnpkg/yarn
v1.22.17Compare Source
v1.22.16Compare Source
v1.22.15Compare Source
v1.22.14Compare Source
v1.22.13Compare Source
--ignore-buildsset (Windows only)yarn init -y2w/ Corepackyarn set version stable(andcanary) will now defer to the stable & canary for upgrading the projectv1.22.12Compare Source
Bogus release (published the wrong folder)
v1.22.11Compare Source
This version fixes a problem where Yarn wasn't forwarding SIGTERM to the binary spawned via
yarnPath. It also makesyarn init -2compatible 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).
v1.22.10v1.22.7This release doesn't change anything and was caused by a publish issue.
v1.22.6Running
yarn initwith the-2flag won't print theset versionoutput anymore.A new preinstall check will ensure that
npm install -g yarnworks even under Corepack. It doesn't have any effect on other setups.v1.22.5Compare Source
Headers won't be printed when calling
yarn initwith the-2flagMaël Nison
Files with the
.cjsextension will be spawned byyarnPathusing `execPath#8144 - bgotink
Generates local yarn verions as
.cjsfiles when callingyarn set version#8145 - bgotink
Sorts files when running
yarn packto produce identical layout on Windows and Unix systems#8142 - Merceyz
Configuration
📅 Schedule: "before 3am on the first day of the month" (UTC).
🚦 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 WhiteSource Renovate. View repository job log here.