Latest Release is not marked as Latest

[IndraVisatiyaF5]

I have a github workflow which create an artifact and upload it to the release, then workflow triggers Azure DevOps release pipeline which is configured to download latest release artifact from GitHub.

When creating a latest release from GitHub, it does not label it as Latest release. That's why, Azure DevOps release pipeline is unable to select default latest release for deployment and it picks up snapshot version.

Please see attached.

[Ziflin]

I just ran into the same issue as well. I have a "latest" release that is updated per-commit (it zips up some of the repository as an asset). However it is not being updated with the "(Latest)" UI label on GitHub now that I also have a automated release created using a version tag (i.e. v1.0.0).

So on GitHub's Releases page, I'm seeing something similar as @IndraVisatiyaF5 :

• 41 Minutes ago - v1.0.0 (Latest) <- GitHub label
• 5 Minutes ago - latest

This also causes the "Releases" UI on the right side of the "Code" page to incorrectly show the "v1.0.0 (Latest)" release, despite there now being 2 commits (and action executions for the "latest" tag).

Perhaps there's an issue with trying to update a previous Release vs. creating a new one not tagging it as latest on GitHub?

Also, I think this requires testing with prerelease: false for both build types. If you're using prerelease: true for one, then that icon/label is shown instead on GitHub I believe. I'm trying to have one release always be valid for the "latest" commits so that I can have a static/permanent link to a zip file that it creates.

[dciborow]

@IndraVisatiyaF5 have you set prerelease = false for your snapshot releases?

[IndraVisatiyaF5]

Yes, it's set to prerelease = false for snapshot already.