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
1179192144,PR_kwDOAMm_X8407zU4,6409,Add kwarg-only breaking change to whats-new,2448579,closed,0,,,0,2022-03-24T08:47:39Z,2022-03-26T08:44:45Z,2022-03-26T08:44:43Z,MEMBER,,0,pydata/xarray/pulls/6409,"Closes #6408
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/6409/reactions"", ""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull
1178949620,I_kwDOAMm_X85GRVf0,6408,backwards incompatible changes in reductions,2448579,closed,0,,,2,2022-03-24T04:11:00Z,2022-03-26T08:44:43Z,2022-03-26T08:44:43Z,MEMBER,,,,"### What is your issue?

I merged #5950 but forgot that it included some backward-incompatible changes (Sorry! this came up in https://github.com/pydata/xarray/pull/6403 thanks to @mathause for spotting.)

1. Arguments like `keep_attrs`, `axis` are now keyword-only.
2. Some reductions had the 3rd position arg as `keep_attrs` and in other cases it was `axis`.

These have been standardized now, and only `dim` is accepted without kwarg-name.

@pydata/xarray Should we add a deprecation cycle (https://github.com/pydata/xarray/issues/5531)? Point (2) above will make it a little messy.

At the very least we should add a deprecation notice before releasing.
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/6408/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue