Browse docs

Releases

This is the chronological release history of @dashforge/tw. Every entry links to a full page with the detail of that release.

The authoritative source is the per-package CHANGELOG.md in the monorepo, with cross-cutting context in the top-level CHANGELOG.md. These pages are a reader-friendly projection of them — when in doubt, the CHANGELOG.md wins.

Versioning model

@dashforge/tw is pre-1.0 and follows Semantic Versioning with -alpha / -beta / -rc pre-release tags. Until 1.0.0:

A minor bump (e.g. 0.1.x → 0.2.0) is additive — new components, new variants, no breaking changes to the existing public API. Adopt incrementally; existing code keeps working unchanged.
A patch / pre-release tag bump (e.g. 0.2.0-beta → 0.2.1-beta) is non-breaking — bug fixes, internal refactors, doc updates.

Independent versioning by design (per architectural plan v2): @dashforge/tw, @dashforge/tw-theme, and @dashforge/tw-tokens version separately. A component-package bump doesn't force a token / theme upgrade, and vice versa. The MUI side ecosystem (@dashforge/ui, @dashforge/theme-mui, …) lives on its own versioning track (0.2.x-beta at the time of writing) and is unrelated to TW releases.

Timeline

Version	Date	Theme
`0.2.0-beta`	`2026-05-17`	Foundation release — 8 layout primitives (Typography, Box, Stack, Grid, Container, Divider, AspectRatio, VisuallyHidden) + 132 edge case tests.
`0.1.0-beta`	`2026-05-16`	First public beta — 16 components across forms (10), layout (4), and providers (2).

How to read a release page

Each release page records:

Theme — the one-line "why this release exists".
Affected packages — @dashforge/tw is always affected (it's the package whose release this is); companion packages (tw-theme, tw-tokens) and the bridge layer (forms / rbac / ui-core) may also be listed when their version was bumped in the same cycle.
Added / Internal / Architecture / Migration — Keep a Changelog sections (omitted when empty). Internal covers test coverage, build pipeline, and validation work that isn't part of the public API.
Upgrade notes — when there is migration work, a pointer to the exact recipe. For strictly-additive releases, the section says so.

Companion packages

For releases of the TW companion packages, see their per-package changelogs in the monorepo:

Both companions are at 0.1.0-beta and unchanged since first publish — their changelogs are still single-entry. When they bump, they'll appear in the table above with their own row.