Create and use libraries

Publish the UI library update with the new badge component and version notes, then push the library to the mobile and web files and notify the design and frontend squads. Ensure the token map for color and spacing is synchronized before publishing, confirm no breaking renames, and ask engineers to pull before their sprint demo on Tuesday.

Before I publish the library, make it easy for engineers and mobile designers to accept the update. Show the diff for token changes, surface components that will change visually on mobile breakpoints, and flag any renames that require code changes. Provide a short upgrade note that tells engineers exactly which tokens to import and what known regressions to watch for.

I just published a library update that renamed a spacing token and Android CI started failing. I can’t see the build logs from here. What is the most likely mismatch between our tokens and the codebase, what immediate message should I send to the Android lead to buy time, and what’s the fastest rollback or patch I can make in the library to unblock builds?

Each library publish seems to create platform build failures or duplicated tokens and engineers complain they can’t rely on our releases. Are we failing on semantic token contracts, release communication, or on automation that should catch breaking changes? Recommend one change to publishing discipline, one automation check, and one cross-team habit to restore trust over the next two releases.