Free component catalogue complete
Carousel, Data Table, Direction, Resizable, Scroll Area, Table, and Sonner complete all 57 public component categories.
Public release record
Built in dependency order.
Dates, behavior changes, registry additions, and verification evidence are recorded with the source. Counts come from the catalogue manifest.
Composite inputs
Calendar, Combobox, Command, Date Picker, Input Group, Input OTP, and Select.
Navigation systems
Context Menu, Menubar, Navigation Menu, and Sidebar.
Overlay family
Alert Dialog, Drawer, Hover Card, Popover, Sheet, and Tooltip.
Selection controls
Button Group, Slider, Toggle, and Toggle Group.
Navigation and disclosure
Accordion, Breadcrumb, Collapsible, and Pagination.
Display and feedback
Alert, Avatar, Empty, Item, and Progress.
Layout and feedback
Separator, Typography, Kbd, Spinner, Skeleton, and Aspect Ratio.
Form foundations
Label, Field, Textarea, Checkbox, Radio Group, and Native Select.
Source record
The repository-level docs/changelog.md is the detailed canonical release log. Subscribe to the public changelog RSS feed for version summaries.
How to read a release entry
Each entry describes public work that exists in the tagged repository, not a roadmap promise. Catalogue counts come from the same typed data used to generate component pages and registry payloads. A component addition names the source that became available; a behavior change records what consumers may need to recheck; documentation and verification entries identify supporting work without presenting it as a new product feature.
Gummy UI distributes editable source rather than a versioned runtime package, so teams remain in control of the copy installed in their own repository. Before taking an update, review the diff, compare any dependency or anatomy changes, and rerun the consuming product’s type, interaction, accessibility, visual, and browser checks. Existing MIT source does not silently change when a later registry version is published.
Public and Pro records stay separate
This page covers the open component system and public product foundation. A future paid release requires its own versioned archive, checksum, licence, protected-download evidence, and entitlement record. An implemented Pro status is therefore not listed here as a customer release, and no changelog entry should be read as proof that checkout or a protected download is available.