When I move my linter Go tool dependencies into the new go.mod based tracking system, then I am starting to see go install tool errors. This tends to happen with the /x/ Go dependencies. It’s happening on GitHub Actions but not macOS. It’s happening with Go 1.24.1 but not Go 1.24.0.
It happens with errcheck and staticcheck.
Can we please allow tools to target different versions of (x) dependencies than the rest of the project? Like how NPM allows each dependency to have isolated sub-dependency trees.
Short term, Go project maintainers can try to work around these errors by keeping up with the very latest Go releases. However, it’s not realistic to expect that all Go projects in the world will rapidly republish to keep up with the Go release cadence. So more options that aid in backwards compatibility are appreciated.