Versioning & migration
Lumora uses Changesets and semantic versioning. The lm-* class contract and theme tokens are public API — breaking changes only happen on majors.
Versioning policy
Every package follows semver. We treat these as the public surface area:
- CSS classes: every
lm-*class shipped by the core plugin. - Theme tokens: the names and types in
requiredThemeTokens. - Adapter props: typed React and Vue component props.
- Plugin options: the API of
@plugin "@lumora-design/core".
Bug fixes, docs updates, non-breaking style corrections.
New components, new themes, additive props or classes.
Breaking class, token, or adapter changes — with migration notes.
Upgrading
Upgrade all Lumora packages together — they share the same class contract and adapter types track core releases.
pnpm up @lumora-design/core@latest @lumora-design/themes@latest \
@lumora-design/react@latest @lumora-design/vue@latestAlways pin same minor version
@lumora-design/core, @lumora-design/themes, @lumora-design/react, and @lumora-design/vue should match minors. Mixing minor versions across these packages can produce missing classes.1.0 stability promise
1.0 freezes the public surface. The lm-* class contract, the theme token names, and the React + Vue adapter prop shapes will not break before 2.0. Additive changes (new components, new themes, new optional props) ship as minors.
- Stable: 65 components, 39 themes, both adapters, all current props.
- Additive only on minors: new components, new themes, new optional props, new utility classes.
- Reserved for majors: renaming classes, renaming tokens, removing props, changing default behavior, raising minimum browser support.
Release log
Initial public release
- 65 components across 11 categories with the stable lm-* class contract
- 39 themes (light / dark / graphite / aurora / nord / solarized and more), each WCAG-AA verified
- Stable React (@lumora-design/react) and Vue (@lumora-design/vue) adapters
- 6 multi-page enterprise templates with 70+ preview routes
- Documentation site with searchable catalog, framework code tabs, CSS class tables, props tables, accessibility notes, and sticky TOC
- Visual regression suite + cross-template a11y audit (axe-core)
Deprecation policy
- Deprecated APIs are kept for at least one minor version after the deprecation announcement.
- Deprecation warnings appear in the dev-time TypeScript output and in the changelog.
- Major releases include a codemod where automation is feasible.
- We give a 4-week heads-up on majors via the GitHub release notes.