Linter for checking 'MVS' of go module

[xiangd...@gmail.com]

Hi all,

I'm wondering if any linter, or is it practical to make one, checks whether a go module's code change conforms the minimal version selection rules, say linter warns a v2 is needed if incompatible changes to APIs are introduced in the current change under linting?

[Mhd Shulhan]

On Wed, 9 Dec 2020, 11:42 xiangd...@gmail.com, <xiangd...@gmail.com> wrote:

Hi all,

I'm wondering if any linter, or is it practical to make one, checks whether a go module's code change conforms the minimal version selection rules, say linter warns a v2 is needed if incompatible changes to APIs are introduced in the current change under linting?

There is an experiment on tooling called gorelease [1]. I believe its in working-in-progress [2].

[1] golang.org/x/exp/cmd/gorelease

[2] https://github.com/golang/go/issues/26420

[xiangd...@gmail.com]

Thanks a lot, Shulhan.