Update Go version

[dveeden]

In go.mod we have the version set to 1.18

The Go release policy is "Each major Go release is supported until there are two newer major releases.". This means only 1.23 and 1.22 are in support.

https://go.dev/doc/devel/release#:~:text=Each%20major%20Go%20release%20is%20supported%20until%20there%20are%20two%20newer%20major%20releases.

Not sure how this would impact projects depending on go-mysql.

Not sure if there are any real benefits to bumping the version either.

If we bump the version, should we go to 1.21, 1.22? or 1.23?

diff --git a/go.mod b/go.mod
index 612dad7..d7e79cf 100644
--- a/go.mod
+++ b/go.mod
@@ -1,6 +1,6 @@
 module github.com/go-mysql-org/go-mysql
 
-go 1.18
+go 1.21
 
 require (
        github.com/BurntSushi/toml v1.3.2

@lance6716 @atercattus what do you think?

[serprex]

go 1.21 introduced log/slog, I could write a PR switching out logger. That would be a breaking change, unless some compatibility layer is kept to support both logging interfaces (which I currently do to wrap slog logger in https://github.com/PeerDB-io/peerdb/blob/main/flow/connectors/mysql/logger.go)

[dveeden]

My personal preference is to use the standard library where possible, and slog would match that. However I don't know what @atercattus and @lance6716 think of that.

[lance6716]

I also prefer the standard library. For compatibility problem, I think the developers won't be bothered much if the new logger can be configurated easily, or we provide a converter function, or we release a major version which means API break.

[serprex]

go.mod bumped to 1.22 by #993, this issue can be closed