From c3fab7712004b16eeea26387a2f3f89f4f1959de Mon Sep 17 00:00:00 2001 From: phips28 Date: Thu, 13 Feb 2020 20:37:10 +0100 Subject: [PATCH] readme --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2ace85c..1606275 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ you'll need to configured that workflow yourself. You can look to the * Based on the commit messages, increment the version from the lastest release. * If the string "BREAKING CHANGE" or "major" is found anywhere in any of the commit messages or descriptions the major version will be incremented. - * If a commit message begins with the string "feat" or "minor" then the minor version will be increased. This works + * If a commit message begins with the string "feat" or includes "minor" 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. * Push the bumped npm version in package.json back into the repo.