Shipping a major version of a widely used library is less about the code changes and more about managing uncertainty for downstream teams. The monday.com team shares lessons from releasing Vibe 3, their design system used across hundreds of microfrontends. Key insights: breaking changes accumulate when you follow semver
Table of contents
When a Backlog Stops Being a BacklogWhen a Major is Necessary, But Not EnoughThe Wrong Assumption We Made EarlyCodemods Removed the Mechanical FearMaking Decisions ExplicitThe Cases Codemods Couldn’t HandleFrom Shipping a Version to Shipping a System1 Comment
Sort: