Conversation
|
@conda-forge-admin, please rerender |
|
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 ( |
|
will fix the failing test in galaxyproject/tools-iuc#7455 |
|
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/conda-forge-webservices/actions/runs/19960068054. Examine the logs at this URL for more detail. |
| - datashader | ||
| - fsspec | ||
| - geopandas >=0.14 | ||
| - multiscale-spatial-image >=2.0.3 |
There was a problem hiding this comment.
| - multiscale-spatial-image 2.0.3 |
Looking at the release notes for 0.6.1, it looks to me like one of the main purposes was to pin multiscale-spatial-image to 2.0.3
https://github.com/scverse/spatialdata/releases/tag/v0.6.1
scverse/spatialdata@v0.6.0...v0.6.1
Is this no longer needed? The Issue about compatibility with 2.1.0 is still open: scverse/spatialdata#1020
There was a problem hiding this comment.
You are correct @jdblischak, it should be 2.0.3 and not >= 2.0.3
| - spatialdata | ||
| commands: | ||
| - pip list | ||
| - pip check |
There was a problem hiding this comment.
pip check only passed because the feedstock PR multiscale-spatial-image 2.1.0 is failing for conda-forge/multiscale-spatial-image-feedstock#15. If it gets merged, then multiscale-spatial-image 2.1.0 will be co-installed with spatialdata
|
Why was the existing PR for 0.6.1 ignored? I had already updated the dependencies. All you had to do was click merge |
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)