Versions and stability
Mlola follows semantic versioning from 1.0. A minor or patch release never asks you to change your code; a breaking change waits for a major version and arrives with the steps to take. This page says exactly what that covers.
- 1.1.4all 8 packages release together
- >=18a peer of the React packages only
- >=20the CSS and behavior need no Node at run time
- 0each with the version that removes it
What only a major version changes
- The element contract. The 92
ml-*element classes and their 154data-*attributes and values, as listed in the generated contract your coding agent reads. Markup that renders today renders the same way after an update. - Token names. Every
--ml-*custom property you read or set. - Component APIs. Exported names and props of every component, free and Pro, and the state words they share.
- Package entry points. The 39 entry points across
@mlola-ui/engine,@mlola-ui/tokens,@mlola-ui/behavior,@mlola-ui/motion,@mlola-ui/scene,@mlola-ui/icons,@mlola-ui/registry,mlola-ui. - Tooling. CLI commands and flags,
mlola.config.json(its schema), MCP tool names, and the theme spec inmlola.theme.json, so a theme you made keeps working.
What any release can change
- Computed values. Colors are derived, not stored. When the solver improves, a shade can move in a patch release; a guaranteed contrast pairing never drops below its target, and the test that checks it runs on every change.
- Refinements inside a recipe. A shadow, a transition or the spacing inside a component, as long as it stays within the tokens and the contract.
- Internals. Helpers under
_internal/and any file a package does not export.
How a name is retired
A renamed class, token or prop keeps its old name as an alias with a removal version, recorded in one ledger. The build fails if an alias outlives its version, so nothing stays deprecated forever. Each removal is listed in the changelog with what to use instead.
Nothing is deprecated in 1.1.4: 1.0 removed every alias the 0.x releases carried.
Updates and the code you own
- The packages (the engine stylesheet, behavior, motion, icons) update with your package manager, within the range in your
package.json. - Components the CLI copied are your source. An update never rewrites them:
npx mlola-ui addrefuses to replace a file that differs from what it would write,--overwritetakes the new version, andnpx mlola-ui doctorlists the files that differ. - A Mlola Pro license includes every update for as long as Mlola Pro is offered, and it is perpetual: you keep every version you installed. See the license.
Supported platforms
React >=18 for the React components, Node.js >=20 for the CLI, and the current stable Chromium, Firefox and Safari, on desktop and mobile. Every change runs the rendering, keyboard and framework-free suites in all three engines. A version that drops support for any of these is a major version.
Every release is in the changelog.