The new 4.x release of jsonschema has borked our schemas for reasons I
do not yet fully understand (though I have an idea - see inline). Unbork
things now and fix our CI, while we work on a longer-term fix.
Conflicts:
requirements-test.txt
Changes:
requirements-text.txt
NOTE(stephenfin): The conflict is because we're using a slightly older
version of openapi-core here which we don't want to update. We also need
to modify the file futher to pin openapi-schema-validator to keep pip
happy since openapi-schema-validator 0.2.0 requires jsonschema > 4.0.
Signed-off-by: Stephen Finucane <stephen@that.guru>
python-dateutil~=2.8.0
tblib~=1.7.0
openapi-core~=0.13.4
+# FIXME(stephenfin): We have to pin this to prevent a recurrence of [1]. It
+# seems openapi-core needs to gain support for OpenAPI 3.1 before we can fix
+# this properly
+#
+# [1] https://github.com/OAI/OpenAPI-Specification/issues/1368
+jsonschema<4.0
+openapi-schema-validator<0.2.0