MNT:(deps): Bump xarray from 0.15.1 to 0.16.0 in /ci

[dependabot]

Bumps xarray from 0.15.1 to 0.16.0.

Release notes

Sourced from xarray's releases.

v0.16.0

This release adds xarray.cov & xarray.corr for covariance & correlation respectively; the idxmax & idxmin methods, the polyfit method & xarray.polyval for fitting polynomials, as well as a number of documentation improvements, other features, and bug fixes. Many thanks to all 44 contributors who contributed to this release.

Commits

• 5676926 Release v0.16.0
• c90d6dc Minor reorg of whatsnew for 0.16.0 (#4216)
• f3ca63a fix sphinx warnings (#4199)
• 64c1391 pin isort (#4206)
• 03c8562 get the colorbar label via public methods (#4201)
• 87f671e Bump minimum versions for 0.16 release (#4175)
• 834d4c4 Allow passing axis kwargs to plot (#4020)
• 329cefb Fix to_unstacked_dataset for single dimension variables. (#4094)
• 03d409e Improve the speed of from_dataframe with a MultiIndex (by 40x!) (#4184)
• e216720 More pint compatibility: silence UnitStrippedWarnings (#4163)
• 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)

[jthielen]

@dopplershift Now that Dependabot is in place, what should the workflow be for patches for version updates? I'd like to go ahead and fix this xarray 0.16 issue.

Ideas I had:

• Separate PR to master bumping version, fixing issue, and closing dependabot PR
• PR to the dependabot branch, which can then be merged, at which point the dependabot PR would be updated
• Directly commit to the dependabot branch, automatically updating the dependabot PR (Member/Collaborator only)

Also, as referenced in #1372 (comment), I think the broken tests are only on master, not 0.12.x, so I think this can be remilestoned as 1.0?

[dopplershift]

I milestoned for 0.12.2 to make sure I didn't forget to check it before I released--don't want to release without support for xarray 0.16.0.

In general, I'm ok with any of those workflows for incorporating version bumps. I'd say go with whatever you're most comfortable with. The important part is that we now have a bot checking for new versions and that's the only time things should change.

[jthielen]

I milestoned for 0.12.2 to make sure I didn't forget to check it before I released--don't want to release without support for xarray 0.16.0.

Sounds good!

In general, I'm ok with any of those workflows for incorporating version bumps. I'd say go with whatever you're most comfortable with. The important part is that we now have a bot checking for new versions and that's the only time things should change.

In that case, I think I'll go with the first (separate PR). Thanks!

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.