Managing dependency chains about bit

[itaymendel]

semver rules are semantic. always think about theh apis you expose to the outside.
in this example, C changed an API, later B adopted that change without a need to change its API, so for A there is no change in B's API layer.
so B is not a breaking change

in a sense, B created a barrier around C's changes, as the change only impacts B and not A (or other dependents).

this is why if you use components to also manage data-fetching and entities in your system, you can ensure you build laters that protect from breaking changes by adopting to them.