Versioning policy

Predictable updates without silent contract breakage.

FG UI uses MAJOR.MINOR.PATCH versioning. Stable archives are immutable, and the version number communicates whether an update is a compatible fix, additive feature release or breaking change.

CURRENT STABLE

1.2.0

457 component families, including 64 additive 1.2 families, with the 393-family 1.1 contract preserved in full.

PREVIOUS STABLE

1.1.0

The immutable 393-family compatibility baseline. Published Stable archives remain unchanged after release.

See the 1.2 additions →

Built with FG UI itself.

This page is built entirely with FG UI using the same components, layout primitives, icons and interactions available in the kit. No Bootstrap, Tailwind or external UI framework is required.

PATCH

1.1.0 → 1.1.1

Backwards-compatible bug, accessibility, browser, responsive, documentation, packaging and performance fixes. No new public component families or API methods.

MINOR

1.1.x → 1.2.0

Backwards-compatible new component families, public API methods/options and other substantial additive capabilities.

MAJOR

1.x → 2.0.0

Removal or rename of a public contract, incompatible behaviour changes or architecture changes that require normal consumers to rewrite supported markup or code.

Pre-releases

Alpha, beta and RC identifiers are not stable releases. RC builds are feature-frozen except for release-blocking defects.

Deprecation

Prefer a documented compatibility path before removing a public contract. Deprecation notes identify the replacement and intended removal release.

Release immutability

Published stable archives are immutable. Fixes create a new version rather than silently replacing an existing stable archive.

Current stable contract

FG UI 1.1.0 preserves the 1.0.2 public contract and adds backwards-compatible 1.1 component families. Breaking public-contract changes require a major release.