@nathan

I was looking for ways people solved for managing design-dev component version mapping. You touched upon this exact point and concluded with "The scheme should maximize how design assets relate to system code and enable designers and developers to communicate and consider version impacts as they make their product."

In your experience, how did you actually define an scheme for this use case?

If in code buttons is at v2.2.1 which was developed using the design of buttons v2.1.0. How does design system teams maintain the fact that design v2.1.0 lead to dev v2.2.1? or the dev v2.2.1 is based on the design v2.1.0?