diff options
| author | Tony Breeds <tony@bakeyournoodle.com> | 2019-04-04 13:59:59 +1100 |
|---|---|---|
| committer | Tony Breeds <tony@bakeyournoodle.com> | 2019-04-04 13:59:59 +1100 |
| commit | d16aed56a298dfbba9e24f53b4c3b702792ccc9d (patch) | |
| tree | 13c36ddde10062b40e7c3ce5050c9a3fe2b69381 /requirements.txt | |
| parent | fdb515e16fe3901b695b7a71627d37eb2f62d481 (diff) | |
| download | python-designateclient-d16aed56a298dfbba9e24f53b4c3b702792ccc9d.tar.gz | |
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: I229ab45375c1c5a06c283b1d0cde3c2d951e5dd8
Co-Authored-by: Sean McGinnis <sean.mcginnis@gmail.com>
Depends-On: https://review.openstack.org/649669
Diffstat (limited to 'requirements.txt')
| -rw-r--r-- | requirements.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/requirements.txt b/requirements.txt index fe51bcf..0d5a614 100644 --- a/requirements.txt +++ b/requirements.txt @@ -2,7 +2,7 @@ # of appearance. Changing the order has an impact on the overall integration # process, which may cause wedges in the gate later. cliff!=2.9.0,>=2.8.0 # Apache-2.0 -jsonschema<3.0.0,>=2.6.0 # MIT +jsonschema>=2.6.0 # MIT osc-lib>=1.8.0 # Apache-2.0 oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0 oslo.utils>=3.33.0 # Apache-2.0 |