chore: run yarn after new release #7715
Merged
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
thymikee
approved these changes
Jan 26, 2019
milesj
reviewed
Jan 26, 2019
| @@ -2182,6 +2182,31 @@ [email protected]: | |||
| 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.
This lock is pulling in Jest 23 and Babel 6. Is that correct?
There was a problem hiding this comment.
"correct" is relative 😛: #7707 (comment)
|
+1 for |
captain-yossarian
pushed a commit
to captain-yossarian/jest
that referenced
this pull request
Jul 18, 2019
|
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. |
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.
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-lockfileon ci?