In my Lerna monorepo, a commit message including a "BREAKING CHANGE" was applied to all packages, yet only a few received a major version release, while the remainder were updated with a minor version. What could be the reason for this discrepancy?

I am using npm workspaces and use lerna for publishing packages to npm registry.
My Repository - https://github.com/sourcefuse/loopback4-microservice-catalog
I follow conventional commit guidelines
My PR - sourcefuse/loopback4-microservice-catalog#2047
here I have added the BREAKING CHANGE footer as well
based on this all the packages affected here should have a major version release but instead only a few have major version while the rest have minor version release
even though they were a part of the same commit message .

This is the release by lerna - sourcefuse/loopback4-microservice-catalog@3ddb407

I use "lerna version --yes --ci --conventional-commits" and "lerna publish from-package --yes" to version and publish my packages. https://github.com/sourcefuse/loopback4-microservice-catalog/blob/master/.github/workflows/release.yml

• @sourceloop/audit-service@12.0.0
• @sourceloop/authentication-service@17.0.0
• @sourceloop/bpmn-service@12.0.0
• @sourceloop/chat-service@10.0.0
• @sourceloop/feature-toggle-service@0.17.0
• @sourceloop/in-mail-service@10.0.0
• @sourceloop/notification-service@12.0.0
• @sourceloop/oidc-service@0.6.0
• @sourceloop/payment-service@12.0.0
• @sourceloop/reporting-service@0.9.0
• @sourceloop/scheduler-service@11.0.0
• @sourceloop/search-service@0.12.0
• @sourceloop/survey-service@0.7.0
• @sourceloop/task-service@0.8.0
• @sourceloop/user-tenant-service@0.16.0
• @sourceloop/video-conferencing-service@11.0.0