fix(golangci-lint): better error message when config version doesn't match tool version#1081
Merged
malept merged 2 commits intomalept/feat/golangci-lint-2.9.0from Feb 17, 2026
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Contributor
|
Link to code coverage report (posted by coverbot 🤖) |
iamrz1
approved these changes
Feb 17, 2026
malept
added a commit
that referenced
this pull request
Feb 17, 2026
* fix(golangci-lint): Go >= 1.26 needs golangci-lint >= 2.9.0 * fix(golangci-lint): only append arguments if they work for the given subcommand * fix(golangci-lint): better error message when config version doesn't match tool version (#1081)
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.
What this PR does / why we need it
For whatever reason,
golangci-lintv2 doesn't give a human-friendly error when it encounters a v1 config, despite the fact that it should know what to expect based on theversionconfig value (or lack thereof).Jira ID
DT-5156
Notes for reviewers
I tested this on a service that was having this issue (upgraded devbase RC but not stencil-golang RC) with the expected output: