Skip to content

spatialdata v0.8.0#36

Merged
LucaMarconato merged 4 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:0.8.0_h649c37
Jul 7, 2026
Merged

spatialdata v0.8.0#36
LucaMarconato merged 4 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:0.8.0_h649c37

Conversation

@regro-cf-autotick-bot

Copy link
Copy Markdown
Contributor

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

  • Dependencies have been updated if changed: see upstream
  • Tests have passed
  • Updated license if changed and license_file is packaged

Information about this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
  3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
  4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
  5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name Upstream Version Current Version
click 8.4.2 Anaconda-Server Badge
pytorch-cpu 1783021838 Anaconda-Server Badge

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: disabled to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by grayskull shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by grayskull but not in the meta.yaml:

  • python {{ python_min }}.*
  • distributed >=2026.3.0
  • ome-zarr >=0.16.0
  • multiscale-spatial-image ==2.0.3
  • python >={{ python_min }}
  • dask-core >=2026.3.0

Packages found in the meta.yaml but not found by grayskull:

  • python 3.11
  • ome-zarr >=0.14.0
  • multiscale-spatial-image 2.0.3
  • pytorch
  • distributed <2026.1.2
  • python >=3.11
  • dask >=2025.12.0,<2026.1.2

This PR was created by the conda-forge-bot. The conda-forge-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/conda-forge/conda-forge-bot/actions/runs/28630717174 - please use this URL for debugging.

@conda-forge-admin

Copy link
Copy Markdown
Contributor

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/meta.yaml) and found it was in an excellent condition.

@jdblischak jdblischak left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread recipe/meta.yaml
{% set version = "0.7.3" %}
{% set python_min = "3.11" %}
{% set version = "0.8.0" %}
{% set python_min = "3.12" %}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread recipe/meta.yaml Outdated
- annsel >=0.1.2
- click
- dask >=2025.12.0,<2026.1.2
- dask >=2026.3.0

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upstream uses dask in pyproject.toml but grayskull prefers dask-core. This caused the initial conda solver error (since grayskull applied the updated pin to dask-core but left the existing incompatible pin on dask).

Could/should this recipe use dask-core over dask? I'm not familiar enough with dask to answer that, so for consistency I continued to require dask. spatialdata maintainers, please feel free to assess and update as desired.

https://github.com/conda-forge/dask-core-feedstock
https://github.com/conda-forge/dask-feedstock

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for flagging this. For dask vs dask-core see here dask/distributed#962 (comment). AFAIU dask should be including both dask-core (equivalent of PyPI's dask) and distributed. Since we depend explicitly on distributed (btw we will drop the dependency after we merge and release scverse/spatialdata#1106), it seems like we should be using dask-core here.

@LucaMarconato
LucaMarconato merged commit efa2ba0 into conda-forge:main Jul 7, 2026
2 checks passed
@regro-cf-autotick-bot
regro-cf-autotick-bot deleted the 0.8.0_h649c37 branch July 7, 2026 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants