CI: require minimum Dask version to avoid missing dask.dataframe.api - #348
Draft
rithiksachdeva wants to merge 1 commit into
Draft
CI: require minimum Dask version to avoid missing dask.dataframe.api#348rithiksachdeva wants to merge 1 commit into
rithiksachdeva wants to merge 1 commit into
Conversation
rithiksachdeva
force-pushed
the
fix/min-dask-dataframe-api-floor
branch
from
April 9, 2026 19:45
024000f to
4549d4c
Compare
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
1 participant
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.
A closed CI run from PR #347 exposed an edge-case environment solve where an older Dask version was installed due to an unbounded dependency in a conda env YAML.
In that environment, test collection failed with:
This occurs when the solver selects a Dask version that predates the introduction of
dask.dataframe.api, which is required by the current codebase.This change updates env YAML files that previously listed
daskwithout a version constraint and adds a minimum compatible version floor.The minimum version is chosen as the higher of:
dask.dataframe.apipyproject.toml:dask[dataframe]>=2025.1.0This ensures CI environments cannot resolve to incompatible Dask versions while preserving flexibility in the "latest" environments across platforms.
This issue was platform/solver-specific (observed in macOS CI) and did not consistently reproduce across all environments.