-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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: run yarn after new release #7715
Conversation
@@ -2182,6 +2182,31 @@ babel-code-frame@6.26.0: | |||
esutils "^2.0.2" | |||
js-tokens "^3.0.2" | |||
|
|||
babel-core@^6.0.0, babel-core@^6.26.0: |
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.
This lock is pulling in Jest 23 and Babel 6. Is that correct?
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.
"correct" is relative 😛: #7707 (comment)
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.
That's unfortunate!
+1 for |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Extracting the noisy parts of #7707 and #7714 into a separate PR
Test plan
Green CI, this doesn't really change anything. We might consider running yarn with
--frozen-lockfile
on ci?