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

Bump golangci to v1.59.1 #1599

Merged
merged 1 commit into from
Jun 12, 2024
Merged

Bump golangci to v1.59.1 #1599

merged 1 commit into from
Jun 12, 2024

Conversation

kuritka
Copy link
Collaborator

@kuritka kuritka commented Jun 11, 2024

I made the changes that were required to pass the linter. I removed the internal directory which hasn't made much sense for a long time. I've modified the GitHub action

the new linter has depguard as the main change, which is a guard for imported packages. these must be explicitly enabled/disabled in the configuration.

@kuritka kuritka force-pushed the golangci-v1.59.1 branch 2 times, most recently from 66ecace to a9e1361 Compare June 11, 2024 13:04
@ytsarev
Copy link
Member

ytsarev commented Jun 12, 2024

@kuritka Sorry, looks like the merge of #1602 led to the conflict, can you please rebase together with other neighbour PRs?

I made the changes that were required to pass the linter. I removed the internal `directory` which hasn't made much sense for a long time. I've modified the GitHub action

the new linter has depguard as the main change, which is a guard for imported packages. these must be explicitly enabled/disabled in the configuration.
- https://golangci-lint.run/usage/linters/#depguard
- https://github.com/OpenPeeDeeP/depguard

Signed-off-by: Michal Kuritka <[email protected]>
@kuritka
Copy link
Collaborator Author

kuritka commented Jun 12, 2024

@ytsarev amended. No worries, the changes may go little against each other as I did in separate PR's, so rebasing is in plan.

@ytsarev ytsarev merged commit 468ed1e into master Jun 12, 2024
21 checks passed
@ytsarev ytsarev deleted the golangci-v1.59.1 branch June 12, 2024 22:14
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