chore: Remove upper bound from fsspec requirement #4461
Closed
+452
−602
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.
In #3922 the fsspec requirement was loosened to allow what was then more recent releases. Since then Feast has further reduced the number dependencies with upper bounds. Instead of re-testing each month (when fsspec usually releases) it would now be idiomatic only specify a minimum bound.
The new minimum bound was chosen to match what was last locked in ci, since that is what was tested and we can be less sure older versions also work.