Remove fsspec version ceiling, set to >=2025.3.2#609
Merged
andrii-i merged 3 commits intojupyter-server:2.xfrom Mar 4, 2026
Merged
Remove fsspec version ceiling, set to >=2025.3.2#609andrii-i merged 3 commits intojupyter-server:2.xfrom
fsspec version ceiling, set to >=2025.3.2#609andrii-i merged 3 commits intojupyter-server:2.xfrom
Conversation
dlqqq
reviewed
Mar 4, 2026
Collaborator
dlqqq
left a comment
There was a problem hiding this comment.
Looks great, thanks! Just one minor comment
fsspec to >= 2026.2.0fsspec version ceiling, set to >=2025.3.2
dlqqq
approved these changes
Mar 4, 2026
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
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.
Problem
Downstream consumers cannot upgrade to newer versions of
fsspec(>= 2026.2.0) becausejupyter-schedulerpinsfsspec>=2023.6.0,<=2025.3.2,!=2025.3.1.Proposed solution
Remove the upper bound on
fsspecand set the minimum to>=2025.3.2.This would allow existing users to upgrade jupyter-scheduler without being forced to change their environment, while also unblocking users that need fsspec 2026.2.0.
Code changes
Changed
fsspec>=2025.3.2.Testing
On top of CI, verified manually that notebook job creation, execution, and output file download work correctly with
fsspec 2026.2.0.User-facing changes
None.
Backwards-incompatible changes
The minimum required
fsspecversion is now2025.3.2(previously2023.6.0). Environments with olderfsspecversions will need to upgrade.