Bump xarray from 0.20.2 to 2022.3.0

[dependabot]

Bumps xarray from 0.20.2 to 2022.3.0.

Release notes

Sourced from xarray's releases.

v2022.03.0

This release brings a number of small improvements, as well as a move to calendar versioning.

Many thanks to the 16 contributors to the v2022.02.0 release!

Aaron Spring, Alan D. Snow, Anderson Banihirwe, crusaderky, Illviljan, Joe Hamman, Jonas Gliß, Lukas Pilz, Martin Bergemann, Mathias Hauser, Maximilian Roos, Romain Caneill, Stan West, Stijn Van Hoey, Tobias Kölling, and Tom Nicholas.

v0.21.1

This is a bugfix release to specify packaging as a dependency.

v0.21.0

Many thanks to the 20 contributors to the v0.21.0 release!

Abel Aoun, Anderson Banihirwe, Ant Gib, Chris Roat, Cindy Chiao, Deepak Cherian, Dominik Stańczak, Fabian Hofmann, Illviljan, Jody Klymak, Joseph K Aicher, Mark Harfouche, Mathias Hauser, Matthew Roeschke, Maximilian Roos, Michael Delgado, Pascal Bourgault, Pierre, Ray Bell, Romain Caneill, Tim Heap, Tom Nicholas, Zeb Nicholls, joseph nowak, keewis.

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

• 9b4d0b2 v2022.03.0 release notes (#6319)
• cdab326 fix typos (using codespell) (#6316)
• 2ab9f36 Add General issue template (#6314)
• f9037c4 Disable CI runs on forks (#6315)
• 0f91f05 Enable running sphinx-build on Windows (#6237)
• 555a70e Fix class attributes versus init parameters (#6312)
• 613a8fd On Windows, enable successful test of opening a dataset containing a cftime i...
• 4292bde from_dict: doctest (#6302)
• 17acbb0 Drop duplicates over multiple dims, and add Dataset.drop_duplicates (#6307)
• de965f3 Amended docs on how to add a new backend (#6292)
• 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)