From f0d5fe99bce5cf0a89d7f62dafd4ca367d89d0f5 Mon Sep 17 00:00:00 2001 From: Jean de Klerk Date: Fri, 20 Sep 2019 10:43:25 -0600 Subject: [PATCH] Fix mod graph output --- Resolving-Problems-From-Modified-Module-Path.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Resolving-Problems-From-Modified-Module-Path.md b/Resolving-Problems-From-Modified-Module-Path.md index dd532e9a..0870414b 100644 --- a/Resolving-Problems-From-Modified-Module-Path.md +++ b/Resolving-Problems-From-Modified-Module-Path.md @@ -50,7 +50,7 @@ Fixing the first example is simple, the only link is from `my-go-project` - whic ``` $ GO111MODULE=on go mod graph -my-go-project golang.org/x/lint v0.0.0-20190301231843-5614ed5bae6f +my-go-project golang.org/x/lint@v0.0.0-20190301231843-5614ed5bae6f ``` Fixing the second example involves more steps but is essentially the same process: `google.golang.org/grpc@v1.16.0` provides the link to `github.com/golang/lint`, so `google.golang.org/grpc` should update its `go.mod` from `github.com/golang/lint@v0.0.0-20180702182130-06c8688daad7` to `golang.org/x/lint v0.0.0-20190301231843-5614ed5bae6f` (this thankfully already happened in `v1.17.0`). Then, `my-go-project` should update its `go.mod` to include the new version of `google.golang.org/grpc`, so that we now have: