update cli dep | update release docs

This commit is contained in:
max furman 2019-03-26 15:06:38 -07:00
parent 2f2e748aca
commit 1bb25b5171
2 changed files with 10 additions and 5 deletions

2
Gopkg.lock generated
View file

@ -298,7 +298,7 @@
"utils", "utils",
] ]
pruneopts = "UT" pruneopts = "UT"
revision = "f1bc6bb3b78d3d508d6cbff1a01402035b76a431" revision = "a2e2d27fd5eff22ba94b1f2bd2fc946f5bb7f041"
[[projects]] [[projects]]
branch = "master" branch = "master"

View file

@ -15,8 +15,13 @@ e.g. `v1.0.2`
* **Release Candidate**: not ready for public use, still testing. must have a * **Release Candidate**: not ready for public use, still testing. must have a
`-rc*` suffix. e.g. `v1.0.2-rc` or `v1.0.2-rc.4` `-rc*` suffix. e.g. `v1.0.2-rc` or `v1.0.2-rc.4`
1. **Update the version of step/cli**
1. **Commit all changes.** ```
$ dep ensure -update github.com/smallstep/cli
```
2. **Commit all changes.**
Make sure that the local checkout is up to date with the remote origin and Make sure that the local checkout is up to date with the remote origin and
that all local changes have been pushed. that all local changes have been pushed.
@ -26,7 +31,7 @@ e.g. `v1.0.2`
git push git push
``` ```
2. **Tag it!** 3. **Tag it!**
1. **Find the most recent tag.** 1. **Find the most recent tag.**
@ -38,7 +43,7 @@ e.g. `v1.0.2`
The new tag needs to be the logical successor of the most recent existing tag. The new tag needs to be the logical successor of the most recent existing tag.
See [versioning](#versioning) section for more information on version numbers. See [versioning](#versioning) section for more information on version numbers.
2. **Select the next tag (but don't actually tag anything yet!!).** 2. **Select the type and value of the next tag.**
Is the new release a *release candidate* or a *standard release*? Is the new release a *release candidate* or a *standard release*?
@ -73,7 +78,7 @@ e.g. `v1.0.2`
git push origin tag v1.0.3-rc.1 # release candidate git push origin tag v1.0.3-rc.1 # release candidate
``` ```
6. Check the build status at 4. Check the build status at
[Travis-CI](https://travis-ci.com/smallstep/certificates/builds/). [Travis-CI](https://travis-ci.com/smallstep/certificates/builds/).
Travis will begin by verifying that there are no compilation or linting errors Travis will begin by verifying that there are no compilation or linting errors