From 71177fe9776d8cf958ac3054885f891f49c1ef4d Mon Sep 17 00:00:00 2001
From: Lucas Costa <lucas@lucascosta.com>
Date: Thu, 26 Oct 2017 16:21:19 -0200
Subject: [PATCH] Prevent requirement breaking changes

I have a project still in 1.2.0 thats has been broken in my last release since it used `'graphql-core>=1.0.1'` in the `install_requires`. Since `graphql-core` has released version 2.0 with breaking changes and there was no instruction to maintain version 1, it was included as a dependency. This prevents this situation for the future.
---
 setup.py | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/setup.py b/setup.py
index 6ac46d18..52d7de0c 100644
--- a/setup.py
+++ b/setup.py
@@ -86,10 +86,10 @@ setup(
     packages=find_packages(exclude=['tests', 'tests.*']),
 
     install_requires=[
-        'six>=1.10.0',
-        'graphql-core>=2.0',
-        'graphql-relay>=0.4.5',
-        'promise>=2.1',
+        'six>=1.10.0,<2',
+        'graphql-core>=2.0,<3',
+        'graphql-relay>=0.4.5,<1',
+        'promise>=2.1,<3',
     ],
     tests_require=tests_require,
     extras_require={