golangci-lint is using go v1.19 for gofmt linter inspite of using go v1.17 in the github action

[nishantwrp]

Welcome

• Yes, I'm using a binary release within 2 latest major releases. Only such installations are supported.
• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've included all information below (version, config, etc).
• Yes, I've tried with the standalone linter if available. (https://golangci-lint.run/usage/linters/)

Description of the problem

In our golangci-lint github workflow, we use go v1.17.x. The errors pointed out by the gofmt linter (see here) doesn't seem to get fixed when using gofmt -s . with the binary provided by go v.17.13 but they do get fixed with running the binary provided by go v1.19.

Here is our .golangci.yml config. How should I modify the config for it to use the go fmt linter corresponding to the go version that I'm using in the CI?

Version of golangci-lint

$ golangci-lint --version
# paste output here

Configuration file

$ cat .golangci.yml
# paste output here

Go environment

$ go version && go env
# paste output here

Verbose output of running

$ golangci-lint cache clean
$ golangci-lint run -v
# paste output here

Code example or link to a public repository

// add your code here

[boring-cyborg]

Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors.

[ldez]

duplicate of #3069 and golangci/golangci-lint-action#535

[ldez]

Offtopic

golangci-lint team as Go team supports only the 2 latest minor versions of Go.

https://golangci-lint.run/usage/faq/#which-go-versions-are-supported

Go v1.17 will not receive any security patch so it's recommended to update to at least go1.18.

[nishantwrp]

Yup, but even gofmt that comes with go v1.18 doesn't fix the errors pointed out.

[ldez]

My remark is explicitly offtopic, so yes this will not change your problem...