Update graphql-tools to the latest version 🚀#22
Update graphql-tools to the latest version 🚀#22greenkeeper[bot] wants to merge 1 commit intomasterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #22 +/- ##
=======================================
Coverage 89.02% 89.02%
=======================================
Files 14 14
Lines 82 82
Branches 3 3
=======================================
Hits 73 73
Misses 7 7
Partials 2 2Continue to review full report at Codecov.
|
Version 2.1.0 just got published. |
Version 2.2.0 just got published. |
Version 2.2.1 just got published. |
Version 2.3.0 just got published. |
Version 2.5.0 just got published. |
Version 2.6.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 79 commits.
There are 79 commits in total. See the full diff |
Version 2.6.1 just got published. |
Version 2.7.0 just got published. |
Version 2.7.1 just got published. |
Version 2.7.2 just got published. |
Version 2.8.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 13 commits ahead by 13, behind by 1.
See the full diff |
Version 2.9.0 just got published. |
Version 2.10.0 just got published. |
Version 2.11.0 just got published. |
Version 2.12.0 just got published. |
Version 2.13.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 37 commits.
There are 37 commits in total. See the full diff |
Version 2.14.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Version 2.14.1 just got published. |
Version 2.16.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Version 2.16.1-launchpad just got published. |
Version 2.17.0 just got published. |
Version 2.18.0 just got published. |
Version 2.0.0 of graphql-tools just got published.
The version 2.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of graphql-tools.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 7 commits.
6b7794f2.0.0 (#407)a8344112.0 with schema stitching (#382)d21c841Remove unused autopublish featuref729751Add Node 8 to Travis CId05c630Update all dependencies to latest versions and fix testsdf82ac9Update vscode settingse73dc9bInstanceof check in resolveType bug (#393)See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴