You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the action would determine, today, that the version of Go it should setup is 1.23.3, instead of 1.24.0, which is the latest available Go version matching the go constraint the author opted for, as explained by the go directive documentation here:
go minimum-go-version
minimum-go-version
The minimum version of Go required to compile packages in this module.
Perhaps there's good reason as to why the action determines the version as it does today, and if that's the case please let me know, but I think that, when go-version-file is used, the action should opt for the greatest available Go version matching the author's specification (perhaps only in cases where check-latest is set), instead of opting for the provided minimum required version.