Unpin, to see what happens

[aulemahal]

Pull Request Checklist:

• This PR addresses an already opened issue (for bug fixes / features)
  • This PR fixes #xyz
• (If applicable) Documentation has been added / updated (for bug fixes / features).
• (If applicable) Tests have been added.
• This PR does not seem to break the templates.
• CHANGELOG.rst has been updated (with summary of main changes).
  • Link to issue (:issue:number) and pull request (:pull:number) has been added.

What kind of change does this PR introduce?

• Unpin xarray, dask and zarr to see what happens.
• Change "<" pin of xESMF to "=!" as the bug is resolved in xESMF's master.

Does this PR introduce a breaking change?

Other information:

[Zeitsperre]

@aulemahal Except for the rechunk error, it looks like everything is working well. Would you want to re-pin rechunker here or wait for the next rechunker release with your bug fixes?

[aulemahal]

The rechunker bug is from two incompatibilities with dask 2024.11 and xarray 2024.10. There are no rechunker versions that work with those two! But, we could fix the issue with xarray here directly. The one with dask is only fixable within rechunker and a PR is opened and ready to review there.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[aulemahal]

So, this :

• does not unpin zarr < 3, which is incompatible as seen in the tests of ed7c891
• unpins xarray as I was able to fix the rechunker issue in our rechunk method
• does not unpin dask as the rechunker issue is unavoidable
• allows python 3.13

[Zeitsperre]

Looks good!