Skip to content
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

Closed
wants to merge 2 commits into from

Conversation

cpanato
Copy link
Contributor

@cpanato cpanato commented Aug 16, 2023

  • update ci to use go matrix to test using 1.17/18/19/20/21

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

@cpanato
Copy link
Contributor Author

cpanato commented Aug 16, 2023

I will fix the lints as well

@cpanato cpanato marked this pull request as draft August 16, 2023 18:12
@embano1
Copy link
Member

embano1 commented Aug 17, 2023

@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

@cpanato
Copy link
Contributor Author

cpanato commented Aug 17, 2023

@embano1 from my point of view go 1.17 is deprecated and we should test/build this project with latest go releases.
We can add a go matrix and test it with go 1.17/18/19/20.... if that is what the maintainers want, happy to help here.

otherwise we should aim to test/build with latest go version.

will wait feedback to change the code
thanks!

@embano1
Copy link
Member

embano1 commented Aug 17, 2023

+1 on the matrix since we currently state in the README

Note: Supported go version: 1.17+

Regarding bumping go 1.17 I'm not sure about the benefits here? Can you elaborate more?

@cpanato
Copy link
Contributor Author

cpanato commented Aug 17, 2023

+1 on the matrix since we currently state in the README

Note: Supported go version: 1.17+

Regarding bumping go 1.17 I'm not sure about the benefits here? Can you elaborate more?

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.
but again it is a decision from the maintainers

@embano1
Copy link
Member

embano1 commented Aug 17, 2023

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

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.

@cpanato cpanato changed the title update ci to use go1.20 for now update ci to use go matrix to test using 1.17/18/19/20/21 Aug 18, 2023
@cpanato
Copy link
Contributor Author

cpanato commented Oct 24, 2023

closing this looks like it is done in #958

@cpanato cpanato closed this Oct 24, 2023
@cpanato cpanato deleted the update-go branch October 24, 2023 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants