From aeeb6d31114720789907822160bf5c1e43316f34 Mon Sep 17 00:00:00 2001 From: Ivan Kerin Date: Tue, 19 Jun 2018 17:24:40 +0300 Subject: [PATCH] Bump graphql version to 14.0.0 So graphql are transitioning to real semver finally. This should fix #3562 I've set the devDependency to graphql@14.0.0-rc.2 to be able to be able to run the tests on the new version and make sure everything's fine. But I'm not sure if you think its ok to merge with that release candidate. Also I think the semver in peerDependencies is more verbose than it should be: ```js "peerDependencies": { "graphql": "^0.11.0 || ^14.0.0" } ``` This should cover all of the graphql versions from 0.11 and up, since ["^" includes minor and patch versions](https://bytearcher.com/articles/semver-explained-why-theres-a-caret-in-my-package-json/) --- packages/apollo-client/package.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/apollo-client/package.json b/packages/apollo-client/package.json index 552786b9a41..97b75ed0e1d 100644 --- a/packages/apollo-client/package.json +++ b/packages/apollo-client/package.json @@ -55,7 +55,7 @@ "zen-observable": "^0.8.0" }, "peerDependencies": { - "graphql": "^0.11.0 || ^0.12.0 || ^0.13.0" + "graphql": "^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0" }, "devDependencies": { "@types/benchmark": "1.0.31", @@ -71,7 +71,7 @@ "danger": "1.1.0", "flow-bin": "0.73.0", "github": "12.1.0", - "graphql": "0.13.2", + "graphql": "14.0.0-rc.2", "graphql-tag": "2.9.2", "isomorphic-fetch": "2.2.1", "jest": "23.0.0",