In the example where "latest release" works, those Releases were all created via either the GitHub web interface or the API. When the release is created, it also creates a tag. So every release has a tag, but not every tag has a full release.
The one that doesn't have the "latest release" feature is because everything you see there are tags that were pushed to the repository without having a release formally created. We still show them on the Releases page because a tag is also a milestone in the repository history, but since no title, description, or assets were added to the tag, it doesn't have the same functionality as a full Release does. That's why the "latest release" button isn't showing there.
Hope that clears up what you're seeing a little bit!
Hello! I'm struggling with the same issue. I'm working for a company that has a semi-automated system that creates release tags. Now we have started monitoring project for all releases in our organization and we want to use the Release event in the API for that. But since our "release tag" is not considered a full release, it does not create "Release" event. We can of course use "New tag event", but we'd much prefer to be able to create full Release with title, description, or assets from the command line. Is there any way to that?
You can employ lastversion - as long as your tags include version information, it will report the latest release version correctly.
I ran into this today and found a straightforward resolution and thought I would share for the next person.
We created a git tag for our release using the git command line. This showed up in GitHub, even under the Releases view. It was in the "Other Tags" section and an older version was highlighted as "Latest Release".
Resolution: I clicked into the tag, clicked the 'Edit tag' button, added a value for the 'Release title' field, then clicked the 'Publish release' button. This converted the tag to a release and moved the 'Latest Release' badge to the correct release.