Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Update Go versions in all modules #24

Merged
merged 10 commits into from
Jul 25, 2022

Conversation

terryyylim
Copy link
Contributor

What this PR does / why we need it:
This PR is to keep our Go version up-to-date, by upgrading from 1.16 to 1.18.

Which issue(s) this PR fixes:

NONE

@terryyylim terryyylim self-assigned this Jul 22, 2022
@terryyylim terryyylim force-pushed the update-modules-go-version branch 4 times, most recently from 7a0a0c9 to 86a8c78 Compare July 25, 2022 02:03
@terryyylim terryyylim force-pushed the update-modules-go-version branch from 86a8c78 to 3deb700 Compare July 25, 2022 02:10
id: setup-go
uses: actions/setup-go@v3
with:
go-version: 1.16
go-version: "1.17"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

golangci-lint does not currently support Go 1.18 fully yet (golangci/golangci-lint#2649), hence pinning to Go 1.17 for linting workflows.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we instead use v2 of the action which seems to support Go1.18 (ref)? That's what Turing is using too.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, I misread your comment, the issue here is with golangci-lint, i.e if we use Go 1.18, the linter will fail.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Umm I think you changed the wrong action earlier. I meant golangci/golangci-lint-action@v3.
You can refer to this: https://github.com/gojek/turing/blob/main/.github/workflows/turing.yaml#L242

Copy link
Contributor Author

@terryyylim terryyylim Jul 25, 2022

Choose a reason for hiding this comment

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

Oh, I thought you meant setup. Ok I've updated that. I also refactored the versions to be part of environment variables so it'll be easier to change versions moving forward.

@terryyylim terryyylim requested a review from a team July 25, 2022 03:12
Copy link
Collaborator

@krithika369 krithika369 left a comment

Choose a reason for hiding this comment

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

Thanks for this PR. Left some comments / questions. Please feel free to merge after reviewing them.

clients/go.mod Show resolved Hide resolved
id: setup-go
uses: actions/setup-go@v3
with:
go-version: 1.16
go-version: "1.17"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we instead use v2 of the action which seems to support Go1.18 (ref)? That's what Turing is using too.

@@ -51,6 +51,11 @@ jobs:
with:
fetch-depth: 0

- name: Set up Go 1.18
Copy link
Collaborator

Choose a reason for hiding this comment

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

Most of the changes to this file can be reverted after resolving: #24 (comment)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants