From cac48823f12d8b0bd99d2938fe137f745d3b2bd3 Mon Sep 17 00:00:00 2001 From: Pierre Vanduynslager Date: Fri, 6 Jul 2018 23:33:28 -0400 Subject: [PATCH] docs: clarify `verifyRelease` plugin description --- docs/usage/plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/usage/plugins.md b/docs/usage/plugins.md index 5dfd462a41..441f61b665 100644 --- a/docs/usage/plugins.md +++ b/docs/usage/plugins.md @@ -20,7 +20,7 @@ Default implementation: [@semantic-release/commit-analyzer](https://github.com/s ### verifyRelease plugin -Responsible for verifying the parameters (version, type, dist-tag etc...) of the release that is about to be published match certain expectations. For example the [cracks plugin](https://github.com/semantic-release/cracks) is able to verify that if a release contains breaking changes, its type must be `major`. +Responsible for verifying the parameters (version, type, dist-tag etc...) of the release that is about to be published. For example the [cracks plugin](https://github.com/semantic-release/cracks) is able to verify that if a release contains breaking changes, its type must be `major`. Default implementation: none.