Description

I've just received a patch bump on a CI commit, when neither the preceding nor succeeding CI commit resulted in a bump at all.

This is possibly the same cause as #695, as the auto-generated messages from dependabot includes "matching" messages in some cases in the body.

Steps to reproduce

1. Have a .cz.toml file:

   [tool.commitizen]
   name = "cz_conventional_commits"
   tag_format = "v$version"
   version_scheme = "semver2"
   version_provider = "scm"
   annotated_tag = true
   breaking_change_exclamation_in_title = true

2. Have a series of the following commit messages:
   • before_non_bump.md
   • bump.md
   • after_non_bump.md
3. Run cz --no-raise 21 bump --get-next, and observe that it outputs a version bump

(I'm sorry, this is a private repo, so I can't point you at a repo itself)

Current behavior

It unexpectedly issued a new bump version.

If a changelog is generated, eg with cz changelog v<new version> --file-name <some file name>, it outputs a changelog without a list of changes:

## v0.2.1 (2026年01月05日)

Desired behavior

No version bump

Screenshots

No response

Environment

Commitizen Version: 4.11.0
Python Version: 3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0]
Operating System: Linux