Python 3.13 support not present for spatialdata >= 0.3.0 from conda

[shashkat]

Minimal working example

$ conda create -n temp python=3.13
$ conda activate temp
$ conda install conda-forge::spatialdata==0.3.0

Output

Channels:
- conda-forge
- bioconda
- r
- defaults
Platform: osx-arm64
Collecting package metadata (repodata.json): done
Solving environment: failed

LibMambaUnsatisfiableError: Encountered problems while solving:
- package spatialdata-0.3.0-pyhd8ed1ab_0 requires python >=3.10,<3.13, but none of the providers can be installed

Could not solve for environment specs
The following packages are incompatible
├─ pin on python 3.13.* =* * is installable and it requires
│  └─ python =3.13 *, which can be installed;
└─ spatialdata ==0.3.0 * is not installable because it requires
└─ python >=3.10,<3.13 *, which conflicts with any installable versions previously reported.

Pins seem to be involved in the conflict. Currently pinned specs:
- python=3.13

Describe the bug

The latest spatialdata-feedstock at conda-forge still seems to have the python<3.13 constraint (https://github.com/conda-forge/spatialdata-feedstock/blob/51e4845ff4698ecdf75bc882f899beb1058e75f5/recipe/meta.yaml#L23), even though the discussion at #964 states that spatialdata should support it now. Just curious if this is intentional or not. A side-effect of this is that installing latest squidpy (v1.7.0) in python3.13 environment using conda is difficult because squidpy1.7.0 requires spatialdata>=0.6.0, which requires python<3.13.

Additional context

This is the link to the commit in the spatialdata-feedstock that added the constraint of python<3.13: conda-forge/spatialdata-feedstock@1cbe783.

Thanks a lot!