chore(deps): downgrade jsonschema dependency to 4.17 #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the problem/requirement? (What/Why)
deadline-cloud
is locked to jsonschema-4.17 as it is the last version to support python 3.7.deadline-cloud-for-nuke
has a dependency on this repo as well asdeadline-cloud
, causing conflicting dependencies.What was the solution? (How)
Downgrade the jsonschema dependency to 4.17 to align with
deadline-cloud
What is the impact of this change?
This repo is also locked to jsonschema-4.17 until we can determine a way to mix dependencies used by the adaptor (which can run python 3.9+) vs the child process being run (such as Nuke 13 which is using python 3.7)
How was this change tested?
Was this change documented?
No
Is this a breaking change?
Yes, dependency version is changing.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.