Closed duckinator closed 11 months ago
In this case, I went to https://cirrus-ci.com/github/duckinator/bork/v5.0.0, found the relevant build, and re-ran the Release on Docker Hub
task.
However, Cirrus seems extremely confused by this: https://cirrus-ci.com/task/6565860963778560
So perhaps it'd make more sense to create new builds?
For xonsh, I just rebuild nightly.
This should've been a hint that Bork's dependencies weren't well-defined.
Pip is now an explicit dependency, and should've been one since zipapp support was added. If we ever encounter bugs that are fixed by requiring a newer pip version, we can start restricting the version of pip we depend on.
It may make sense to re-build the Docker Hub image when Pip is released.
There's a RSS feed for Pip releases: https://pypi.org/rss/project/pip/releases.xml It also looks like the Python Docker image is re-released whenever Pip is: https://hub.docker.com/layers/python/library/python/3.8-slim/images/sha256-282fc7428f74cf3317d78224349b9215f266fc9cb4197cce58dad775cb565ed3
I'm not sure if I want to automatically rebuild+push the Docker Hub image, but it'd be nice to at least get an alert somehow that would let me manually initiate the process.