Docker images are pushed on every commit to master, but contain the nightly release, not the code from the commit that triggered the build.
This leads to the confusing situation where there are Docker tags for each commit on master (e.g. lycheeverse/lychee:sha-102ecb4) which do not contain the changes in that commit. The only thing that (potentially) changes is the Dockerfile used to build the image.
Also the latest and master tags are identical, which seems redundant, and there is no way to track the latest stable release (#1981).
I would propose that the "floating" Docker tags should be
latest: the latest stable release
nightly: the latest nightly release
master: the latest commit on master
as well as immutable tags
X.Y.Z for stable releases
sha-01234abc for commits to master
(plus the -alpine counterparts).
Docker images are pushed on every commit to master, but contain the nightly release, not the code from the commit that triggered the build.
This leads to the confusing situation where there are Docker tags for each commit on master (e.g.
lycheeverse/lychee:sha-102ecb4) which do not contain the changes in that commit. The only thing that (potentially) changes is the Dockerfile used to build the image.Also the
latestandmastertags are identical, which seems redundant, and there is no way to track the latest stable release (#1981).I would propose that the "floating" Docker tags should be
latest: the latest stable releasenightly: the latest nightly releasemaster: the latest commit on masteras well as immutable tags
X.Y.Zfor stable releasessha-01234abcfor commits to master(plus the
-alpinecounterparts).