Skip to content

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

Merged
merged 1 commit into from
Jun 4, 2025
Merged

Conversation

justinhwang
Copy link
Contributor

@justinhwang justinhwang commented Jun 3, 2025

Bump go to v1.22 and fix lint issues

Copy link
Collaborator

@jogly jogly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ty!

@coveralls
Copy link

Pull Request Test Coverage Report for Build 15427738042

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 98.527%

Totals Coverage Status
Change from base Build 14172792260: 0.0%
Covered Lines: 602
Relevant Lines: 611

💛 - Coveralls

@@ -11,27 +11,27 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
go-version: ["1.21"]
go-version: ["1.22"]
Copy link
Collaborator

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

Copy link
Contributor Author

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?

Copy link
Collaborator

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
Copy link
Collaborator

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?

Copy link
Contributor Author

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

@zachcoleman zachcoleman merged commit 5c18e4a into uber:master Jun 4, 2025
6 checks passed
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.

4 participants