Module dependencies are transitive. 'go mod edit' edits the syntax of the go.mod file, but does not ensure that the resulting transitive dependencies are consistent.
To adjust your dependencies, use 'go get -d' instead of 'go mod edit': go get -d google.golang.org/grpc@v1.29.1 That will downgrade or remove other dependencies as needed so that the requested version is actually what is selected. On Tuesday, May 11, 2021 at 2:44:46 PM UTC-4 Sankar wrote: > Hi, > > I have some packages with some versions in my `go.mod` including some > indirect dependencies that are needed by some of my direct dependencies. In > this, there is a particular version of grpc that I want to use (and not the > latest). > > I add the specific version of grpc I want by: > > go mod edit -require=google.golang.org/gr...@v1.29.1 > <http://google.golang.org/grpc@v1.29.1> > > which correctly updates the `go.mod` file. But when I run the `go mod > vendor` next, this grpc line gets deleted and the latest of grpc is fetched > again. How do I enforce and vendor a particular version of an indirect > dependency ? > -- 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/8c79cc09-74e3-4f4d-b4f7-1b661a8ea806n%40googlegroups.com.
