I'm learning about Conventional Commits. How do I correctly indicate a 'BREAKING CHANGE' in both the commit message footer and the type/scope prefix? Also, can you recommend two tools from this website that help automate release-related tasks like changelog generation or version bumping?
Navigate to the 'Full Specification' section. Identify the precise syntax for a 'BREAKING CHANGE' in the commit footer. Identify the precise syntax for a 'BREAKING CHANGE' in the type/scope prefix. Navigate to the 'About' section. Identify two distinct tools that automate release-related tasks (e.g., changelog generation, version bumping, release lifecycle automation). State the identified formatting rules for 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 (e.g., 'BREAKING CHANGE: environment variables now take precedence over config files'). State that 'BREAKING CHANGE' in the type/scope prefix requires a '!' immediately before the ':' (e.g., 'feat!: description'). List two distinct tools from the 'About' section that are related to release automation (e.g., 'conventional-changelog', 'bumped', 'unleash', 'chglog', 'commitizen-tools/commitizen', 'fastlane-plugin').