Remove max limit on dependency versions #302
Merged
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.
Brief Slack discussion (link to thread) with @adammcmaster confirmed that there was no specific issue dictating max limits on dependency versions (added in #129). To limit dependency version conflicts, I propose we remove these limits until a point where a specific max limit is required for any of the dependencies. We have received multiple reports (e.g., from Spyfish Aotearoa and Gravity Spy teams) of max version on
requests
library causing issues and incompatibilities.Closes #301 as that sort of bump would no longer be required.