CI failure due to dependency conflict

[fjetter]

All our CI jobs with python>3.10 are failing due to a dependency resolution conflict

The conflict is caused by:
    The user requested fsspec 2024.3.2.dev5+g2dd9355 (from git+https://github.com/fsspec/filesystem_spec)
    dask 2024.4.1+4.gb2ec1e1a depends on fsspec>=2021.09.0
    s3fs 2024.3.1+2.g7ccc0a5 depends on fsspec==2024.3.1

cc @martindurant are you aware of anything that caused this hard pinning between s3fs and fsspec?

e.g. https://github.com/dask/distributed/actions/runs/8619396892/job/23704420478?pr=8610

[martindurant]

Yes, s3fs (and gcsfs) are hard pinned to exactly the same version as fsspec, and have been for a long time. They are always released within hours of each other.

The latest release is 2024.3.1. I am thinking that the introduction of hatch in fsspec/filesystem_spec#1553 has caused the dev version to be called "2024.3.2.XXX" instead of "2024.3.1.XXX" as versioneer used to do. I am not sure how to change this convention.

[fjetter]

OK, I don't want our entire CI to be blocked by this and opened #8615 to temporarily just run CI against stable versions until this is figured out

[martindurant]

fsspec/filesystem_spec#1569 should fix this, if you care to try

[phofl]

#8618 tries this

[martindurant]

Please try again with main/master whenever you think the caches might have cleared.

[phofl]

did that on my revert pr