Observations from 2021.8.1 automatic release

[jrbourbeau]

A couple unexpected things happened with the latest automatic release procedure:

• GitHub actions didn't run when the pull request was initially opened (though when I pushed an empty commit, GHA ran as expected). I checked https://www.githubstatus.com/ and there were know reported issues with GitHub actions during this time. xref Update Dask version to 2021.8.1 #178
• Even though the automerge label was applied to the PR, it wasn't automatically merged after all CI checks passed. xref Update Dask version to 2021.8.1 #178
• Twice as many build CI jobs ran on Update Dask version to 2021.8.1 #178. I suspect this is because we're triggering on both pull_request and push events
  

  dask-docker/.github/workflows/build.yml

  Line 3 in e82ac06

  on: [pull_request, push]

• The PR which was automatically created updated the release: XXXX.XX.X field in build/docker-compose.yml but not .github/workflows/build.yml (xref Bump to 2021.8.1 in docker build workflow #179). EDIT: fixed by Update watch-conda-forge include regex #181
• Images for the new 2021.8.1 release aren't appearing on docker hub (https://hub.docker.com/r/daskdev/dask/tags?page=1&ordering=last_updated) (I think this is related to our autotagging action)

[jrbourbeau]

For reference, since our build workflow will push to docker hub on push events with a new tag

dask-docker/.github/workflows/build.yml

Line 78 in 3362618

push: ${{ github.repository == 'dask/dask-docker' && github.event_name == 'push' && startsWith(github.ref, 'refs/tags') }}

I ended up manually deleting the 2021.8.1 tag (which was generated from the autotag workflow) and pushing an empty commit to main with a new 2021.8.1 tag (3362618). This resulted in docker images for the new release being published

[jacobtomlinson]

Thanks for writing this up @jrbourbeau. I'll take a look at these.

[jakirkham]

Curious how many of these are still issues

[jrbourbeau]

IIUC all of the unchecked boxes in the original post are still valid

[jacobtomlinson]

I've fixed up a few things and checked a few boxes in the post above that I can confirm as resolved.

The last outstanding one is the auto merge, I'm not sure if this is fixed by the other changes I've made so let's wait until the next release and see what happens. cc @jrbourbeau @jsignell.

[jacobtomlinson]

ping @jrbourbeau @jsignell how did things go with the latest release?

I see some extra changes were pushed to the PR so I'm guessing the find and replace still isn't working quite right, and the automerge didn't work. Is there anything else?

[jrbourbeau]

Yeah, that's correct. I also noticed that the autotag workflow did assign a 2022.4.0 tag, but assigning that tag didn't result in us pushing Docker images to Docker Hub or ghcr.io. As of now the latest images available are for 2022.3.0. I should also note that deleted the 2022.4.0 tag which was automatically added and manually re-added the tag myself to see if that would help, but it did not