Release 2023.2.1

[charlesbluca]

Closes #214

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/dask-feedstock/actions/runs/4265968041.

[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 unconstrained 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]

Good catch! Should we update the jinja optional requirement in dask as well?

[charlesbluca]

Yeah good catch, bumping that makes sense to me

[charlesbluca]

Opened up dask/dask#9999 to handle this

[jakirkham]

@conda-forge-admin, please restart CI

[github-actions]

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!