From e18b79ef878795d8445fb7c85202a6f51f125948 Mon Sep 17 00:00:00 2001 From: Tony Breeds Date: Fri, 12 Apr 2019 10:14:18 +1000 Subject: [PATCH] Uncap jsonschema We have jsonschema capped at a fairly old version. Other than some specific releases, it looks like keeping it below 3.0 was added in I943fd68b9fab3bce1764305a5058df5339470757 without really any explanation why. In order to update to a 3.x release we need to: 1. Remove the cap from global-requirements.txt (see Depends-On), leaving upper-constraints.txt at a 2.x release 2. Remove the cap from all consumers (this change) 3. Release a new version of consumers that are published to pypi 4. Update upper-constraints.txt with those new releases 5. Update jsonschema in upper-constraints.txt to a 3.X release (See: https://review.openstack.org/649789) 6. Test consumers with the change from 5. 7. [Optional] fix issues in consumers that arise from 6. 8. Merge the change from 5. Change-Id: I8ba739b97cb9673b34acb041524a2041c1489466 Co-Authored-by: Sean McGinnis Depends-On: https://review.openstack.org/649669 --- requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.txt b/requirements.txt index 9a7d88708b83..32951a8fe0f3 100644 --- a/requirements.txt +++ b/requirements.txt @@ -25,7 +25,7 @@ paramiko>=2.0.0 # LGPLv2.1+ Babel!=2.4.0,>=2.3.4 # BSD enum34>=1.0.4;python_version=='2.7' or python_version=='2.6' or python_version=='3.3' # BSD iso8601>=0.1.11 # MIT -jsonschema<3.0.0,>=2.6.0 # MIT +jsonschema>=2.6.0 # MIT python-cinderclient>=3.3.0 # Apache-2.0 keystoneauth1>=3.9.0 # Apache-2.0 python-neutronclient>=6.7.0 # Apache-2.0