Skip to content
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

Merged
merged 3 commits into from
Apr 1, 2022
Merged

Release 2022.04.0 #202

merged 3 commits into from
Apr 1, 2022

Conversation

jsignell
Copy link
Member

@jsignell jsignell commented Apr 1, 2022

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@conda-forge-linter
Copy link

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 (recipe) and found it was in an excellent condition.

@jsignell
Copy link
Member Author

jsignell commented Apr 1, 2022

@conda-forge-admin, please rerender

@jakirkham jakirkham added the automerge Merge the PR when CI passes label Apr 1, 2022
@jakirkham
Copy link
Member

jakirkham commented Apr 1, 2022

Looks like dask-core is on CDN

$ 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

@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2022

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: passed

Thus the PR was passing and merged! Have a great day!

@github-actions github-actions bot removed the automerge Merge the PR when CI passes label Apr 1, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2022

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

Comment on lines 16 to +19
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
Copy link
Member

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

@jakirkham jakirkham added the automerge Merge the PR when CI passes label Apr 1, 2022
@github-actions github-actions bot merged commit 4f45fbd into conda-forge:main Apr 1, 2022
@jsignell jsignell deleted the 2022.04.0 branch June 24, 2022 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge the PR when CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants