always use 1.

Orygin · Jun 23, 2019 · e9bedc1 · e9bedc1
1 parent a919438
commit e9bedc1
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/docs/release-process.md b/docs/release-process.md
@@ -2,11 +2,11 @@
 Releases are performed automatically with travis.
 
 1. `git tag -a v<major>.<minor>.<patch>` or `git tag -a v<major>.<minor>.<patch>-<prerelease>`   _('v' required)_ where anything before the first `.` in `<prerelease>` will be become the [npm dist-tag](https://docs.npmjs.com/cli/dist-tag).
-2. `git push`
-3. `git push --tag`
-4. Wait for travis to create a new draft GitHub release with the build attached. At this point the new npm package should have been published.
-5. Add the release notes to the new draft GitHub release.
-6. Publish the GitHub release.
+1. `git push`
+1. `git push --tag`
+1. Wait for travis to create a new draft GitHub release with the build attached. At this point the new npm package should have been published.
+1. Add the release notes to the new draft GitHub release.
+1. Publish the GitHub release.
 
 ## Examples
 - `git tag -a v1.2.3` will result in `1.2.3` being published with the `latest` npm tag.