I've set of organizational private repos with quite long lists of releases. Releases have names N-Y.M.D-X
where N
is sequential number, Y.M.D
is date of the release and X
could be commit hashcode or combination of branch name and hashcode.
The problem is the release 9-2024.10.13-607d6fd
(from two weeks ago) is still marked as "latest" even if there are other recent releases (the actual last one - 17-2024.10.15-rename-models-1533982
- is from last week).
It looks like GitHub changed the way of latest
evaluation from different day timestamps or consider the version number (9-2024
> 17-2024
lexicographically) prior the release timestamp.
Is there a way to fix that? Is it a problem of GitHub or the format of the first part of version number N-Y
?
BTW: If list releases by tag then they are ordered right way.
We use ncipollo/release-action@v1
GitHub action to make releases. I don't why it was working well before, but anyway I found I can pass makeLatest: true
for the release and it will be marked as latest
. It resolved the problem.