-
Notifications
You must be signed in to change notification settings - Fork 63
chore: bump Go to v1.22 #83
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
Conversation
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.
ty!
Pull Request Test Coverage Report for Build 15427738042Details
💛 - Coveralls |
@@ -11,27 +11,27 @@ jobs: | |||
runs-on: ubuntu-latest | |||
strategy: | |||
matrix: | |||
go-version: ["1.21"] | |||
go-version: ["1.22"] |
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.
there's no matrix action going on here, this is just an artifact of history. if you're feeling noble you can scrap the whole matrix and inline the version. but also not necessary
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.
Will probably leave it as is for now haha - is convention to keep this two versions behind latest?
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.
not a problem! and yes, that's right. it helps make sure that the linter doesn't recommend something in 1.24 that isn't supported in 1.22. Perfect example is the copyloop var change was added in 1.22. but while we supported 1.21, we didn't want to use that rule. using the lowest supported version reinforces that design goal.
formatters: | ||
enable: | ||
- gofmt | ||
- goimports |
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 didn't vet all these settings, any changes of note besides the comments being correctly enforced and the copyloop linter getting enabled?
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.
No changes of note - the settings
block was copied from the previous linters-settings
block (formerly at L1) because the YAML definition had changed with the version bump
Bump go to v1.22 and fix lint issues