Skip to content

SCHED-2200: Bump golangci-lint to v2.12.2#2788

Open
theyoprst wants to merge 1 commit into
mainfrom
SCHED-2200/00
Open

SCHED-2200: Bump golangci-lint to v2.12.2#2788
theyoprst wants to merge 1 commit into
mainfrom
SCHED-2200/00

Conversation

@theyoprst

@theyoprst theyoprst commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

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

  • bump golangci-lint to v2.12.2 in the workflow and Makefile while the module still targets Go 1.25; both linter versions pass on this branch
  • fix govet inline-analyzer findings v2.12.2 reports: reflect.Ptr -> reflect.Pointer, constraints.Ordered -> cmp.Ordered, x/exp/slices -> stdlib slices

Lint 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

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.
@theyoprst theyoprst added go Pull requests that update Go code ignore-for-release Don't include this PR into changelog labels Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

go Pull requests that update Go code ignore-for-release Don't include this PR into changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant