The issue has been closed
<!-- Thanks for contributing! 🏓 -->
Releases can be created from tags, which can then be further classified as pre-release or the default of the latest release.
<img width="604" alt="Screen Shot 2019-07-15 at 6 47 35 PM" src="https://user-images.githubusercontent.com/1894657/61256118-1dff0880-a731-11e9-9aa6-8e98da1527ae.png">
The latest release widget displays a release marked as pre-release as the latest release.
<img width="332" alt="Screen Shot 2019-07-15 at 6 46 31 PM" src="https://user-images.githubusercontent.com/1894657/61256119-1dff0880-a731-11e9-9cff-11bc487f6fca.png">
The API supports the ability to differentiate between the two.
https://developer.github.com/v3/repos/releases/#list-releases-for-a-repository
posted by sindresorhus over 5 years ago 
The Tags endpoint doesn’t include this info and the Releases endpoint doesn’t include all tags (so it would only work if a repo uses releases)
This returns a list of releases, which does not include regular Git tags that have not been associated with a release. To get a list of Git tags, use the Repository Tags API.
The Tag object doesn’t include references to the related release either: https://developer.github.com/v4/object/tag/
The only way to do this seems to be making 2 queries and then check filter out any tags that are in prereleases.
More generically, I think we can just exclude tags that include - which seems to be used for prereleases
we can just exclude tags that include -
Quite a few repos have dates in their tag names (for example YYYY-MM-DD).
I think we already have a condition that excludes tags that aren’t “version-like”
We’ll never catch all the edge cases but, maybe:
- exclude specifically
x.y-b and x.y.z-b tags
in our existing v4 query, also check if we have information about a tag being a pre-release or “latest release” The first one is enough
posted by fregante about 5 years ago 
IssueHunt