-
Notifications
You must be signed in to change notification settings - Fork 158
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(yarn): upgrade yarn to 1.22.17 #8234
chore(yarn): upgrade yarn to 1.22.17 #8234
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just 1 question about the version
@@ -2,8 +2,8 @@ | |||
# yarn lockfile v1 | |||
|
|||
|
|||
version v1.19.0 | |||
lastUpdateCheck 1597082923381 | |||
version "1.22.10" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this supposed to match up with the release version in yarn-path
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm yeah, this was auto generated and I set the policy to use 1.22.17. Not sure why it says 1.22.10...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gotcha, I guess it should be fine since it was autogenerated and still the same minor version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me if the version mismatch is just from yarn's autogenerating!
@@ -2,8 +2,8 @@ | |||
# yarn lockfile v1 | |||
|
|||
|
|||
version v1.19.0 | |||
lastUpdateCheck 1597082923381 | |||
version "1.22.10" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gotcha, I guess it should be fine since it was autogenerated and still the same minor version
Deploy preview created for package Built with commit: df697dfe820e9b4fce2714a01c95a67cd8fd9a19 |
Deploy preview created for package Built with commit: df697dfe820e9b4fce2714a01c95a67cd8fd9a19 |
Deploy preview created for package Built with commit: df697dfe820e9b4fce2714a01c95a67cd8fd9a19 |
Deploy preview created for package Built with commit: ae2f41d5f1b9964d4687685040859ae96f47f0b3 |
Deploy preview created for package Built with commit: df697dfe820e9b4fce2714a01c95a67cd8fd9a19 |
Deploy preview created for package Built with commit: df697dfe820e9b4fce2714a01c95a67cd8fd9a19 |
Deploy preview created for package Built with commit: df697dfe820e9b4fce2714a01c95a67cd8fd9a19 |
Related Ticket(s)
No related issue
Description
We are seeing connectivity issues with
yarn install
on our CI, this is an attempt to see if this might help at all.Changelog
Changed
1.22.17