From d369a854887cb4ff6120173c04e8712bc6c16aa1 Mon Sep 17 00:00:00 2001 From: "cwilton@scottlogic.com" Date: Thu, 17 Oct 2024 08:37:55 +0100 Subject: [PATCH] Updated A Round Of Applause Semantic Release For The Clapper Component --- ...applause-semantic-release-for-the-clapper-component.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_drafts/a-round-of-applause-semantic-release-for-the-clapper-component.markdown b/_drafts/a-round-of-applause-semantic-release-for-the-clapper-component.markdown index 66dfde812..7bb77db8a 100644 --- a/_drafts/a-round-of-applause-semantic-release-for-the-clapper-component.markdown +++ b/_drafts/a-round-of-applause-semantic-release-for-the-clapper-component.markdown @@ -53,7 +53,7 @@ It's worth going into a little more detail on each of these steps. ### 🔍 Analyze Commits -[Commit Analyzer plugin][commit-analyzer-plugin] uses [Angular commit message conventions](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit) by default to determine whether a release is major (breaking changes), minor (new feature) or patch (bug fixes); other commit message formats are available. Under the bonnet, the plugin uses [conventional-changelog][conventional-changelog]. +[Commit Analyzer plugin][commit-analyzer-plugin] uses [Angular commit message conventions](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit) by default to determine whether a release is major (breaking changes), minor (new features) or patch (fixes); other commit message formats are available. Under the bonnet, the plugin uses [conventional-changelog][conventional-changelog]. It's important to note that neither `docs` nor `chore` commit types trigger a release by default, and I chose to deviate from that by including `docs` changes in patch releases, otherwise our npm package README could become out of sync with the README in GitHub.