lamintra/ui

Changelog

The CLI and the registry have separate version numbers, which confuses people until it is written down. So here it is written down.

Two version lines

The CLI is the jar you download. The registry is the repository of component sources it reads from. They ship separately, because a fix to a component should not require a new jar and a fix to the installer should not require re-tagging every component.

They are connected at exactly one point: each CLI release is pinned to one registry tag. Today v0.5.0 installs from registry v0.5.2, and it will keep installing from v0.5.2 forever, because the pin is a tag rather than a branch.

The practical consequence: the registry version moving does not change what you get. Upgrading the jar is what changes it, which also means a component you installed last month cannot be altered by anything happening upstream this month.

Upgrading is the same two commands as a first install: replace the jar, and re-run add for anything you want moved to the new version.

CLI releases

Each line is the release tag's own summary, not a rewrite of it. Full notes and the downloadable jar are on the releases page.

  1. v0.5.0

    current

    Wave 1: flat slugs, new base-tier language, retire the neon fixtures

  2. v0.4.0

    Ship the rename: registry v0.4.0, CLI v0.4.0

  3. v0.3.3

    Fix 11 token deviations; release CLI 0.3.3 against registry v0.3.2

  4. v0.3.2

    Window insets for bottom sheet; harden installer against path traversal

  5. v0.3.1

    Preview-on-install

  6. v0.3.0

    init auto-detection, and an add idempotency guard

  7. v0.2.1

    Fix bottom sheet drag-to-dismiss

  8. v0.2.0

    Add the button and neon-outline components

  9. v0.1.0

    Initial public release

Things that were removed

Recorded rather than quietly dropped, because a name that used to work and now 404s is worse than one that never existed.

  • neon-button and neon-outline-button, retired in v0.5.0. They were built in a design language this project later rejected, and were named after the exact aesthetic the product brief lists as its anti-reference. Asking for either now fails with a readable error rather than a stack trace.
  • bottomsheet became glass-sheet during the rename in v0.4.0.
  • glass-sheet itself was retired from the registry on 2026-08-11, for the same reason the neon components were: it did not hold to the design language the rest of the set follows. It had been off this site since 2026-08-09 while still being installable, which is the wrong way round. Retiring it takes the registry to six, which is what the site has been showing all along.
  • Because the CLI pins a registry tag, removing a component from the registry does not reach anyone already holding a jar. Existing copies of v0.5.0 keep installing from v0.5.2, which still contains it. That is the same guarantee described above working in the awkward direction, and it is the honest description of what "retired" means here: no new registry tag carries it, and the next CLI release will not reach it.