chore: update go version in module

[mmorel-35]

Description

Go 1.24.0 has been released on since 11 February 2025

This updates Go version from 1.18 to 1.23

Notice that loong64 arch is only available since Go1.19 so it's surprising to see that gopsutil supports it (at least partially) with a Go1.18 module.

[shirou]

Thank you for the suggestion!

However, gopsutil is a library that supports a wide range of platforms. Not all platforms provide the latest version of Go in their package managers, and some users might not be able to upgrade their Go version.

gopsutil depends on golang.org/x/sys, and x/sys's golang dependency is regularly updated. So, in practice, the version from golang.org/x/sys might be used, but I still believe that the library itself should aim to support the lowest possible Go version.

Of course, if there’s a need to use new language features in Go, I’m not against it. However, I think we should discuss whether it’s truly necessary at that time.

[mmorel-35]

Would you consider at least 1.19 ? That would then allow to extend golangci-lint matrix for loong64

[mmorel-35]

github.com/google/go-cmp require go1.21 and there are no workflows that are still using go1.19

[shirou]

I just noticed golang/go#69095. This proposal suggests automatically updating the go.mod version to 1.(N-1).0, including x/sys, and already accepted.

In the discussion, there are comments suggesting that the required version should be set to the minimum, but it seems that people like rsc believe it's important to encourage the use of the latest version.

Personally, I also agree with the idea of keeping the version at the minimum. However, the overall direction of Go team seems to be to promote the use of the latest version. Therefore, I've changed my mind and now think it might be better to change 1.23.0 in go.mod.

[mmorel-35]

Alright, that ready to Go :) !

Golangci-lint timeout it extended because of Windows exeeding it.

[shirou]

Thank you for the update. However, when I looked at the diff, I wondered, "Why is the toolchain directive included?" So I did some research and found golang/go#65847. I haven't read through the entire issue comments, but it seems that the toolchain directive might be automatically added and could potentially cause issues.

It doesn't seems to be resolved yet, so how about removing the toolchain directive in this PR for now?