Component library updates
How we’ll track new components, token changes, and breaking notes as @granicus/gds-core grows.
As @granicus/gds-core grows, product teams need a simple way to see what
changed - without digging through every PR. This News stream is where we will
call out library updates that affect consumers.
What you can expect here
| Kind of update | What we’ll say |
|---|---|
| New components | Name, when-to-use, links to docs + Storybook |
| Token / theme changes | What shifted in color, type, space, or elevation |
| Behavior changes | Props, defaults, or accessibility fixes |
| Breaking changes | What breaks, why, and how to migrate |
Day-to-day API detail still lives on each component page and in Storybook. The package Changelog is the version-by-version history from Changesets. News is the narrative signal - short, scannable, dated context when teams need more than a bullet list.
How to stay current
- Check Changelog for what changed in each version
- Read News when planning a larger upgrade
- Skim Foundations if tokens moved
- Open the affected component doc for examples and props
- Validate in Storybook before promoting to a product branch
For EHQ and other multi-app teams
If you maintain several frontends (for example Admin UI, Blue Haven, and Bazaar), treat these posts as the shared upgrade brief. One note here should be enough to decide which apps need a bump this sprint.