From 876ef274f3543b286c5e13d06005878ab3d7d809 Mon Sep 17 00:00:00 2001 From: Tony Breeds Date: Thu, 4 Apr 2019 14:01:34 +1100 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: Ic782c3085fb85634d2ae2b7d5538ae2948d2f9b8 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 813e1cc84..c304a4be1 100644 --- a/requirements.txt +++ b/requirements.txt @@ -29,5 +29,5 @@ keystoneauth1>=3.4.0 # Apache-2.0 tenacity>=4.4.0 # Apache-2.0 futures>=3.0.0;python_version=='2.7' or python_version=='2.6' # BSD metalsmith>=0.9.0 # Apache-2.0 -jsonschema<3.0.0,>=2.6.0 # MIT +jsonschema>=2.6.0 # MIT requests>=2.18.0,!=2.20.0 # Apache-2.0