diff options
| author | Tony Breeds <tony@bakeyournoodle.com> | 2019-04-04 13:59:37 +1100 |
|---|---|---|
| committer | Tony Breeds <tony@bakeyournoodle.com> | 2019-04-04 13:59:37 +1100 |
| commit | a42acbb60a1650ea9e246316b0247c9241133d46 (patch) | |
| tree | 8c312535d005df5a690211be6d712d9cced46ced /requirements.txt | |
| parent | 053bc369688793e866523fcf9362e8ad422ba568 (diff) | |
| download | glance_store-a42acbb60a1650ea9e246316b0247c9241133d46.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: Iaabde1c8e8a9d23952e499810715adac992f67cc
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 e02741c..65fdd87 100644 --- a/requirements.txt +++ b/requirements.txt @@ -11,7 +11,7 @@ enum34>=1.0.4;python_version=='2.7' or python_version=='2.6' or python_version== eventlet!=0.18.3,!=0.20.1,>=0.18.2 # MIT six>=1.10.0 # MIT -jsonschema<3.0.0,>=2.6.0 # MIT +jsonschema>=2.6.0 # MIT keystoneauth1>=3.4.0 # Apache-2.0 python-keystoneclient>=3.8.0 # Apache-2.0 requests>=2.14.2 # Apache-2.0 |