Semantic versioning script incorrectly bumps patch instead of minor

[aatmanvaidya]

The custom semantic versioning workflow that we have written broke in the recent release management process. More information about the workflow can be found here - https://tattle.co.in/blog/2025-04-01-feluda-semantic-versioning/. The script parses commits following the Conventional Commits spec and decides whether to apply a major, minor, or patch bump.

In the most recent run of the action - https://github.com/tattle-made/feluda/actions/runs/17910649178/job/50921220727
the following issues occurred:

• Some packages correctly get a minor bump when commit messages use feat: .... BUT other packages, with similar commit messages, only get a patch bump instead of a minor bump.

Expected Behaviour

Any commit with type feat: (and not containing BREAKING CHANGE) should always trigger a minor version bump.

Possible reason for error

We are using git log to check which folder (operator) has received what all commits between the last tag and now. I think some code in parsing of these commits is failing. We have written some detailed automated tests here - https://github.com/aatmanvaidya/feluda-versioning-check/tree/main/automate_testing

[dhairya-pandya]

Greetings, this is Dhairya. I investigated this problem, and I believe that the existing regex for parsing commits is a little too strict, which results in valid feature commits (like feat :) failing to match(due to spaces or some other characters). These features are being released as patches rather than minor versions because the script defaults to a "patch" bump whenever the regex fails.

To handle these edge cases (breaking changes, spacing), I was considering loosening the regex as it strictly wants colon before the feat part and falls back to default as regex fails, so would consider fixing that.

If the maintainers believe this is the best course of action, I'd be happy to submit a PR! @aatmanvaidya