Update dependencies for 2024.5.0

[conda-forge-admin]

• Update dependencies to match latest release
• Add pip check in tests to confirm this
• Enable Grayskull for version updates to automate dependency handling

Also submitted a couple minor tweaks upstream: dask/dask-image#374

Fixes #25

[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.

[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.

[jakirkham]

Marking as draft until we confirm what we would like to do upstream: dask/dask-image#374

[GenevieveBuckley]

I've removed slicerator and scikit-image from the dependencies, as per the discussion in dask/dask-image#374

[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!

[GenevieveBuckley]

Ok, the conda-forge docker build does not pass because dask-image v2024.05.0 says it requires scikit-image and slicerator (those dependencies we think should be removed, and were removed in dask/dask-image#374) .

I assume the best thing to do now is to tag v2024.5.1 on dask-image, and see if that fixes things over here.

[jakirkham]

Sounds good

As pip check will fail due to those dependencies not being included, have commented and raised issue ( #26 ) to remind us to reenable it next release

[jakirkham]

We can also do a release, but I'd be ok punting on that for now and just trying pip check later

Edit: Expect CI will pass

[GenevieveBuckley]

We can also do a release, but I'd be ok punting on that for now and just trying pip check later

Honestly it's probably easier to do that now. I don't think I'm going to remember to check the dask-image-feedstock issues at the right time just before the next release.

All we have to do is add a v2024.5.1 tag to dask-image, right?

[jakirkham]

Yep that would work

It would be a good test of the Grayskull dependency update bits we just added here 😉

[GenevieveBuckley]

Ok, I'll do that now 😄

[jakirkham]

Thanks Genevieve! 🙏

Am wondering if that will also fix the doc versioning issue we saw

[GenevieveBuckley]

Here we go: https://github.com/dask/dask-image/releases/tag/v2024.5.1

Am wondering if that will also fix the doc versioning issue we saw

I don't think so, but that docs hypothesis is just my best guess for now.