golang: v↑ go1.14 (1.14.12 -> 1.14.15)
Going Go1.14.12 -> Go1.14.15 brings in fixes to compiler, runtime, standard library and build security. https://golang.org/doc/devel/release.html#go1.14.minor Tested on helloworld SR (by adjusting it to use go1.14 instead of go1.15) Go1.14.15 is the last Go1.14.x release, because, after Go1.16 was released, Go1.14 becomes end-of-life and will not receive any updates nor fixes for security bugs. /cc @jerome (for theia which is on go1.14) /cc @luke (for caddy which is on go1.14) /cc @tomo, @alain.takoudjou (for galene which is still on EOL go1.13) /cc @alain.takoudjou (for replication-manager which is still on EOL go1.13) /cc @alain.takoudjou (for restic which is still on EOL go1.13) /cc @jerome, @alain.takoudjou (for gitlab which is still on EOL go1.12) /cc @jerome (for grafana which is still on EOL go1.12)
-
Owner
/cc @jerome, @luke, @tomo, @alain.takoudjou
-
Owner
Thanks @kirr I already started updating grafana first, it's easy, because we don't use it.
We should update gitlab. It will requires more time because it's really used and it's important for us. It will be very hard for me to find enough time for this in the next weeks.
Theia uses go mainly because it also uses caddy. It also uses gopls but I think it does not really work there.
For repman, I see they use "tip" in their CI ( https://github.com/signal18/replication-manager/blob/2.1/.travis.yml#L3 ) which means latest. I believe we should try to use 1.16 and see if test pass.
For galene I don't see anything about a required go version, so we should also try 1.16 - but we don't seem to have tests for this at this point, so someone would have to verify manually.
-
Owner
I changed grafana to use golang 1.6 and update many other components from this software release in !921 (merged) . It looks working locally.
I also started to change replication-manager / restic to use the default golang version (ie. stop using an old version), I'm building this locally.
-
Owner