Mattermost-server: Github: Release tagged as "latest"

[jangrewe]

Summary

I'm not sure what causes this, but for some reason the "latest" tag of the Github releases (https://github.com/mattermost/mattermost-server/releases) keeps being changed and for a couple of days now doesn't point to the actual latest release.

This might seem trivial to you, but i have automation in place that alerts me on new releases for various Github projects, and i keep getting notified that Mattermost (and only you guys) have a new release, which is actually older than then actual latest release.

#### Steps to reproduce
-

Expected behavior

The actually latest release is tagged as "latest"

Observed behavior (that appears unintentional)

The "latest" tag keeps jumping between the latest and some previous release.

Possible fixes

Make sure that the latest release is tagged as "latest".

[amyblais]

@metanerd / @jaydeland Is this expected / unexpected?

[jaydeland]

I don't believe so, we will have to investigate

[amyblais]

@jaydeland Would you like me to open a ticket for this, and if yes, which team?

[jaydeland]

@amyblais - I was wrong, this is expected according to GitHub: https://developer.github.com/v3/repos/releases/#get-the-latest-release
Since we cherry-pick fixes into past releases.

[jangrewe]

But if you cherry-pick into past releases, then, as the name implies, those are still past releases and not the latest release.
It is also my understanding that by modifying an existing release, that release should get a patch level version increment, as it is not the same version you released under that version number.

[metanerd]

@jangrewe what you say is correct. Still the created_at date of the commit for the past release is newer than the latest release's created_at date. So this is technically correct, but not intended this way.

Since there will be a revision coming up for our release process, this shouldn't happen anymore afterwards. Please kindly bear with us till then.

[jangrewe]

@metanerd Hey Eli, nice to see you at your new job ;-)

Thanks, i'll silence my alerts for this repo and will check manually for now.