Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
x/website: Go latest release version info oh home page #33212
What version of Go are you using (
Thanks for the request.
This is essentially a dup of #33083 (show current Go version next to download button on homepage). Andybons is working on this, so I think we can close this issue in favour of the older one. Feel free to subscribe to that thread for updates.
Sorry for the confusion here. OP had opened #33145 which I closed citing the same reason. And I asked him to open a new issue for this.
As far as I understand, #33083 is just about showing the existing string which was shown at the footer to be shown next to the download page. But that string just shows the version with which x/website is being built.
OP wants the latest released Go version to be displayed on the home page. I understand both are eventually equivalent, but not exactly same. If that is what @andybons meant in #33083, then we can close this.
So just to be clear, I will reopen this and leave it to Andy for a final call.
Apologies for the to-and-fro.
Wait, I don't get it. If we end up showing something on the DOWNLOAD button, it'll be the latest released version, right? Which is what the OP is asking here. So #33083 will solve the issues this OP has.
I don't think the version near the download button will show the version the website was built with (it wouldn't make much sense for that information to be on the download button).
Also the OP in that old issues wrote:
it seems he's talking about the latest released version, I don't think he cares about the version the website was build for. So my understanding is that 1) OP here and OP in #33083 are asking exactly for the same thing 2) andybons work will fix #33083 (and this one) and satisfy both OPs
@ALTree Yeah, I guess you are right. I just wanted to clarify that the initial assumption of OP in #33083 was wrong. It's not just a matter of showing the exact same string in a different location now. We will be showing something completely different.
I guess we can close this since the end result of #33083 is the right one in any case.