You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are old tags with higher number than the latest releases => v1.0.20210914-ls99
This causes confusion in docker updaters like diun / whatsupdocker. You should bump the ls99 part to a higher number
Expected Behavior
No response
Steps To Reproduce
.
Environment
.
CPU architecture
x86-64
Docker creation
.
Container logs
.
The text was updated successfully, but these errors were encountered:
While we think on this, its worth mentioning the lsxxx number did indeed restart, but it did not stop at 99, it went to 126. While our logic has some inconsistencies here, the detection you posted also isnt flawless.
To provide more context, we use skopeo to retrieve the last pushed version for the branch tag and extract the ls version to decide on the new tag.
Every once in a while it fails and starts from 1. Normally that's not an issue as the versions get bumped and there is no overlap. But wireguard tools did not get a version update in 3 years, and it led to overlap of tags
Is there an existing issue for this?
Current Behavior
There are old tags with higher number than the latest releases => v1.0.20210914-ls99
This causes confusion in docker updaters like diun / whatsupdocker. You should bump the
ls99
part to a higher numberExpected Behavior
No response
Steps To Reproduce
.
Environment
CPU architecture
x86-64
Docker creation
.
Container logs
.
The text was updated successfully, but these errors were encountered: