Releases are how new tokens and patterns reach teams. A release process makes sure updates are clear, consistent, and trusted. Each release should follow the way you have defined for your system, scaling from a light touch to a full walkthrough or workshop depending on impact. Use this when rolling out new work or updating existing patterns.
How to
-
Plan the release Define what is changing, who is impacted, and whether it is a patch, minor, or major update. Choose if it should be piloted or pushed system-wide.
-
Choose the right channel Match communication to the size of the update. Small changes may only need a light message update in your Systems channel, larger ones may need a changelog, walkthrough, or workshop.
-
Communicate clearly Explain what changed, why it matters, and whether migration is needed.
-
Support migration and retirement Reference Migration Guides to give teams a clear path from old to new, and link to Retire and Replace where older work is being phased out.
-
Update guidance Make sure your Guidance Setup reflects the new release though updating or Creating Guidance Pages.
-
Collect feedback Capture issues and questions to improve both releases and your framework.