83cd4f9d8c
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: I66ad793a52c657564ece35019430557a45edd3bf Co-Authored-by: Sean McGinnis <sean.mcginnis@gmail.com> Co-Authored-by: Tony Breeds <tony@bakeyournoodle.com>
22 lines
707 B
Plaintext
22 lines
707 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
hacking>=1.0,<1.2 # Apache-2.0
|
|
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
extras>=1.0.0 # MIT
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
jsonschema>=2.6.0 # MIT
|
|
mock>=2.0.0 # BSD
|
|
prometheus-client>=0.4.2 # Apache-2.0
|
|
python-subunit>=1.0.0 # Apache-2.0/BSD
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
requests-mock>=1.2.0 # Apache-2.0
|
|
statsd>=3.3.0
|
|
stestr>=1.0.0 # Apache-2.0
|
|
testrepository>=0.0.18 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
doc8>=0.8.0 # Apache-2.0
|
|
Pygments>=2.2.0 # BSD license
|