Add CI check to block unwanted major release

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

If a commit message contains BREAKING CHANGE, it published a major version release. If the commit is only describing a breaking change but not actually containing one, this will lead to an unwanted major version release, but major version releases are only scheduled for the beginning of every year and need to be done in a controlled manner with preparatory work involved.

Feature / Enhancement Description

Add check to semantic release to block an unwanted major version increment.

I remember that there is a semantic release plugin to stop major releases, but I haven't found it anymore. Such a plugin would block major releases and needs to be temporarily disabled to publish a major release, which could be an acceptable solution.

Example Use Case

n/a

Alternatives / Workarounds

n/a

No file or test is named; start by locating the semantic-release configuration and existing CI checks. Determine how a BREAKING CHANGE currently triggers a major release, then verify that unwanted major increments are blocked while an intentionally enabled major release remains possible.