Lock Go version about sql_exporter HOT 1 CLOSED

Hey @alex1989hu, thanks for suggestions. Some feedback from my side:

go.mod references a minimum version of Go required by the module as per docs, so we increase it periodically. v1.16 is a valid version so far.

setup-go the way it's set in Github Actions allows me to stay up to date with a new released Go version whenever it's generally available, and to fail early if there is any issue.

In your case, I'd say there wasn't much of a problem - it wasn't a compile issue, but a part of the workflow to keep go fmt applied consistently. Apparently, go v1.19 introduced changes for go style. Moreover, those comments will go away anyway as there's another PR to refactor drivers initialization.

Since there's no automated release management for container image builds anymore (as Docker Inc. removed such an opportunity sometime ago), we know in advance what version of Go is the latest and available (via GHA) to be used during container image builds.

As sql_exporter hasn't reached v1.0, I consider this ok. We can come back to this topic later, though. :)

from sql_exporter.