Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 27, 2020

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

Dependabot compatibility score

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)

@dependabot dependabot bot added the Type: Maintenance Updates and clean ups (but not wrong) label Jul 27, 2020
@dopplershift dopplershift added this to the 0.12.2 milestone Jul 27, 2020
@dependabot dependabot bot force-pushed the dependabot-pip-ci-xarray-0.16.0 branch from 54a0e66 to 00da3c9 Compare July 27, 2020 10:55
@jthielen
Copy link
Collaborator

jthielen commented Jul 27, 2020

@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
Copy link
Member

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
Copy link
Collaborator

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 @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 28, 2020

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.

@dependabot dependabot bot deleted the dependabot-pip-ci-xarray-0.16.0 branch July 28, 2020 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Maintenance Updates and clean ups (but not wrong)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants