aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--content/publishing-go-modules.article18
1 files changed, 10 insertions, 8 deletions
diff --git a/content/publishing-go-modules.article b/content/publishing-go-modules.article
index 951a085..a215072 100644
--- a/content/publishing-go-modules.article
+++ b/content/publishing-go-modules.article
@@ -162,14 +162,16 @@ Tagging a new version has a few steps:
4. Push the new tag to the origin repository.
- $ go mod tidy
- $ go test ./...
- ok example.com/hello 0.015s
- $ git add go.mod go.sum hello.go hello_test.go
- $ git commit -m "hello: changes for v0.1.0"
- $ git tag v0.1.0
- $ git push origin v0.1.0
- $
+```
+$ go mod tidy
+$ go test ./...
+ok example.com/hello 0.015s
+$ git add go.mod go.sum hello.go hello_test.go
+$ git commit -m "hello: changes for v0.1.0"
+$ git tag v0.1.0
+$ git push origin v0.1.0
+$
+```
Now other projects can depend on `v0.1.0` of `example.com/hello`. For your own
module, you can run `go list -m example.com/hello@v0.1.0` to confirm the latest