Update to Go 1.14.12

[tao12345666333]

Signed-off-by: Jintao Zhang zhangjintao9020@gmail.com

[Jacalz]

Any chance of getting this merged or/and updated to 1.14.1?
Would be wonderful to get some faster defer statements going :)

[tao12345666333]

ping @thaJeztah PTAL, thanks!

[thaJeztah]

I'd like to hold off for a bit; we're not yet updating our toolchain to Go 1.14, because there's some regressions / incompatibilities with Go 1.14 related tot the preemptive changes made in that release.

[Jacalz]

I would say that it’s time to get this landed now. With 1.15 out of the door, 1.13.x won’t receive updates any more which isn’t ideal from a security standpoint.

[tao12345666333]

rebased.

[Jacalz]

Sorry, but could we please get this merged soon? It is getting very necessary to get 1.14.10 landed due to the big timezone issue, golang/go/issues/42138 among with 1.13.x not getting any security fixes. This has sat open for almost nine months.

[tao12345666333]

Sorry, but could we please get this merged soon? It is getting very necessary to get 1.14.10 landed due to the big timezone issue, golang/go/issues/42138 among with 1.13.x not getting any security fixes. This has sat open for almost nine months.

ping @thaJeztah
Thanks!

[Jacalz]

An update to 1.14.10 would be useful as it contains two security fixes.

[carleeto]

Hi, we're at v1.14.12, which is the latest 1.14 version as of today. I would suggest merging now, since all downstream projects that depend on the golang-cross image will gain the ability to automatically support vendored dependencies in Go modules, which is a change that was introduced in Go 1.14

[jlk]

Not sure how this is being used by Docker - if this is merged, dockercore/golang-cross:1.13.15 would still be on docker hub for use, but those of us who wanted newer could have that as well, no?