In one of my image builds, I realized that for some reason, version 10.0.20250712.3 is actually newer than 10.0.20250712.5:
INFO New version: '10.0.20250712.3'
INFO Previous version: '10.0.20250712.5'
https://github.com/AlmaLinux/atomic-workstation/actions/runs/16387536260/job/46309207948#step:4:1782
I'm not sure how this happened, but it seems that the image that should have had the tag 10.0.20250712.3 originally was never created, and somehow the next time the CI ran it still skipped to 10.0.20250712.4. You can see this here and filtering for 10.0.20250712.
I think the logic for new versions should be "first available tag higher than previous version", rather than "first available tag higher than 10.0.20250712.0".
Also, the current suffix logic will break after .9 .
In one of my image builds, I realized that for some reason, version
10.0.20250712.3is actually newer than10.0.20250712.5:https://github.com/AlmaLinux/atomic-workstation/actions/runs/16387536260/job/46309207948#step:4:1782
I'm not sure how this happened, but it seems that the image that should have had the tag
10.0.20250712.3originally was never created, and somehow the next time the CI ran it still skipped to10.0.20250712.4. You can see this here and filtering for10.0.20250712.I think the logic for new versions should be "first available tag higher than previous version", rather than "first available tag higher than 10.0.20250712.0".
Also, the current suffix logic will break after
.9.