If I change a Sanity component's fields, does it break the mapped Croct slot?

We iterate on our Sanity component schemas fairly often, adding and renaming fields as the design evolves. My worry is that editing a component's fields silently breaks the Croct slot it is mapped to, and we only find out in production.

How does versioning handle that kind of schema drift?