Looks like the publish step in the GH Actions pipeline is skipped, see workflow. I believe this is because that step is only triggered when a new tag is created.
Could @softprops (or the maintainers, if any) push a new tag for the current master branch? Or, maybe merging #90 will work too. We could all benefit from having a central location to pull the image from, instead of publishing to our own Docker Hub repos, so that GitHub Actions can hold the image cache for everyone a little longer.
Looks like the
publishstep in the GH Actions pipeline is skipped, see workflow. I believe this is because that step is only triggered when a new tag is created.Could @softprops (or the maintainers, if any) push a new tag for the current master branch? Or, maybe merging #90 will work too. We could all benefit from having a central location to pull the image from, instead of publishing to our own Docker Hub repos, so that GitHub Actions can hold the image cache for everyone a little longer.