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

chore: Update golang to 1.18 #56

Merged
merged 3 commits into from
Jun 21, 2022

Conversation

Aerex
Copy link
Collaborator

@Aerex Aerex commented Jun 14, 2022

Context

The repo is using a very old version of golang and we should look into updating to the latest if possible. This PR will remove the vendor files in favor of go modules via the go.mod file.

Copy link
Owner

@maximilien maximilien 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.
/approve
/lgtm

@maximilien
Copy link
Owner

OK so there was another PR upgrading to 1.17 which passes the tests. Can you rebase with the new merged code. Sorry about that.

@maximilien maximilien self-assigned this Jun 14, 2022
@Aerex Aerex force-pushed the chore/update-golang branch from 6061b25 to 665d469 Compare June 14, 2022 22:21
Copy link
Owner

@maximilien maximilien left a comment

Choose a reason for hiding this comment

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

/lgtm

@Aerex Aerex force-pushed the chore/update-golang branch from 2ef97e6 to 153ea83 Compare June 16, 2022 16:13
@maximilien
Copy link
Owner

/ok-to-test

@Aerex Aerex force-pushed the chore/update-golang branch from 153ea83 to 2900be2 Compare June 17, 2022 20:59
@maximilien
Copy link
Owner

Merging and will try to figure out issue #58 which seems unrelated to your PR.

Thanks for the contribution.

@maximilien maximilien merged commit dda7449 into maximilien:master Jun 21, 2022
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