html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/6222#issuecomment-1029124001,https://api.github.com/repos/pydata/xarray/issues/6222,1029124001,IC_kwDOAMm_X849Vy-h,13301940,2022-02-03T15:45:17Z,2022-02-03T15:45:17Z,MEMBER,Closed by #6224,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1119738354
https://github.com/pydata/xarray/issues/6222#issuecomment-1026050538,https://api.github.com/repos/pydata/xarray/issues/6222,1026050538,IC_kwDOAMm_X849KEnq,13301940,2022-01-31T17:55:52Z,2022-01-31T17:57:26Z,MEMBER,"> after twine check where we pip install and then try to import xarray.
> Alternatively we could have another test config in our regular CI to build + import.

it's my understanding that we're doing this here:

https://github.com/pydata/xarray/blob/b09de8195a9e22dd35d1b7ed608ea15dad0806ef/.github/workflows/pypi-release.yaml#L74-L80

However, it appears that the three seconds in `sleep 3` aren't enough to warrant getting the latest metadata from `test.pypi.org`... For instance, the latest build ended up pulling `v0.20.2` instead of the `v0.21.0` ([relevant run](https://github.com/pydata/xarray/runs/4987064187?check_suite_focus=true))","{""total_count"": 1, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 1, ""rocket"": 0, ""eyes"": 0}",,1119738354