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

Prepare for v0.6.3 #176

Merged
merged 2 commits into from
Jun 29, 2022
Merged

Prepare for v0.6.3 #176

merged 2 commits into from
Jun 29, 2022

Conversation

aulemahal
Copy link
Collaborator

Simply put a date in CHANGES.rst

I also bumped the versions of github actions, to close all the automatic PRs.

@aulemahal aulemahal requested a review from raphaeldussin June 29, 2022 20:02
@aulemahal aulemahal requested a review from huard June 29, 2022 20:08
@aulemahal
Copy link
Collaborator Author

Haha, lucky us, recent commits to xarray seem to have broken cf-xarray and thus our own upstream builds.

@raphaeldussin
Copy link
Contributor

I approve for release as well. Is there an issue reported in cf-xarray?
Hopefully this will be resolved soon and fix the upstream

@aulemahal
Copy link
Collaborator Author

Without being sure what caused the bug in xarray, I was able to fix it in cf-xarray quite simply and opened a PR there : xarray-contrib/cf-xarray#343.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants