-
-
Notifications
You must be signed in to change notification settings - Fork 597
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
fix: yarn.lock conflicts on setup #1367
Conversation
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
Looks like the culprit is #1317 |
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.
Don't worry about it, handled in #1339
@snitin315 Thanks for your update. I labeled the Pull Request so reviewers will review it again. @anshumanv Please review the new changes. |
@anshumanv I think still there are some differences after merge #1339 |
What kind of change does this PR introduce?
yarn.lock
file is not up-to-date.To reproduce the error -
upstream/next
yarn
Did you add tests for your changes?
NA
If relevant, did you update the documentation?
NA
Summary
NA
Does this PR introduce a breaking change?
NO
Other information