Restart numbering of -ls123 release tag for image?

[mikespub]

Nothing serious, but is there a particular reason why release tags would restart from -ls1 instead of increasing -ls307 etc. every week?

I just noticed that for https://github.com/linuxserver/docker-cops/tags we went from 4.5.2-ls307 to 4.5.2-ls1 and then increased onwards again, but I couldn't find any logic behind it (no app version change, no base image change, ...)

Just wondering...

[Roxedus]

Ratelimits/service interruptions. The previous number is gathered from the GitHub api

[mikespub]

For future reference, this is about the lsio_build_tag part mentioned in https://www.linuxserver.io/blog/docker-tags-so-many-tags-so-little-time#2-build-tag-static

[aptalca]

It triggered my OCD enough for me to look into a potential solution a while back, but unfortunately I couldn't come up with one that didn't introduce other potential issues like build failures.

It doesn't happen too often so as long as upstream pushes out new versions every once in a while, we can avoid the risk of overwriting an older build.

I just accepted the risk.

[mikespub]

Cheers - with 307 runs over 7+ years for this image it's looking pretty good anyway ;-)