From 64ede2d482f7e5dd35a6eb14c137672199efa332 Mon Sep 17 00:00:00 2001 From: Jayson Smith Date: Tue, 14 Apr 2020 23:58:05 -0700 Subject: [PATCH] Update README.md --- README.md | 19 ++++--------------- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index 79bd147..61529de 100644 --- a/README.md +++ b/README.md @@ -42,15 +42,15 @@ The following about section was taken from Due to dependency changes in a coming merge to master, including breaking changes, you should update how you install or depend on godog so that you have a version specified. -### Install +## Install ``` -go get github.com/cucumber/godog/cmd/godog@v0.8.1 +go get github.com/cucumber/godog/cmd/godog@v0.9.0 ``` -Adding `@v0.8.1` will install v0.8.1 specifically instead of master. +Adding `@v0.9.0` will install v0.9.0 specifically instead of master. Running `within the $GOPATH`, you would also need to set `GO111MODULE=on`, like this: ``` -GO111MODULE=on go get github.com/cucumber/godog/cmd/godog@v0.8.1 +GO111MODULE=on go get github.com/cucumber/godog/cmd/godog@v0.9.0 ``` ## About @@ -75,17 +75,6 @@ business goal in mind at all times. When automated testing is this much fun, teams can easily protect themselves from costly regressions. -## Install -``` -go get github.com/cucumber/godog/cmd/godog@v0.9.0 -``` -Adding `@v0.9.0` will install v0.9.0 specifically instead of master. - -Running `within the $GOPATH`, you would also need to set `GO111MODULE=on`, like this: -``` -GO111MODULE=on go get github.com/cucumber/godog/cmd/godog@v0.9.0 -``` - ## Example The following example can be [found