Skip to content

Conversation

schilkp
Copy link

@schilkp schilkp commented Sep 25, 2025

Description

A plugin I was using had a breaking change. I updated and adjusted my config as required. Some time later, the plugin reverted this commit again. I missed that when updating again because for said plugin the author is usually diligent about using conventional-commits for indicating breaking changes, so I did not read the changes too closely when I saw no breaking changes highlighted.

This updates the breaking-change detection regex to detect both commits of the form feat!: ... and Revert "feat!: ...

Related Issue(s)

None that I am aware of.

Screenshots

Without this change:
image

With this change:
image

@schilkp schilkp force-pushed the schilkp/revert_breaking branch from d1b85ab to 62d9512 Compare September 25, 2025 13:22
@schilkp schilkp changed the title feat: Highlight reverted breaking changes as a breaking change. feat(ui): Highlight reverted breaking changes as a breaking change. Sep 25, 2025
@schilkp schilkp force-pushed the schilkp/revert_breaking branch from 62d9512 to 0efac74 Compare September 25, 2025 13:23
@schilkp schilkp changed the title feat(ui): Highlight reverted breaking changes as a breaking change. feat(ui): highlight reverted breaking changes as a breaking change. Sep 25, 2025
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.

1 participant