Instead of Docker Hub Autobuild (#16), use a GitHub Actions workflow that is triggered by a git tag and publishes images to the GitHub Container Registry. Making image changes more explicit, though further work will be required to fully prevent accidental breaking changes like #17.
In this new workflow, each image gets version tags sourced from the git tag, starting at version 1.0.0. E.g. one can pull prebuild/alpine:1, prebuild/alpine:1.0, prebuild/alpine:1.0.0 or (same as before) prebuild/alpine:latest. This will allow us to make breaking changes like #15 and #10.
Instead of Docker Hub Autobuild (#16), use a GitHub Actions workflow that is triggered by a git tag and publishes images to the GitHub Container Registry. Making image changes more explicit, though further work will be required to fully prevent accidental breaking changes like #17.
In this new workflow, each image gets version tags sourced from the git tag, starting at version 1.0.0. E.g. one can pull
prebuild/alpine:1
,prebuild/alpine:1.0
,prebuild/alpine:1.0.0
or (same as before)prebuild/alpine:latest
. This will allow us to make breaking changes like #15 and #10.