-
Notifications
You must be signed in to change notification settings - Fork 55
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
chore: update to supported go versions #157
base: v4
Are you sure you want to change the base?
Conversation
github.com/twmb/murmur3 v1.1.5/go.mod h1:Qq/R7NUyOfr65zD+6Q5IHKsJLwP7exErjN6lyyq3OSQ= | ||
gopkg.in/h2non/gock.v1 v1.0.10 h1:D4j796HhgidcxF0LnDyFXcoEbEZWoLEWf0kRh61p22w= | ||
gopkg.in/h2non/gock.v1 v1.0.10/go.mod h1:KHI4Z1sxDW6P4N3DfTWSEza07YpkQP7KJBfglRMEjKY= | ||
github.com/stretchr/objx v0.1.0/go.mod h1:HFkY916IF+rwdDfMAkV7OtwuqBVzrE8GR6GFx+wExME= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we have explosion of versions here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that go 1.17 updated the format for go.mod/go.sum, and since we now explicitly state go 1.19 in our go.mod, the new format takes effect.
With this change we might be dropping support for older versions of go. Maybe something we want to do... I did test the current v4 against newer versions of go and it seems to work well: #177 |
Discussion
Having read https://go.dev/doc/devel/release I realised we haven't looked at our build matrix since 1.16 came out, and our go.mod is still pointing to 1.13 which was EoL 2021-02-16.
This PR bumps go.mod to 1.19 (the current oldest supported version) and updates the build matrix to 1.19, 1.20 and 1.21