Olivier Ligot

As explained in the [toolchain doc](https://go.dev/doc/toolchain), your go.mod should specify a go version greater than or equal to version 1.22.0, if one of your dependencies has a version 1.22.0 in...

AFAIK, the go command used to find dependencies updates (which is used internally by go-mod-upgrade) doesn’t expose what’s needed for your use case. If that’s true, the only option you...

This may already be fixed in #46 Can you try again with [v0.10.0](https://github.com/oligot/go-mod-upgrade/releases/tag/v0.10.0) that has just been released ?

> Are you able to provide a reproduction repo perhaps ? Yeah, @jherman a reproduction repo would help us to find if there is a problem or not.

See also https://github.com/golang/go/issues/38762

Thanks for the follow-up ! Major modules version in Go is a hot topic right now, with articles like [Semantic Import Versioning is unsound](https://peter.bourgon.org/blog/2020/09/14/siv-is-unsound.html) and [Go Modules have a v2+...

Thanks for the link, @StevenACoffman ! Finding the latest version of a module is still quite hacky for now, as it [requires parsing the html from the https://pkg.go.dev website](https://github.com/icholy/gomajor/blob/2ce7ff463e5e9811e511b2b8e761a4558991edf2/internal/latest/latest.go#L38-L63). I...

Hi @ebezault, Is there a reason why this pull request hasn't been merged yet ?

Note that there is an open discussion in the Gobo mailing list. Here is the replay from Eric: http://tech.groups.yahoo.com/group/gobo-eiffel/message/1823 In the meantime, the ecf files are available in another Git...

I'm also for the split. @pgcrism did the same for the [SAFE Project](https://github.com/safe-eiffel/) when it was moved from Sourceforge to Github. I don't remember if the history was kept: maybe...