Skip to content

Conversation

ldez
Copy link
Member

@ldez ldez commented Sep 18, 2025

I opened a PR against the original repository with the fix.

gostaticanalysis/nilerr#21

In the meantime, to fix the bug, we will use a fork.

This is a special case; there is no rule about forking when a linter author is not responsive.
The default rule stays the same: no forks.

The fork is inside the golangci org: https://github.com/golangci/nilerr

Fixes #6043

@ldez ldez added this to the v2-unreleased milestone Sep 18, 2025
@ldez ldez added dependencies Relates to an upstream dependency linter: update version Update version of linter go Pull requests that update Go code labels Sep 18, 2025
@ldez ldez merged commit b65912b into golangci:main Sep 19, 2025
18 checks passed
@ldez ldez deleted the fix/nilerr-panic branch September 19, 2025 23:26
@ldez ldez modified the milestones: v2-unreleased, v2.5 Sep 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Relates to an upstream dependency go Pull requests that update Go code linter: update version Update version of linter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

stack overflow on nilerr linter
2 participants