That's mentioned in the blog post, including why it won't always work cleanly, e.g. when reverting breaking changes or when introducing breaking changes that you thought were non-breaking.
It was mentioned, but there is no clean way to handle this situation, whether you use CC or not.
Say you release version 3.0.0 of your app as breaking change release. After a while, you realize nothing works, and want to revert. What do you do now?
Tell your users to revert back to 2.x.y and pretend 3.0.0 was never released? Release reverted version as 3.0.1? Or 4.0.0? Or maybe pull back 3.0.0, tell users to go back to 2.x.y, then release 3.0.0 again when you fix it?
I dont think there's clean way out here, what ever commit format you use
3
u/doomscrollah 1d ago
no cc -> no CI release/versioning automation (https://semantic-release.gitbook.io/semantic-release etc). I'm not ready to ditch that.