I wrote a guide to how we use Semantic Versioning at Optimizely to manage our UI library.
Here’s part of the introduction:
We’ve created an interpretation of the Semantic Versioning rules at Optimizely that both adheres to the scheme, and helps mitigate the risk of incorrectly categorizing changes. Now we have guidelines to confidently and consistently determine the severity of a change that modifies the user interface. The process also introduces a new risk: breaking changes miscategorized and released as non-breaking have the potential to break Sass compilation or introduce UI bugs.
Read the entire post on the Design @ Optimizely publication.