Upper bound dependencies, add dependabot integration #170
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
|
We could also upper bound tensorflow at |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation is the same as in SeldonIO/alibi#349 .
The only dependency I'm uncertain of is
dask. First, not sure what the lower bound should be (I set it from what I had in my environment), second, they switched to calver (dask/community#100) citing in part the ability to have breaking changes in releases. Now, this doesn't mean we should have an upper bound for every version as most likely there will be no breaking changes, but do we have an arbitrary upper bound (e.g. year 2022 as proposed) or just not have an upper bound fordask?Finally, I cleaned up some entries in
setup.pywhich are not relevant as we don't run tests usingpython setup.py testanymore (same behaviour asalibi).