With the latest upper constraints updating generated patch  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  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.  I89576353371aa87d181610eb6242cbe961487af6 
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
All official OpenStack software should go through the OpenStack Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
You can reach the Release Management team on the #openstack-release channel on OFTC IRC <https://www.oftc.net/>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.