Daniel Martí

I think you need to raise this issue with golangci-lint. The panic does not appear to happen with the gofumpt binary at version v0.7.0, so it must be something that...

Indeed - the PR you show is you updating gofumpt to the release we did three days ago, but golangci-lint's latest release is a week old, so the two latest...

Yes, the issue is with the release times, see my last comment :) Note that the change here happened over a month ago, so I didn't exactly push it at...

I'll leave this issue open for now because, from past experience, users will keep opening issues here until golangci-lint does another release. I'd rather keep this open for another week...

Yep, understandable. FWIW I keep breaking changes to a minimum where I can. This was a rare exception as I explained above.

Yep, correct. Just note that Go versioning is different from semver in that Semver dictates `v1.22-rc.1 < v1.22 == v1.22.0`, but Go versioning dictates `go1.22 < go1.22rc1 < go1.22.0`, because...

Well, `go1.22` and `go1.23` will never be releases anymore, but they are still valid Go versions which can be used in `go.mod` files, via the go/version API, with gofumpt, etc....

https://github.com/golangci/golangci-lint/releases/tag/v1.60.2 happened four days ago as promised - closing this.

Tracking this issue here is correct. I think sending a PR to do this change would be fine.

Agreed. We should not be triggering or investigating runtime bugs.