Publish and update libraries

Publish the updated component library to the team space and notify Sam in product and Leila in engineering that the library is ready for pull. Before you publish, open the design file, run the instance checker, and confirm there are no detached instances or missing tokens. Publish only the components tag that changes and attach a short changelog of what broke and what to migrate. Deadline Friday 5pm.

Before I publish the team library, make it easier for engineers to adopt: surface the breaking token changes at the top, mark renamed components with the old name, and list migration steps for primary button and card variants. Flag any instances that will lose properties and suggest a safe fallback. Keep the changelog to five bullet points.

I renamed button/primary to button/cta and adjusted spacing tokens; Sam and Leila say builds broke and can’t find styles. Diagnose the most likely cause and give the fastest remediation to restore their builds with minimal rework, plus a short message I can send them explaining what I’ll do and when.

Over the past three months every library publish causes at least one engineer to open a ticket about missing styles. Where am I consistently failing — naming, migration notes, or test steps — and what three habits should I adopt so publishes stop breaking builds and engineers stop having to patch instances?