Bump xarray from 0.17.0 to 2023.4.2

[dependabot]

Bumps xarray from 0.17.0 to 2023.4.2.

Release notes

Sourced from xarray's releases.

v2023.04.2

This is a bugfix release to fix another bug with binning (#7766)

What's Changed

• Docstrings examples for string methods by @​remigathoni in pydata/xarray#7669
• Fix groupby_bins when labels are specified by @​dcherian in pydata/xarray#7769

Full Changelog: pydata/xarray@v2023.04.1...v2023.04.2

v2023.04.1

This is a patch release to fix a bug with groupby_bins

What's Changed

• Fix binning by unsorted array by @​dcherian in pydata/xarray#7762

Full Changelog: pydata/xarray@v2023.04.0...v2023.04.1

v2023.04.0

What's Changed

This release includes support for pandas v2, allows refreshing of backend engines in a session, and removes deprecated backends for rasterio and cfgrib.

Thanks to our 19 contributors: Chinemere, Tom Coleman, Deepak Cherian, Harshitha, Illviljan, Jessica Scheick, Joe Hamman, Justus Magin, Kai Mühlbauer, Kwonil-Kim, Mary Gathoni, Michael Niklas, Pierre, Scott Henderson, Shreyal Gupta, Spencer Clark, mccloskey, nishtha981, veenstrajelmer

New Contributors

• @​harshitha1201 made their first contribution in pydata/xarray#7638
• @​veenstrajelmer made their first contribution in pydata/xarray#7553
• @​Chinemere made their first contribution in pydata/xarray#7677
• @​nishtha981 made their first contribution in pydata/xarray#7623
• @​Kwonil-Kim made their first contribution in pydata/xarray#7746
• @​mccloskey made their first contribution in pydata/xarray#7747

Full Changelog: pydata/xarray@v2023.03.0...v2023.04.0

v2023.03.0

This release brings many bug fixes, and some new features. The maximum pandas version is pinned to <2 until we can support the new pandas datetime types. Thanks to our 19 contributors: Abel Aoun, Alex Goodman, Deepak Cherian, Illviljan, Jody Klymak, Joe Hamman, Justus Magin, Mary Gathoni, Mathias Hauser, Mattia Almansi, Mick, Oriol Abril-Pla, Patrick Hoefler, Paul Ockenfuß, Pierre, Shreyal Gupta, Spencer Clark, Tom Nicholas, Tom Vo

New Contributors

• @​tomvothecoder made their first contribution in pydata/xarray#7579
• @​agoodm made their first contribution in pydata/xarray#7494
• @​Ravenin7 made their first contribution in pydata/xarray#7615
• @​Ockenfuss made their first contribution in pydata/xarray#7598
• @​remigathoni made their first contribution in pydata/xarray#7625

... (truncated)

Changelog

Sourced from xarray's changelog.

How to issue an xarray release in 16 easy steps

Time required: about an hour.

These instructions assume that upstream refers to the main repository:

$ git remote -v
{...}
upstream        https://github.com/pydata/xarray (fetch)
upstream        https://github.com/pydata/xarray (push)

1. Ensure your main branch is synced to upstream:

   git switch main
   git pull upstream main

2. Add a list of contributors with:

   git log "$(git tag --sort=v:refname | tail -1).." --format=%aN | sort -u | perl -pe 's/\n/$1, /'

   This will return the number of contributors:

   git log "$(git tag --sort=v:refname | tail -1).." --format=%aN | sort -u | wc -l

3. Write a release summary: ~50 words describing the high level features. This will be used in the release emails, tweets, GitHub release notes, etc.
4. Look over whats-new.rst and the docs. Make sure "What's New" is complete (check the date!) and add the release summary at the top. Things to watch out for:
   • Important new features should be highlighted towards the top.
   • Function/method references should include links to the API docs.
   • Sometimes notes get added in the wrong section of whats-new, typically due to a bad merge. Check for these before a release by using git diff, e.g., git diff v{YYYY.MM.X-1} whats-new.rst where {YYYY.MM.X-1} is the previous release.
5. Open a PR with the release summary and whatsnew changes; in particular the release headline should get feedback from the team on what's important to include.
6. After merging, again ensure your main branch is synced to upstream:

   git pull upstream main

7. If you have any doubts, run the full test suite one final time!

   pytest

8. Check that the ReadTheDocs build is passing on the main branch.

... (truncated)

Commits

• 91f14c9 [skip-ci] Release 2023.04.2 (#7774)
• a4c54a3 Fix groupby_bins when labels are specified (#7769)
• c75ac8b Docstrings examples for string methods (#7669)
• ae10df4 Add dev whats-new
• 5cd3db5 Add benchmark against latest release on main. (#7753)
• 4f5675c Update whats-new.rst
• 99f03c2 Fix binning by unsorted array (#7762)
• 68bae08 Bump codecov/codecov-action from 3.1.1 to 3.1.2 (#7760)
• 6b7515c Fix typing errors using mypy 1.2 (#7752)
• b889208 [skip-ci] dev whats-new
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)