chore(api): Constrain jsonschema dependency to current major version #5006
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.
Overview
This PR tweaks #5005.
jsonschema uses semantic versioning. So, we can specify that we don't want their next breaking change.
jsonschema has already had one major version bump since we've started using it, apparently. That could have included breaking changes that affect us; we're lucky it didn't.
Review requests
Should we also change this in the Pipfile?
opentrons/api/Pipfile
Line 32 in 01fccdf
Further reading