Linter does not pass on `main` with fresh checkout

[ilyakamens]

I'm following the contributing guidelines here. Step 3 fails with the following error:

$ golangci-lint run
pkg/errors/error_test.go:1:9: var-naming: avoid package names that conflict with Go standard library package names (revive)
package errors
        ^
1 issues:
* revive: 1

$ sw_vers
ProductName:		macOS
ProductVersion:		26.2
BuildVersion:		25C56

$ go version
go version go1.25.6 darwin/arm64

$ golangci-lint --version
golangci-lint has version 2.8.0 built with go1.25.5 from e2e40021 on 2026-01-07T21:29:47Z

$ git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean

$ git log -n1
commit 64752fd0828c05dd265a0a17ac9646152c1aa856 (HEAD -> main, origin/main, origin/HEAD)
Author: JoannaaKL <joannaakl@github.com>
Date:   Tue Jan 20 10:06:28 2026 +0100

    Update README.md

    Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

$ echo $SHELL
/bin/zsh

Am I doing something wrong? Any help would be appreciated. Thank you.

[icamys]

Just accidentally passed by this thread, looking for an answer to a similar question.

Apparently, one of the golangci-lint sublinters - revive, got updated and introduced a breaking change that was propagated to many repositories that use the latest version of the linter by default. The details of the issue are described here.

[SamMorrowDrums]

Thank you for report, this is correct and we will address. We will be able to update branches and re-run CI.

[kerobbi]

This was addressed in #1988, thanks for raising this!