Upgrade to Go 1.19

[thanethomson]

Following from #173, at what point should we consider upgrading the codebase and our tooling to use Go 1.19?

And in general, what are our criteria for updating to support a new version of Go? On the Rust side of development at Informal, we always update to the latest stable version of Rust the moment it's released.

PRs addressing this

• Upgrade to Go 1.19 on main #206
• Upgrade to Go 1.19 on v0.37.x #208
• Upgrade to Go 1.19 on 0.34.x #360

[sergio-mena]

My view is that we probably want to be aligned with the SDK when changing the (recommended) version of Go

[thanethomson]

I see they use 1.18 in their v0.46 release line at present: https://github.com/cosmos/cosmos-sdk/blob/89e956c021edb1ec3e9d496b5efbcd11f3997d27/go.mod#L1

And 1.19 in their v0.47 release line: https://github.com/cosmos/cosmos-sdk/blob/504acaeab7985f7c079000b6015c08552ece9b0f/go.mod#L1

[thanethomson]

I'm checking whether this actually works in #206 and #208.

[andynog]

The SDK updated to go 1.20.0 as of last week and on the README it says it requires 1.20+
cosmos/cosmos-sdk@ad847c4