From 72522c3570ea6b8a5eb32473fa2eacf48f204cef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aki=20M=C3=A4kinen?= Date: Thu, 8 Apr 2021 00:47:41 +0300 Subject: [PATCH] docs(Plugin Developer Guide): Update lifecycle list (#1874) The old list was missing analyzeCommits lifecycle and the verification lifecycle was incorrectly listed as "verify", when it should currently be "verifyConditions" in order to properly load. --- docs/developer-guide/plugin.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/developer-guide/plugin.md b/docs/developer-guide/plugin.md index dd9bde40..7843c651 100644 --- a/docs/developer-guide/plugin.md +++ b/docs/developer-guide/plugin.md @@ -2,7 +2,8 @@ To create a plugin for `semantic-release`, you need to decide which parts of the release lifecycle are important to that plugin. For example, it is best to always have a `verify` step because you may be receiving inputs from a user and want to make sure they exist. A plugin can abide by any of the following lifecycles: -- `verify` +- `analyzeCommits` +- `verifyConditions` - `prepare` - `publish` - `success` @@ -103,4 +104,4 @@ const { env } = context; if (env.GITHUB_TOKEN) { //... } -``` \ No newline at end of file +```