From d9c164822e47c414184ba5f0987e389bbf1ffe89 Mon Sep 17 00:00:00 2001 From: phips28 Date: Sat, 26 Oct 2019 21:10:38 +0200 Subject: [PATCH] README --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 7f6ca6d..140441f 100644 --- a/README.md +++ b/README.md @@ -16,6 +16,5 @@ you'll need to configured that workflow yourself. You can look to the * If a commit message begins with the string "feat" then the minor version will be increased. This works for most common commit metadata for feature additions: `"feat: new API"` and `"feature: new API"`. * All other changes will increment the patch version. -* Publish to npm using the configured token. * Push the bumped npm version in package.json back into the repo. -* Push a tag for the new version to GitHub. +* Push a tag for the new version back into the repo.