$mol is delivered continuously. Instead of cutting numbered versions, the framework ships straight from the mam_mol monorepo — every merged change is immediately available to anyone building against it. The MAM build tool always pulls the current sources, so there is no upgrade step and no version matrix to reconcile.
Commit history — the mam_mol commits are the canonical changelog.Per-module history — each component folder on GitHub carries its own commit log, so you can watch just the parts you use.DEV community — notable additions and write-ups are shared under the #mol tag.
Because there are no breaking release boundaries, the framework favours backward-compatible evolution: components gain features without renaming, and the typed view.tree interfaces make incompatibilities surface at compile time rather than at runtime. If a build stops compiling after an update, the TypeScript errors point you straight at what changed.Edit this page on GitHubWas this helpful?YesNoPreviousTeamNext$mol_button_majorOn this pageFollowing changesWhat this means in practiceType to search the documentation.
