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
1654022522,I_kwDOAMm_X85ilmF6,7716,bad conda solve with pandas 2,2448579,closed,0,,,18,2023-04-04T14:37:58Z,2023-04-16T17:57:27Z,2023-04-13T17:56:34Z,MEMBER,,,,"### What happened?

Pandas 2 is out. 

We have a `pandas<2` pin for our latest release, but `mamba` is now returning `xarray=2023.1.0` and `pandas=2.0` which is making [cf-xarray](https://github.com/xarray-contrib/cf-xarray/actions/runs/4603068761/jobs/8132721316?pr=431) and [flox](https://github.com/xarray-contrib/flox/actions/runs/4603066011/jobs/8132714566?pr=229) tests fail.

It looks like any project that tests `resample` without pinning pandas will fail.

I opened the issue here for visibility. It seems we might need a repodata patch to disallow `pandas<2`?

cc @ocefpaf 

### What did you expect to happen?

_No response_

### Minimal Complete Verifiable Example

_No response_

### MVCE confirmation

- [ ] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
- [ ] Complete example — the example is self-contained, including all data and the text of any traceback.
- [ ] Verifiable example — the example copy & pastes into an IPython prompt or [Binder notebook](https://mybinder.org/v2/gh/pydata/xarray/main?urlpath=lab/tree/doc/examples/blank_template.ipynb), returning the result.
- [ ] New issue — a search of GitHub Issues suggests this is not a duplicate.

### Relevant log output

_No response_

### Anything else we need to know?

_No response_

### Environment

<details>



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