chore(gatsby): Update more dependencies to support graphql@14 #11512
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
|
Looks like broken CI has nothing to do to the changes. @janicduplessis could you try rebasing this PR? |
janicduplessis
force-pushed
the
update-graphql-deps
branch
from
d079e7d to
811e431
Compare
|
@RomanGotsiy Rebased, tests are now passing |
sidharthachatterjee
approved these changes
Mar 8, 2019
sidharthachatterjee
changed the title
|
Published in |
|
@janicduplessis @RomanGotsiy Unfortunately this had to be reverted because the updated |
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.
Description
I noticed a few peer dependencies warning since updating to graphql@14 (#11377), the goal is to fix those by updating some dependencies to the latest version that supports graphql@14. Nothing is broken because of this but this will remove some peer dep warnings.
Verified the changelog of each updated lib to make sure there were no breaking changes affecting us.
Related Issues
Follow up to PR #11377