Repository navigation
fix(ci): Use the latest golangci-lint release - #525
Merged
Merged
Conversation
Track the latest linter release alongside the stable Go toolchain to avoid recurring manual version bumps as Go support advances.
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.
Use
version: latestfor golangci-lint so the linter advances alongside the workflow’sstableGo toolchain without recurring manual version bumps. Keep the action itself pinned to its existing commit.Validation: the official golangci-lint v2.15.0 binary reports zero issues with Go 1.27.2;
git diff --checkpasses. Future linter releases can introduce new findings or configuration changes.