-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2022.04.0 #202
Release 2022.04.0 #202
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2022.04.01.12.21.46
Looks like $ conda search 'conda-forge::dask-core=2022.4'
Loading channels: done
# Name Version Build Channel
dask-core 2022.4.0 pyhd8ed1ab_0 conda-forge Restarting CI |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
entry_points: | ||
- dask-scheduler = distributed.cli.dask_scheduler:go | ||
- dask-ssh = distributed.cli.dask_ssh:go | ||
- dask-worker = distributed.cli.dask_worker:go | ||
- dask-scheduler = distributed.cli.dask_scheduler:main | ||
- dask-ssh = distributed.cli.dask_ssh:main | ||
- dask-worker = distributed.cli.dask_worker:main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As the entry_points
changed upstream in response to the click
8.1.0
release ( dask/distributed#6018 ), needed to make similar changes here
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)