[FEAT]: Updater to be Conventional Commits Compliant #80

New issue

Closed

opened 2026-04-22 23:38:34 +00:00 by imAsparky · 0 comments

imAsparky commented

2026-04-22 23:38:34 +00:00

Owner

Before you submit

I have searched existing issues and this has not already been requested

Problem Statement

The updater follows the older standard, and doesnt handle BREAKING as it should.

Proposed Solution

Update the regex to handle the many options no available for BREAKING

Alternatives Considered

No response

Additional Context

No response

### Before you submit - [x] I have searched existing issues and this has not already been requested ### Problem Statement The updater follows the older standard, and doesnt handle `BREAKING` as it should. ### Proposed Solution Update the regex to handle the many options no available for `BREAKING` ### Alternatives Considered _No response_ ### Additional Context _No response_

imAsparky referenced this issue from a commit

2026-04-23 22:46:31 +00:00

docs(all): Add/Update usage patterns for new features #80

imAsparky referenced this issue from a commit

2026-04-23 22:46:31 +00:00

test(changelog): Add/Update for new parser features #80

imAsparky referenced this issue from a commit

2026-04-23 22:46:31 +00:00

feat(parser): Add latest Conventional Commits patterns #80

imAsparky referenced this issue from a pull request that will close it,

2026-04-23 22:47:34 +00:00

feat(parser): Add latest Conventional Commits patterns #80 #81