Replies: 50 comments 95 replies
-
|
@PHLAK what is the repository you are referencing here? If releasees are made on the same day it is supposed to sort by SemVer, which might be falling apart here. It should also be sorting based on date of the tag / commit not the GitHub release. |
Beta Was this translation helpful? Give feedback.
-
|
Today this issue also affected the automatically generated release notes since it was using the incorrect release/tag ( |
Beta Was this translation helpful? Give feedback.
-
|
I also noticed this seemingly-random order on https://github.com/ruby/truffleruby-dev-builder/releases |
Beta Was this translation helpful? Give feedback.
-
|
We also encountered this bug in https://github.com/Shadowsocks-NET/QvStaticBuild/releases. This project uses tags in The wrong release order breaks our AUR package, since it uses a simple script to select the first (assuming the first is also the latest) release from the API, which is now one month behind the latest. |
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing my releases out of order with |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Not sure why |
Beta Was this translation helpful? Give feedback.
-
|
I got |
Beta Was this translation helpful? Give feedback.
-
|
FWIW, we're also seeing this behavior on https://github.com/StackExchange/StackExchange.Redis/releases - I can't really make sense of what's it's trying to do. I'd expect it to either respect the tag order (chronologically) or the version number - both are in the correct order and I created the releases (backfill) oldest to newest one day last week. Is there any way for us to get these in the correct order? For a while (I checked every release I added) the latest wasn't at the top which is very not-awesome. Any help would be appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
We have an issue as well, where the release |
Beta Was this translation helpful? Give feedback.
-
|
Also experiencing this. Tags are in the correct order but releases are in a very weird order. |
Beta Was this translation helpful? Give feedback.
-
|
same issue here |
Beta Was this translation helpful? Give feedback.
-
|
Hello folks, we've been experiencing a similar issue for some time in a private repo. We create a new release weekly and have an old one from December 2022 "stuck" at the top of the list as if it were the latest release. The actual latest release is also tagged correctly as such.
I also checked the
|
Beta Was this translation helpful? Give feedback.
-
|
I think the same issue has happened in the CSV Lint repository |
Beta Was this translation helpful? Give feedback.
-
|
Even tags are not always sorted correctly. See how v0.20.0 is out of order. But the releases make no sense. I don't really want to have to have When I use Before and after changing the I don't even have a My releases are listed in this order:
What I don't understand is if releases have an associated tag, why isn't that what gets used for sorting? My tags/release names are very simple compared to what others are using, but even those simple tags/release names are not sorting in any predictable order. Is this going to be "fixed"? Or at least made predictable? As users, we don't seem to have any reliable way of making sure releases are sorted in any expected way. |
Beta Was this translation helpful? Give feedback.
-
|
I have previously tried "Update release without making any changes" and that didn't help if I recall I also tried setting 'Latest' which does work if the last release is truly Latest. But not the case if Release was a PATCH release for an existing release. In this instance we will manually go and reset last release to 'Latest' after PATCH version has been released but that still leaves the PATCH release out of order (e.g. v5.0.5). See https://github.com/hazelcast/hazelcast/releases I have not tried suggestion made here https://github.com/orgs/community/discussions/8226#discussioncomment-7704448. This appears to work so will try this at some point As for "Releases on the same day can get out of order if the semver is not in order", still might be an issue unless GitHub have fixed this explicitly. As I recall, either the git commit or Release datetime is used to sort, so for a PATCH release this will still be an issue I believe |
Beta Was this translation helpful? Give feedback.
-
|
Unless someone gets their attention on social media they ain't fixing it. |
Beta Was this translation helpful? Give feedback.
-
|
Tags are properly ordered whereas Releases are incorrectly ordered (erratic). With some suggested solutions, have tried updating the previous tag of a few releases but in vain because when I open the updated release once again, the value of the previous tag reverts to auto once again instead of retaining the edited value. Seems like an issue in identifying the previous tag with the value of the auto set. Needs a fix at the earliest. |
Beta Was this translation helpful? Give feedback.
-
|
We just had this happen for one of our internal repositories, but when I edited an older release that was appearing at the top to have "[NOT LATEST]", it magically fixed itself, almost like it was a cached result of a bug that was previously fixed. So I re-edited the release to remove the NOT LATEST and everything is good now. The release that got stuck at the top was from August 9, 2023, and all further releases appeared below it until we edited the August 9 release. |
Beta Was this translation helpful? Give feedback.
-
|
response 2# |
Beta Was this translation helpful? Give feedback.
-
|
We've also hit this problem. I have tried editing older and the latest releases but nothing seems to work. The funny thing is we have 13 repos that all have the same release numbering scheme but only 1 repo is affected by this. Our repos only hold releases/binaries and a README, so the past several releases all are tagged based on the same commit. That could be contributing to why it's getting confused. But still odd that it's only happening on 1 of 13 repos. |
Beta Was this translation helpful? Give feedback.
-
|
This makes it incredibly painful to look through changelogs for projects that rely on Releases and don't have a separate CHANGELOG.md. The Releases search is also pretty bad so you can't even filter down to a specific version prefix |
Beta Was this translation helpful? Give feedback.
-
|
I've reproduced this bug in https://github.com/dskecse/gh_releases_order_issue/releases with semver (version string) tags, e.g. |
Beta Was this translation helpful? Give feedback.
-
|
When multiple releases occur on the same day, the earliest release remains at the top, even when a subsequent release is designated as the latest. You can have a look at a sample here. Kindly fix this issue at the earliest. |
Beta Was this translation helpful? Give feedback.
-
|
I have a mono repository that contains multiple projects that are each one versioned separated. All releases/tags have a prefix (ex.: The semver happens but only after the prefix. Is there a way to consider this in the release sorting? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
I also have this problem. Four years later nonetheless... |
Beta Was this translation helpful? Give feedback.
-
|
Can't believe you github cannot do such a simple thing well |
Beta Was this translation helpful? Give feedback.
-
|
I've got the same issue as of today with this repo https://github.com/openmobilityfoundation/curb-data-specification/releases Note the release sorted to the top now (tagged 1.1.0-rc marked as pre release) was created weeks before the release created today that should be at the top (tagged 1.1.0 and marked as latest release). |
Beta Was this translation helpful? Give feedback.
-
|
Same issue https://github.com/JanKrivanek/MSBuildStructuredLog/releases v2.3.175-beta.1 appearing before v2.3.176-beta.1 Any way to manually influence the order? |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here: https://github.com/Wooly-AI/woolyai-client-libraries/releases |
Beta Was this translation helpful? Give feedback.














Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Releases are displaying out of order and it seems to be a bit random. They're not sorted by date/time, commit or tag name.
Beta Was this translation helpful? Give feedback.
All reactions