Decide whether to release post-EOL 1.19.13 if upstream does
dagood opened this issue · comments
I spotted this issue that implies there's going to be a 1.19.13 release (or some other minor 1.19 version) even though 1.21 and 1.20 are the current supported major versions:
I don't understand what's being fixed:
include corrected handling of modules and workspaces that declare to need Go 1.22, as mentioned at https://go.dev/doc/toolchain.
We need to decide whether to follow up on this type of release or not, and whether to revive the Docker image build too.
Ah, was able to find the commit on the 1.19 branch directly. There are actually a handful (so far):
- golang/go@2f498f2 <- The one being referred to earlier, making 1.19 refuse to build code that declares it requires 1.22.
- golang/go@c08a5fa
net/http: permit requests with invalid Host headers - golang/go@caca5f1
crypto/tls: add GODEBUG to control max RSA key size
Team sync notes: we think going along with upstream makes sense here. People in Microsoft are likely using 1.19 and would benefit (CBL-Mariner ships 1.19, for example), and it shouldn't be too bad to set up the Dockerfiles again--it's just a semi-manual process.