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(*) cleanup after upgrading to go 1.14 #727
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jakubdyszkiewicz
approved these changes
May 11, 2020
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.
Awesome, thanks!
I love all the removed dependencies. Can we integrate go mod tidy
in our Makefiles? Maybe on make check
?
@jakubdyszkiewicz excellent idea. I will use this PR to push the proposed addition |
nickolaev
changed the title
Chore/cleanup after go14
chore(*) cleanup after upgrading to go 1.14
May 11, 2020
after e4d31d, the linter does nto finish its job and complains with "WARN [runner] Can't run linter goanalysis_metalinter" and "export data is newer version - update tool". This is described here golangci/golangci-lint#893. The solution is to use newer golangci-lint, which is done here. Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Go 1.14 deprecates BuildNameToCertificate as described here golang/go#37626 Fixing the linter exposes this issue and it's fixed here. Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Also Move the namespace creation to BeforeSuite section in k8s store testing. Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
nickolaev
force-pushed
the
chore/cleanup_after_go14
branch
from
May 11, 2020 12:20
01d70fd
to
2cfa3da
Compare
Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
After the upgrade to go 1.14 in #718, the golang-ci is actually not completing its run
successfully. Fixing this by bumping its version to 1.26 (latest) uncovers an issue with a
deprecated call
BuildNameToCertificate
, which can be omitted.Also run
go mod tidy
to cleanup unneeded dependencies.Full changelog
go mod tidy
Issues resolved
None