At the moment, a new Docker image is pushed when a release Git tag is pushed. For example:
In both cases, there was a Docker image tag for the SHA corresponding to the commit of the Git tag, but no Docker image tag for the release. So:
- For
v0.20.1, there was --tag lycheeverse/lychee:sha-0a96dc2 (for 0a96dc2) but no --tag lycheeverse/lychee:v0.20.1 or --tag lycheeverse/lychee:0.20.1.
- For
v0.20.0, there was --tag lycheeverse/lychee:sha-e510602 (for e510602) but no --tag lycheeverse/lychee:v0.20.0 or --tag lycheeverse/lychee:0.20.0.
The Docker image tagging seems to be controlled by using the docker/metadata-action GitHub Action: https://github.com/docker/metadata-action. So some configuration change might be required to have a Docker image tagged with the release version number in addition to the SHA of the Git tag.
At the moment, a new Docker image is pushed when a release Git tag is pushed. For example:
v0.20.1(Debian): https://github.com/lycheeverse/lychee/actions/runs/17205362504/job/48804656733#step:9:218v0.20.0(Debian): https://github.com/lycheeverse/lychee/actions/runs/17148270680/job/48652300555#step:9:218In both cases, there was a Docker image tag for the SHA corresponding to the commit of the Git tag, but no Docker image tag for the release. So:
v0.20.1, there was--tag lycheeverse/lychee:sha-0a96dc2(for 0a96dc2) but no--tag lycheeverse/lychee:v0.20.1or--tag lycheeverse/lychee:0.20.1.v0.20.0, there was--tag lycheeverse/lychee:sha-e510602(for e510602) but no--tag lycheeverse/lychee:v0.20.0or--tag lycheeverse/lychee:0.20.0.The Docker image tagging seems to be controlled by using the
docker/metadata-actionGitHub Action: https://github.com/docker/metadata-action. So some configuration change might be required to have a Docker image tagged with the release version number in addition to the SHA of the Git tag.