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 Go versions to test. #336

Merged
merged 1 commit into from
Aug 2, 2024
Merged

Conversation

NullHypothesis
Copy link
Contributor

We should include the latest minor release (1.22) and I see no harm in discontinuing testing with 1.20.

This PR is identical to #326 but I couldn't merge it because there are two now-obsolete jobs that are stuck, so I'm opening a new PR.

@thetorpedodog
Copy link
Contributor

If we’re doing this, perhaps we should update the go.mod file to say "go 1.21" as well.

We need to be sure that the latest minor release works well.
@NullHypothesis
Copy link
Contributor Author

If we’re doing this, perhaps we should update the go.mod file to say "go 1.21" as well.

On second thought, I think it's best to add 1.22 to the test array while keeping 1.20 in go.mod. After all, we're not using any new language features, so there's no strong reason to update.

@NullHypothesis NullHypothesis merged commit 4bdba5c into master Aug 2, 2024
8 checks passed
@NullHypothesis NullHypothesis deleted the phw/update-go-versions-2 branch August 2, 2024 15:12
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.

3 participants