Skip to content

Remove fsspec version ceiling, set to >=2025.3.2#609

Merged
andrii-i merged 3 commits intojupyter-server:2.xfrom
andrii-i:fsspec
Mar 4, 2026
Merged

Remove fsspec version ceiling, set to >=2025.3.2#609
andrii-i merged 3 commits intojupyter-server:2.xfrom
andrii-i:fsspec

Conversation

@andrii-i
Copy link
Collaborator

@andrii-i andrii-i commented Mar 4, 2026

Problem

Downstream consumers cannot upgrade to newer versions of fsspec (>= 2026.2.0) because jupyter-scheduler pins fsspec>=2023.6.0,<=2025.3.2,!=2025.3.1.

Proposed solution

Remove the upper bound on fsspec and 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 fsspec version is now 2025.3.2 (previously 2023.6.0). Environments with older fsspec versions will need to upgrade.

@andrii-i andrii-i added dependencies Pull requests that update a dependency file enhancement New feature or request labels Mar 4, 2026
Copy link
Collaborator

@dlqqq dlqqq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks! Just one minor comment

@andrii-i andrii-i changed the title bump fsspec to >= 2026.2.0 Remove fsspec version ceiling, set to >=2025.3.2 Mar 4, 2026
@andrii-i andrii-i merged commit c6fe3a2 into jupyter-server:2.x Mar 4, 2026
9 checks passed
@andrii-i andrii-i deleted the fsspec branch March 4, 2026 00:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants