Browse docs
Browse docs
This is the chronological release history of the @dashforge/* packages.
Every entry links to a full page with the detail of that release.
Dashforge is stable at 2.0.1 and follows
Semantic Versioning:
1.x → 2.0.0) signals a breaking change to
the public API — check that release's page and
MIGRATION.md.1.0.x → 1.1.0) is additive — new
features, no breaking changes.1.0.0 → 1.0.1) is non-breaking — bug
fixes, internal refactors, doc updates.The 1.0.0 cut bumped all eleven workspace packages in lockstep. Between
1.1.0 and 1.3.0 they versioned independently, so a component bump
did not force a token or theme upgrade.
2.0.0 returns to lockstep, and this time it is enforced. Internal
dependencies are declared with workspace:*, which pnpm rewrites at pack
time to the EXACT sibling version rather than a range, so every
@dashforge/* package ships on one version and has to be installed on
one version. A mixed 1.x / 2.0.0 install does not resolve. The TW
side (@dashforge/tw, @dashforge/tw-theme, @dashforge/tw-tokens) is
on the same version line from 2.0.0, so its
releases page covers the same cut from the
Tailwind angle.
| Version | Date | Theme |
|---|---|---|
2.0.1 | 2026-09-29 | Current stable. Lockstep patch. @dashforge/ui-core and @dashforge/rbac shipped 2.0.0 without their declaration payload: TS2307 on every symbol, or a silent degrade to any with skipLibCheck: true. Runtime was never affected. |
2.0.0 | 2026-09-28 | First major. Multi-select finally has a runtime: <Autocomplete multiple> and <Select multiple> carry a parallel pipeline for the array case. Adds <CheckboxGroup>. One breaking change, type-level only: value and onChange widened to describe both modes, so a narrow single-select handler no longer type-checks. All eleven packages move together and must be upgraded together. |
1.3.0 | 2026-08-15 | Label-help tooltip on all form inputs. A ⓘ in the label row (string shorthand or config) with a built-in default icon and position before/after. The MUI twin of the TW tooltip prop. Only @dashforge/ui advances. No breaking changes. |
1.2.0 | 2026-08-14 | <Video> primitive. The moving-image twin of <Image> — a native <video> wrapper with anti-CLS aspect-lock, poster + loading skeleton, graceful error fallback, controls by default; supports access + visibleWhen gating. Only @dashforge/ui advances. No breaking changes. |
1.1.0 | 2026-08-14 | <Image> + gating-aware layout primitives. New <Image> (MUI twin of the TW one) and <Box> / <Stack> / <Grid> overrides of the MUI layout primitives — every native prop forwarded, each adding access (RBAC) + visibleWhen. Only @dashforge/ui advances (first independent minor). No breaking changes. |
1.0.0 | 2026-05-23 | Stable release — first semver-stable version. Public API frozen, semver guaranteed. All eleven workspace packages bumped to 1.0.0 in lockstep. The page summarises the pre-1.0 history (0.2.2 → 0.4.0 beta releases) not listed below. |
0.2.1-beta | 2026-05-14 | Bug fixes — DashForm resolver passthrough + DashFormProvider SSR-safe useForm(). Schema validation and useDashFieldArray-under-SSG both work. |
0.2.0-beta | 2026-05-14 | Public-API freeze — DashFormBridge interface tightened, deprecated fields removed, @internal markers, first MIGRATION.md. |
0.1.9-alpha | 2026-05-13 | Test coverage + docs polish — 8 new unit tests, JSDoc hook decision tree. Zero functional changes. |
0.1.8-alpha | 2026-05-13 | Packaging cleanup — per-package CHANGELOG.md in every npm tarball, stale dev warning corrected. |
0.1.7-alpha | 2026-05-11 | MUI v9 compatibility — migration to slotProps, four React deprecation warnings eliminated. |
0.1.6-alpha | 2026-05-10 | Performance + correctness — per-field subscriptions, useDashFieldMeta, hook-rules fixes, auto-reset policy. |
Each release page records:
Throughout the rest of the docs you will see inline badges like Added in 0.1.6-alpha or Changed in 0.2.0-beta — each links straight back to the release that introduced or changed that specific feature.