Repository navigation
v0.1.0-alpha.9
Pre-releaseA small release with an unusual property for this package: nothing renders differently.
Added
--token-fontSizeXXL (1.5rem), the step above XL in the size ladder (#13). The ladder had XXS but nothing above XL, so a component with a large numeric readout had no token to reach for and took a heading token instead. Both products that define this name already declare 1.5rem. Token contract goes from 115 names to 116.
styles/tokenContract.test.ts. CONTRIBUTING has always said that a token a component reads must be declared in styles/base.css, because one declared only in a product's theme file makes the component render correctly there and nowhere else. Nothing enforced it. The rule holds today at zero violations, so this pins it as a ratchet rather than fixing anything.
Fixed
StatCard sizes its value from the numeric ladder, not from a heading token (#13). .stat-card__value read --token-fontSizeHeading2, so the number followed whatever heading ladder the consuming product had chosen. A stat value is a numeric display rather than a heading, and the two are decisions about different things: one is about data, the other about prose.
A consumer shipping the Ant Design v5 heading scale rendered the value at 30px where this package intends 24px, with no way to correct it that did not also move every heading in the product. That consumer had been carrying its own copy of the component because of it.
The two --emphasis variants still read heading tokens. Settling a numeric ladder above XXL needs agreement no consuming product has reached, and inventing one here would be a token contract nobody asked for.
Before you upgrade
Nothing changes visually. Every consumer that exists resolves both --token-fontSizeHeading2 and --token-fontSizeXXL to 1.5rem: this package's own default declared the heading token at 1.5rem, and both consuming products declare --token-fontSizeXXL at 1.5rem in their own theme files. The two names were equal only by coincidence, which is why the change was worth making, but the coincidence holds for everyone upgrading into this release.
A minor under the versioning policy, for the new token.
Full changelog: v0.1.0-alpha.8...v0.1.0-alpha.9