I have 3 releases of this repository in GitHub:
( tags and maybe other required related info could be seen by following the url)
The latest release is the v1.2:
However, the first version is marked as "Latest Release":
Then if I use this url below, I get the earliest version of my releases:
I wonder if its possibly to set the release that I want it to be the latest release, via the GitHub web, with no complicated things.
When I said "with no complicated things" is because I read this post below on which they comment to use the git console, but really I don't want to depend on git console to be clonning my repository and messing with tags and etc just to set the green indicator of the damn Latest Release.
That makes me think whether really GitHub doesn't provide any "Set this as the Latest Release" friendly button on their web?, why they don't?, I hope just I'm missing something in their web because this is very annonying for their online users.
All three of your tags — 1.0, 1.1, and 1.2 — are linked to this commit. So in this case, all three releases are identical.
If you add or merge a new commit on the master
branch that's tagged with 1.3, but don't update the last 3 tags, then this will become your latest release.
If you tag the commit correctly, git tag --contains
should only output the latest tag. However:
$ git tag --contains
1.0
1.1
1.2
And as you can see, each tag points to the same commit:
$ git rev-list -1 1.0
6fbce42a8c59b0a06f679a369d19b7a1282023d0
$ git rev-list -1 1.1
6fbce42a8c59b0a06f679a369d19b7a1282023d0
$ git rev-list -1 1.2
6fbce42a8c59b0a06f679a369d19b7a1282023d0
TLDR: Make a new commit, then tag it, and don't update the other tags.