-
Notifications
You must be signed in to change notification settings - Fork 639
Upgrade to Go 1.19 #174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
My view is that we probably want to be aligned with the SDK when changing the (recommended) version of Go |
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 |
The SDK updated to go 1.20.0 as of last week and on the README it says it requires 1.20+ |
Uh oh!
There was an error while loading. Please reload this page.
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
main
#206v0.37.x
#2080.34.x
#360The text was updated successfully, but these errors were encountered: