Upgrade golangci-lint GitHub Action go v5
and linter to 1.56
#223
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.
A small one to upgrade:
v4
tov5
A small change, but I upgraded locally at some point, and it's causing a
build issue in #212. The
tparallel
lint previously had a bug whereit'd want you to put a
t.Parallel()
on test cases that uset.Setenv()
,even though use of
t.Parallel()
witht.Setenv()
is disallowed by Go'stest framework, so you'd have to mark those test cases with
nolint
.That bug's been fixed now, and now the linter detects that the
nolint
is no longer necessary, and automatically strips it out with my upgraded
golangci-lint version, causing a failure when I push to CI.
The
v5
GitHub Action is also somewhat nice because it stops using adeprecated NodeJS version, so produces fewer warnings in the log.