releases/requirements.txt
Előd Illés e83bb1f69a Uncap jsonschema
With the latest upper constraints updating generated patch [1] the
openstack-tox-docs job started to fail, due to conflict:

ERROR: Cannot install jsonschema<4.0.0 and >=3.2.0 because these
package versions have conflicting dependencies.

The conflict is caused by:
    The user requested jsonschema<4.0.0 and >=3.2.0
    The user requested (constraint) jsonschema===4.7.2

This is because we have jsonschema<4.0.0 in our requirements.txt.
By uncapping the constraint the docs job is passing.

Date validation needed to be updated as well, because a deprecated
usage of validator extending method was used in the code, which was
removed [2] from jsonschema with the 4.0.0 release. This patch replaces
that with adding a TYPE_CHECKER instead.

With the new jsonschema constraint openstack-tox-py36 job does not pass
anymore, but py36 is dropped from zed anyway. That job is pulled in by
an old job template, which needs to be replaced to the new zed job
templates, too.

[1] I89576353371aa87d181610eb6242cbe961487af6
[2] d9f6384060

Closes-Bug: #1982757
Change-Id: Ida6310dd822e587ce9c424a228fdff5192ba0476
2022-07-26 12:24:11 +02:00

36 lines
1.0 KiB
Plaintext

######################################################################
# #
# ** IMPORTANT ** #
# #
# THIS FILE IS ONLY USED BY TOX IN THE CHECK AND GATE JOBS. YOU MUST #
# UPDATE bindep.txt TO INCLUDE ADDITIONAL PACKAGES NEEDED IN THE #
# POST-MERGE # JOBS SUCH AS "tag-releases". #
# #
######################################################################
build>=0.7.0
pbr>=1.6
keyring>=7.3
requests>=2.5.2
PyYAML>=3.1.0
yamlordereddictloader
prompt_toolkit>=2.0.7
tqdm
mwclient==0.8.1
jsonschema>=3.2.0
twine>=1.13.0
wheel>=0.34.2
ruamel.yaml>=0.15
tenacity>=6.1.0
# For release notes generation.
Jinja2>=2.6 # BSD License (3 clause)
parawrap
reno>=3.2.0
sphinx>=1.6.2 # BSD
appdirs
packaging>=16.5
openstack-governance>=0.11.0 # Apache 2.0