Could you provide explicit steps (ideally a `go.mod` file and a corresponding `.go` source file, and the version of the Go toolchain you are using) to reproduce the problem?
All three of those `v2` versions appear to have `go.mod` files, so the `go` command should not allow them to be used as `+incomptable` versions at all, let alone use them by default. (See https://golang.org/doc/go1.13#version-validation.) Moreover, because the latest `v1` release of that module includes a go.mod <https://github.com/nicksnyder/go-i18n/blob/v1.10.1/go.mod> file, as of Go 1.14 beta 1 the `go` command should ignore `+incompatible` versions when resolving upgrades to that module. (See https://tip.golang.org/doc/go1.14#incompatible-versions.) On Friday, January 3, 2020 at 3:49:27 PM UTC-5, Jérôme LAFORGE wrote: > > Hello, > > Does it exist a way to exclude modules' version and above ? > > Currently I have to do this (in order to not use v2) in my go.mod: > > exclude ( > github.com/nicksnyder/go-i18n v2.0.1+incompatible > github.com/nicksnyder/go-i18n v2.0.2+incompatible > github.com/nicksnyder/go-i18n v2.0.3+incompatible > ) > > Many thx > Jérôme > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/c195e5b0-866a-4b42-af8d-15b7eb52db5a%40googlegroups.com.
