From 60f82fd3f05614247ae15a5f705c1fadaec382e2 Mon Sep 17 00:00:00 2001 From: David Cumps Date: Sun, 1 Apr 2018 22:12:01 +0200 Subject: [PATCH] Fix breaking change documentation Breaking changes are a `major` release, not a `minor`. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7586a87e..f540c704 100644 --- a/README.md +++ b/README.md @@ -80,7 +80,7 @@ With the previous example: If a commit doesn't match any rule in `releaseRules` it will be evaluated against the [default release rules](lib/default-release-rules.js). With the previous example: -- Commits with a breaking change will be associated with a `minor` release. +- Commits with a breaking change will be associated with a `major` release. - Commits with `type` 'feat' will be associated with a `minor` release. - Commits with `type` 'fix' will be associated with a `patch` release. - Commits with `type` 'perf' will be associated with a `patch` release.