-
Notifications
You must be signed in to change notification settings - Fork 219
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
update ci to use go matrix to test using 1.17/18/19/20/21 #932
Conversation
Signed-off-by: cpanato <[email protected]>
I will fix the lints as well |
@cpanato quick question, is there a reason for this CI/mod change? Asking bc we haven't yet discussed up to which Go version we want to test/"support". README IIRC still says 1.17. We could use matrix strategy tests. Just not sure about the go.mod bump yet. cc/ @lionelvillard |
@embano1 from my point of view go 1.17 is deprecated and we should test/build this project with latest go releases. otherwise we should aim to test/build with latest go version. will wait feedback to change the code |
+1 on the matrix since we currently state in the README
Regarding bumping |
That one we can leave, but that tells what the minimum go version is to use the lib, but also, the newer go version has better management of the go modules, so it is good to bring that up to a newer go release. |
Yes, main concern from my end is that this will encourage usage of Go 1.18 APIs/features (Generics for example). This is not a bad thing per se, but requires users to also be on that Go version to compile. Hence my caution. Feel free to start with the Go version matrix in CI. |
Signed-off-by: cpanato <[email protected]>
closing this looks like it is done in #958 |
if want we can go straight to 1.21
also we might want to bump the go modules as well to set the go version to maybe 1.19
this will require an update in the github status check