SCHED-2200: Bump golangci-lint to v2.12.2#2788
Open
theyoprst wants to merge 1 commit into
Open
Conversation
The lint job runs via pull_request_target, so the workflow definition comes from the base branch. Bumping the pin while the module still targets Go 1.25 lets the Go 1.26 migration PR lint with a linter that supports it. Fix govet inline-analyzer findings the new version reports: reflect.Ptr -> reflect.Pointer, constraints.Ordered -> cmp.Ordered, x/exp/slices -> stdlib slices.
This was referenced Jul 24, 2026
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 1.26 migration (#2789) cannot pass lint while main pins golangci-lint v2.5.0: the lint job runs on
pull_request_target, which takes the workflow definition from the default branch, and v2.5.0 is built with go1.25 and refuses go 1.26 modules.Solution
reflect.Ptr->reflect.Pointer,constraints.Ordered->cmp.Ordered,x/exp/slices-> stdlibslicesLint on the rest of the stack (#2789 -> #2784 -> #2785) keeps using main's v2.5.0 and stays red until this PR merges; after merging, rebase the stack to re-trigger their checks.
Testing
Linted with v2.5.0 (what CI runs before this merges) and v2.12.2 (what it runs after): 0 issues both. Unit suite green. The lint check on this PR passed in CI.
Release Notes
None