I'm using Conventional Commits and need to know how to properly signal a 'BREAKING CHANGE' in my commit messages, both in the commit footer and in the type/scope prefix. Additionally, what are two tools from the 'About' section that can help automate release-related tasks based on this specification?
Navigate to the 'Full Specification' section. Identify the method for indicating 'BREAKING CHANGE' in the commit footer. Identify the method for indicating 'BREAKING CHANGE' in the type/scope prefix. Navigate to the 'About' section. Identify two tools listed that automate release-related tasks (e.g., changelog generation, version bumping, release lifecycle automation). State the methods for indicating breaking changes and the names of the two tools.
State that 'BREAKING CHANGE' in the footer requires the uppercase text 'BREAKING CHANGE:' followed by a description. State that 'BREAKING CHANGE' in the type/scope prefix requires a '!' immediately before the ':'. List two distinct tools from the 'About' section that are related to release automation (e.g., 'conventional-changelog', 'bumped', 'unleash', 'chglog', 'fastlane-plugin', 'commitizen-tools/commitizen').