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: I1d57fc4255ff18f6cf5a27dbd39f7fa8b1323958 Co-Authored-by: Sean McGinnis <sean.mcginnis@gmail.com> Depends-On: https://review.openstack.org/649669
This commit is contained in:
parent
977717e756
commit
d23255300a
|
@ -9,7 +9,7 @@ oslo.utils>=3.33.0 # Apache-2.0
|
|||
oslo.log>=3.36.0 # Apache-2.0
|
||||
httplib2>=0.9.1 # MIT
|
||||
iso8601>=0.1.11 # MIT
|
||||
jsonschema<3.0.0,>=2.6.0 # MIT
|
||||
jsonschema>=2.6.0 # MIT
|
||||
requests>=2.14.2 # Apache-2.0
|
||||
python-keystoneclient>=3.8.0 # Apache-2.0
|
||||
PyYAML>=3.12 # MIT
|
||||
|
|
Loading…
Reference in New Issue