Skip to content

Conversation

@woile
Copy link
Member

@woile woile commented Nov 11, 2025

BREAKING CHANGE, as it will require v4.10 minimum

@woile woile force-pushed the feat/add-more-outputs branch 4 times, most recently from 0302735 to d5efebb Compare November 11, 2025 18:39
BREAKING CHANGE: This update requires commitizen > 4.10 in order to use --minor and --major
@woile woile force-pushed the feat/add-more-outputs branch from d5efebb to 083bb24 Compare November 11, 2025 18:40
Copy link
Member

@Lee-W Lee-W left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are not introducing new features to Commitizen itself; instead, we are focused on improving our CI/CD processes. I think we're good to mark this commit as ci(...) without marking it as a breaking change. WDYT? Adding a request changes for avoiding accidentally bumping

@woile
Copy link
Member Author

woile commented Nov 13, 2025

The thing is, if someone is using the input commitizen_version and it's before 4.10, they won't have the --major flag, meaning that their ci would be broken. I could mark it as ci + breaking

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants