Releases | Dashforge Docs

Browse docs

Releases

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

The authoritative source is the top-level CHANGELOG.md in the monorepo. These pages are a reader-friendly projection of it — when in doubt, the CHANGELOG.md wins.

Versioning model

Dashforge is stable at 1.0.0 and follows Semantic Versioning:

A major bump (e.g. 1.x → 2.0.0) signals a breaking change to the public API — check that release's page and MIGRATION.md.

A minor bump (e.g. 1.0.x → 1.1.0) is additive — new features, no breaking changes.

A patch bump (e.g. 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. From 1.1.0 onward, packages version independently — a component bump no longer forces a token / theme upgrade, and vice versa. The TW side ecosystem (@dashforge/tw, @dashforge/tw-theme, @dashforge/tw-tokens) also released 1.0.0 in the same cycle and tracks its own version line — see the TW releases page.

Timeline

Version	Date	Theme
`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.

How to read a release page

Each release page records:

Theme — the one-line "why this release exists".

Affected packages — which of the seven packages actually changed.

Breaking / Changed / Added / Fixed — the concrete deltas.

Upgrade notes — when there is migration work, a pointer to the exact recipe.

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.