id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type
1603957501,I_kwDOAMm_X85fmnL9,7573,Add optional min versions to conda-forge recipe (`run_constrained`),2448579,closed,0,,,4,2023-02-28T23:12:15Z,2023-08-21T16:12:34Z,2023-08-21T16:12:21Z,MEMBER,,,,"### Is your feature request related to a problem?

I opened this PR to add minimum versions for our optional dependencies: https://github.com/conda-forge/xarray-feedstock/pull/84/files to prevent issues like #7467 

I think we'd need a policy to choose which ones to list. Here's the current list:
```
run_constrained:
    - bottleneck >=1.3
    - cartopy >=0.20
    - cftime >=1.5
    - dask-core >=2022.1
    - distributed >=2022.1
    - flox >=0.5
    - h5netcdf >=0.13
    - h5py >=3.6
    - hdf5 >=1.12
    - iris >=3.1
    - matplotlib-base >=3.5
    - nc-time-axis >=1.4
    - netcdf4 >=1.5.7
    - numba >=0.55
    - pint >=0.18
    - scipy >=1.7
    - seaborn >=0.11
    - sparse >=0.13
    - toolz >=0.11
    - zarr >=2.10
```


Some examples to think about:
1. `iris` seems like a bad one to force. It seems like people might use Iris and Xarray independently and Xarray shouldn't force a minimum version.
2. For backends, I arbitrarily kept `netcdf4`, `h5netcdf` and `zarr`. 
3. It seems like we should keep array types: so `dask`, `sparse`, `pint`.

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_

### Additional context

_No response_","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/7573/reactions"", ""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue