Changelog

What shipped and what it changed for the systems you author. Milda is in closed alpha, so this is a record of capability rather than a semver history - the packages you generate carry their own versions, derived from their contracts.

#August 2026

#The Mac app

A native AppKit editor renders the same document through a third target - not a web view. The canvas resolves the IR to native primitives and records what it cannot express rather than approximating it, which is the strongest test so far that the format is genuinely platform-neutral.

#The Foundations editor, per token type

Every token type now has an editor built around what that type actually is: a radius is shown on a box you choose, spacing in a role (row gap, stack gap, inset), a duration as frames you can replay, an elevation as a light direction. Sixteen types, each answering the question that type raises rather than showing a number field.

• Multi-select and bulk operations across tokens.
• Table and flow views beside the tree.
• Exceptions and the layer chain are visible where you edit.

#Storybook for the editor's own components

Internal, but it is why the editor's controls now behave consistently.

#July 2026

#The .milda file carries the whole system

Export and re-import round-trips a complete document - foundations, components, examples, docs and the written contract - and the round trip is a tested fixed point over a real corpus. The surface version moved to 0.4.

#Typed lengths and first-class values

A length says what it means rather than carrying a CSS unit: 12px is density-independent, scaled(0.75)follows the user's text size, and pillis the intent "fully rounded" rather than a large number. Colours are space-aware functions -hex(), oklch(), p3() - instead of quoted strings, and a computed colour prints as the relationship it is.

#Release lines and snapshots

A release stores the document it was built from, content-addressed and immutable, so the past stays reproducible.

#The CLI and the MCP server

milda pulls a published system from the command line, and the MCP server exposes it to AI coding agents. See The CLI and Milda & AI.

#Editor support

A language server, a VS Code extension and a JetBrains plugin, all reusing the same parser the compiler uses - so completion and diagnostics cannot drift from the language.

#June 2026

#Figma as a design target

Foundations export as Figma Variables and DTCG tokens, and components as component sets. The plugin is a persistent bridge rather than a one-way dump - Milda stays the source of truth.

#Icon provenance

An icon records where it came from - an uploaded asset or a named set - and the generator emits it accordingly, with no CDN fallback anywhere in the output.

#Documentation as part of the system

A design system carries its own docs, published per tenant at *.milda.page.

#Before that

The editor, the IR, the React generator, the registry and the release pipeline - the wedge that makes the rest possible. Thinking in Milda is the shortest route to what those are.