GuidesLumos 1.0.0New
What changed in v1.0.0
A stable component API and native text trimming in Lumos v1.0.0.
Lumos v1.0.0 was released October 16, 2026. It makes the component API stable and simplifies how headings and paragraphs are trimmed.
Stable component API
The component names, paths and public props in this release are the contract for Lumos 1.x. A future change that breaks that contract requires a new major version. Fixes and additions that preserve it can ship in minor and patch releases.
Native text trimming
Headings, paragraphs and text-style classes now use text-box: trim-both cap alphabetic. The browser reads the font's own cap height and alphabetic baseline, so Lumos no longer needs generated ::before and ::after boxes or per-font trim values.
- Removed
--primary-trim-topand--primary-trim-bottom. - Removed every
--*-trim-topand--*-trim-bottomtext-style token. - Removed the private
--_trim-topand--_trim-bottomvariables. - Text elements can now become flex or grid containers without generated trim boxes turning into layout items.
Dependency updates
A repository-only updater checks Astro and its integrations each day, verifies the starter, and opens a pull request when something changes. Passing non-breaking updates merge automatically; major updates wait for review. create-lumos reads the current template requirements before it writes a project, so a future minimum change produces a clear error instead of an incomplete site.
Before upgrading
- Remove project overrides for the deleted trim tokens.
- Update custom CSS that expected the old generated trim pseudo-elements.
- Review the visual diff around headings and paragraphs; native font metrics can change their visible spacing.