Skip to content

Update to dask==2026.1.1#142

Merged
rapids-bot[bot] merged 5 commits intorapidsai:release/26.02from
TomAugspurger:tom/dask-2026
Jan 20, 2026
Merged

Update to dask==2026.1.1#142
rapids-bot[bot] merged 5 commits intorapidsai:release/26.02from
TomAugspurger:tom/dask-2026

Conversation

@TomAugspurger
Copy link
Contributor

No description provided.

AyodeAwe and others added 3 commits January 15, 2026 11:48
This PR updates the repository to version 26.04.

This is part of the 26.02 release burndown process.
@TomAugspurger TomAugspurger requested a review from a team as a code owner January 16, 2026 21:43
@copy-pr-bot
Copy link

copy-pr-bot bot commented Jan 16, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@TomAugspurger TomAugspurger added non-breaking Introduces a non-breaking change improvement Improves an existing functionality labels Jan 16, 2026
@TomAugspurger TomAugspurger changed the base branch from main to release/26.02 January 16, 2026 22:43
@TomAugspurger TomAugspurger requested a review from a team as a code owner January 16, 2026 22:43
Copy link
Member

@jameslamb jameslamb left a comment

Choose a reason for hiding this comment

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

Thanks for this!

There are a couple 26.04 changes here. Now that this PR has been retargeted to release/26.02, this branch should rebased onto that one.

git fetch upstream release/26.02
git rebase release/26.02
git push origin tom/dask-2026 --force

@TomAugspurger
Copy link
Contributor Author

Thanks. We should be back to just the dask version changes.

Copy link
Member

@rjzamora rjzamora left a comment

Choose a reason for hiding this comment

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

Thanks for taking care of this @TomAugspurger

Copy link
Member

@jameslamb jameslamb 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, thank you!

@jameslamb

This comment was marked as resolved.

@copy-pr-bot

This comment was marked as resolved.

@jameslamb
Copy link
Member

/ok to test cbceb21

@TomAugspurger
Copy link
Contributor Author

/merge

@rapids-bot rapids-bot bot merged commit bedbfa6 into rapidsai:release/26.02 Jan 20, 2026
11 checks passed
@jakirkham
Copy link
Member

Thanks all for working on this! 🙏

Unfortunately this missed the Conda recipe, which needs the same updates

run:
- dask ==2025.12.0
- dask-core ==2025.12.0
- distributed ==2025.12.0

@jakirkham
Copy link
Member

Submitted a fix with PR: #147

jameslamb pushed a commit that referenced this pull request Jan 29, 2026
Dask was updated to 2026.1.1 in PR:
#142

However this missed updating the Conda recipe

This PR updates the Conda recipes as well
rapids-bot bot pushed a commit that referenced this pull request Jan 29, 2026
## Summary

- Adds a pre-commit hook that validates dask, dask-core, and distributed versions are consistent across `dependencies.yaml`, `pyproject.toml`, and `conda/recipes/rapids-dask-dependency/recipe.yaml`

This addresses the issue seen in #142 and #147 where the conda recipe was not updated when the dask version was changed in `dependencies.yaml`.

The hook:
- Uses only Python standard library (no external dependencies)
- Only runs when relevant files are modified
- Provides clear error messages showing which files have mismatched versions

Authors:
  - Bradley Dice (https://github.com/bdice)
  - Peter Andreas Entschev (https://github.com/pentschev)

Approvers:
  - https://github.com/jakirkham
  - Peter Andreas Entschev (https://github.com/pentschev)

URL: #148
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Improves an existing functionality non-breaking Introduces a non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants