-
Notifications
You must be signed in to change notification settings - Fork 53
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: Bump to GoLang v1.19 #818
chore: Bump to GoLang v1.19 #818
Conversation
Copying my comment on #817 here: The issue that made us hard code to version v1.47 still persists (#727) lint action uses the default built binary that enforces go v1.19 formatting. suggest waiting for this until that is fixed (or else we would manually have to build golang-ci every time in the CI). Or until we bump to GoLang v1.19 |
That means CI check will fail with |
Yes, with the current golang-ci workflow action version we have and the actual hardcoded golangci version. However once v0.3.1 is kicked out the door, will investigate if perhaps there are new golang-ci action versions and if they fix this bug. Until then suggest leaving this as draft. |
6d858bc
to
30e5c44
Compare
Blocked until this is fixed: golangci/golangci-lint-action#540 |
30e5c44
to
ccfcdad
Compare
ccfcdad
to
7eb225b
Compare
bf2974d
to
93e509e
Compare
968fc54
to
bcb2025
Compare
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.
LGTM
Perhaps we can additionally drop support for Go 1.18 as it AFAIK not further supported by Official Go Team. This way we can additionally get rid of things like https://github.com/sourcenetwork/defradb/blob/develop/tests/integration/utils.go#L53 in this PR |
There is an init block in the main intergration test utils that needs removal within this PR too (unless we want to open a new issue for it), Orpheus noted it in #1070 |
bcb2025
to
2deb84f
Compare
Done |
tests/integration/query/commits/with_dockey_order_limit_offset_test.go
Outdated
Show resolved
Hide resolved
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.
Unapproving as I missed the cid change, happy for you to merge if that has been resolved and someone else approves though
513da54
to
f00aa58
Compare
This PR shouldn't merge until #1094 is in, in which case the cids won't change (I have dropped that commit btw). |
f00aa58
to
b402550
Compare
- Resolves #817 - Resolves #1070 - This PR was initially started as: `ci: Bump workflow's golang-ci lint version` to fix the golang-ci lint issue. This work that was done in this PR was the following: - Remove the `deadcode` and `varcheck` linters that are now deprecated with `v1.49` - Remove all `nolint` directives where the deprecated linters were being referenced. - Update CI's linter version to use the latest version. However as the golang-ci lint team still didn't fix that issue but golang1.19 was released we can just fix those errors and bump the GoLang version for defradb and keeping the previous linter fixes. Inaddtion also re-enabling the `goheader` linter rule as the change was somehow dropped when we released defradb v0.4.
## Relevant issue(s) - Resolves #522 - Resolves #1687 ## Description - This is a routine version bump of GoLang, the previous bump was done in (#818) - This PR also introduces a new workflow action (not-mandatory to pass in order to merge) that was showing some vulnerabilities pre-version-bump, all of the vulnerabilities were resolved once the golang version was bumped. In future this trigger will be used to bump golang versions. - Also updates the golang version for AWS AMI generation. Note: - Before the bump we had 13 vulnerabilities: https://github.com/sourcenetwork/defradb/actions/runs/5629964770/job/15255493129?pr=1688 - After the bump: passing with no vulnerabilities. ## How has this been tested? - Added action that failed with vulnerabilities. - Bumped version. - Vulnerabilities were resolved and action passed. Specify the platform(s) on which this was tested: - Arch Linux
- Resolves sourcenetwork#817 - Resolves sourcenetwork#1070 - This PR was initially started as: `ci: Bump workflow's golang-ci lint version` to fix the golang-ci lint issue. This work that was done in this PR was the following: - Remove the `deadcode` and `varcheck` linters that are now deprecated with `v1.49` - Remove all `nolint` directives where the deprecated linters were being referenced. - Update CI's linter version to use the latest version. However as the golang-ci lint team still didn't fix that issue but golang1.19 was released we can just fix those errors and bump the GoLang version for defradb and keeping the previous linter fixes. Inaddtion also re-enabling the `goheader` linter rule as the change was somehow dropped when we released defradb v0.4.
## Relevant issue(s) - Resolves sourcenetwork#522 - Resolves sourcenetwork#1687 ## Description - This is a routine version bump of GoLang, the previous bump was done in (sourcenetwork#818) - This PR also introduces a new workflow action (not-mandatory to pass in order to merge) that was showing some vulnerabilities pre-version-bump, all of the vulnerabilities were resolved once the golang version was bumped. In future this trigger will be used to bump golang versions. - Also updates the golang version for AWS AMI generation. Note: - Before the bump we had 13 vulnerabilities: https://github.com/sourcenetwork/defradb/actions/runs/5629964770/job/15255493129?pr=1688 - After the bump: passing with no vulnerabilities. ## How has this been tested? - Added action that failed with vulnerabilities. - Bumped version. - Vulnerabilities were resolved and action passed. Specify the platform(s) on which this was tested: - Arch Linux
Relevant issue(s)
Resolves #817
Resolves #1070
Description
This PR was initially started as:
ci: Bump workflow's golang-ci lint version
to fix the golang-ci lint issue. This work that was done in this PR was the following:deadcode
andvarcheck
linters that are now deprecated withv1.49
nolint
directives where the deprecated linters were being referenced.However as the golang-ci lint team still didn't fix that issue but golang1.19 was released we can just fix those errors and bump the GoLang version for defradb and keeping the previous linter fixes.
Inaddtion also re-enabling the
goheader
linter rule as the change was somehow dropped when we released defradb v0.4.How has this been tested?
Local & CI
Specify the platform(s) on which this was tested: