docs: warn about BREAKING CHANGES

Author: knocte

CHANGELOG.md

@@ -3,6 +3,13 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [22.0.0](https://github.com/conventional-changelog/commitlint/compare/v20.5.2...v22.0.0) (2026-04-30)
+
+### BREAKING CHANGES
+
+* When using commitlint in --verbose mode, commit message will be shown after a new line (EOL), instead of after a colon like in older versions. To restore the old behaviour, use the flag `--legacy-output`.
+
+
 ## [20.5.2](https://github.com/conventional-changelog/commitlint/compare/v20.5.1...v20.5.2) (2026-04-25)
 
 

docs/guides/local-setup.md

@@ -291,4 +291,7 @@ No staged files match any of provided globs.
 # husky > commit-msg
 ```
 
+Since [v22.0.0](https://github.com/conventional-changelog/commitlint/releases/tag/v22.0.0) `commitlint` will output the commit message after a new line (EOL) instead of after a colon.\
+(You can use the `--legacy-output` flag to get the previous output format used in older versions)
+
 Local linting is fine for fast feedback but can easily be tinkered with. To ensure all commits are linted you'll want to check commits on an automated CI Server too. Learn how to in the [CI Setup guide](/guides/ci-setup).