Release 2023.2.1

[charlesbluca]

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-webservices]

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.

[charlesbluca]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/distributed-feedstock/actions/runs/4265949970.

[charlesbluca]

Seems like this was a change made with dask/distributed#7285 that we missed in the 2023.1.0 release? cc @jrbourbeau @jakirkham just making sure that leaving this at >=0.10.0 wasn't intentional in the past few releases.

Shouldn't be difficult to submit a repodata patch to update this for the impacted versions

[jakirkham]

Should we bump the toolz version in requirements.txt as well?

[charlesbluca]

Not immediately obvious to me? It doesn't look like there's a package for toolz 0.10.1 available on either PyPI or conda-forge, and it looks like Distributed's mindeps testing is currently running without issues pinned to 0.10.0 (though not sure if this is case where installing cytoolz in the same environment would override this)

[jakirkham]

Gotcha. Yeah guess 0.11.0 is the next version where they are aligned. So sounds like we leave toolz alone

[charlesbluca]

@conda-forge-admin, please restart CI