fix: support golangci-lint v2 JSON output#630
Open
FrankSpitulski wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
Problem
The Go scanner still invokes
golangci-lint run --out-format=json. golangci-lint v2 removed that flag, so every Go scan reportsgolangci_lint tooling unavailable (parser_error)and silently loses linter coverage.Fix
Use the v2
--output.json.path stdoutflag and disable stats so the existing JSON parser receives only the structured report. Add a focused regression test that executes the configured Go phase and verifies the exact command.Validation