id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type
806436724,MDU6SXNzdWU4MDY0MzY3MjQ=,4894,release 0.17.0,2448579,closed,0,,,14,2021-02-11T14:24:18Z,2021-02-26T20:16:16Z,2021-02-26T20:16:16Z,MEMBER,,,,"Quoting @spencerkclark email:

> Somewhat related to this issue, would others on the core team be open to making a new xarray release soon?  In addition to the license change, this cftime update unintentionally introduced a change* that broke our encoding logic for cftime dates in a subtle way.  I recently fixed this in pydata/xarray#4871, but until a new xarray release is made, this issue makes it dangerous to use the latest non-GPL-licensed version of cftime.

These three seem like high-priority fixes. Thoughts?

- [x] #4884
- [x] #4893
- [ ] #4879 ?
- [x] #4911
- [x] #4179 / #4907

Nice to have

- [ ] #4740","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/4894/reactions"", ""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue
552994673,MDExOlB1bGxSZXF1ZXN0MzY1NDAxMTMw,3713,bump min deps for 0.15,2448579,closed,0,,,14,2020-01-21T16:39:07Z,2020-01-24T21:47:00Z,2020-01-24T21:46:55Z,MEMBER,,0,pydata/xarray/pulls/3713,"<!-- Feel free to remove check-list items aren't relevant to your change -->

 - [x] Closes #1679
 - [x] Passes `black . && mypy . && flake8`
 - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/3713/reactions"", ""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull