proposal: affected/package: Cut a latest 1.## release with every new minor release

[ctm8788]

Currently 1.21 was just released as 1.21.0 .

I'm unable to download the 1.21 release via jenkins unless I specify 1.21.0

Once we move to a new minor release, we should be able to specify that and not have to wait until a patch version (1.21.1) to be able to specify 1.21
Works:
curl https://dl.google.com/go/go1.21.0.linux-amd64.tar.gz --output go1.21.0.linux-amd64.tar.gz
Doesn't Work:
curl https://dl.google.com/go/go1.21.linux-amd64.tar.gz --output go1.21.linux-amd64.tar.gz

[seankhliao]

This goes against our policy of providing stable / explicit versioning, both for the go distribution and dependencies in general.
You can parse the latest version out of the API endpoint https://go.dev/dl/?mode=json

[ctm8788]

Why can I download 1.20 without issue then?
curl https://dl.google.com/go/go1.20.linux-amd64.tar.gz --output go1.20.linux-amd64.tar.gz

[seankhliao]

https://go.dev/doc/go1.21#introduction

Go 1.21 introduces a small change to the numbering of releases. In the past, we used Go 1.N to refer to both the overall Go language version and release family as well as the first release in that family. Starting in Go 1.21, the first release is now Go 1.N.0.

[ctm8788]

I see, I feel like this could possibly break teams build processes and cause more overhead.