Unreleased
Prepared changes
Changelog
The changelog comes from the repository and is included in the package archive. The Unreleased section lists prepared changes that have not been published yet.
What changed in Gavia UI and what to consider when upgrading. Versions before the rebrand used the previous package name. The history was reconstructed from release Git tags and migration notes. Historical generated Changeset paragraphs are preserved in the maintainer archive.
Prepared changes
Stable 1.0 promotes the RC public API to npm latest. The library API is unchanged from 1.0.0-rc.1; the Playground now translates all changelog prose into Russian. Follow the 1.0 upgrade guide.
WlConfig with wlLocaleRu to keep Russian (localization).iconButton overrides from button (PT mapping).tone and overlay dismissable with dismissible (appearance and dismissal).WlTooltip, register WlTooltipDirective, and provide names for icon actions (Tooltip and names).gavia-ui/utils and Vue helpers through gavia-ui/composables.An opt-in release candidate for npm next; stable latest remains unchanged. Follow the 1.0 upgrade guide.
WlConfig with wlLocaleRu to keep Russian (localization).iconButton overrides from button (PT mapping).tone and overlay dismissable with dismissible (appearance and dismissal).WlTooltip, register WlTooltipDirective, and provide names for icon actions (Tooltip and names).gavia-ui/utils and Vue helpers through gavia-ui/composables.#3c7490; updated hover, active and accent text shades.gavia-dark, themes/gavia-dark.css) with Gavia Sans; the catalog contains five themes.white / graphite, CSS paths, original theme values and catalog positions are preserved.wlDesignThemes expanded from four to five entries; literal labels changed. Use WlDesignTheme / WlThemeName and name rather than fixing the old tuple length or label. Theme migration.This release includes the 0.9 branch changes and corrected browser checks. Version 0.9.0 was not published to npm; upgrade directly from 0.8.1 to 0.9.1.
This release includes the 0.8 branch changes and the nested overlay fix. Version 0.8.0 was not published to npm; upgrade directly from 0.7.1 to 0.8.1.
WlTimePicker: local HH:mm/null time, minute precision, bounds and native attributes.WlFilePicker: stateless File[] selection, a trigger slot and synchronous choose()/clear(); the app owns uploads and limits.WlDatePicker.displayFormat: Russian display by default and ISO display with matching manual input; the ISO model is preserved.resolveWlIconName for canonical and legacy names.WlInput retains a string model with type="number", including clearing; native IME composition avoids premature commits.WlTimePicker shows focus and invalid outlines when the keyboard moves into internal segments of the native time control.verify:package handles Windows and Linux line endings in LICENSE while comparing license content strictly.WlNumberInput bounds do not reach aria-valuemin/aria-valuemax; default max=99 is preserved.Consumer upgrade. Existing models, classes, tokens and defaults are preserved; new components are imported explicitly.
WlCheckbox checked and indeterminate marks use SVG icons instead of font characters: their shapes and alignment match across three themes.WlCheckbox and WlRadio retain their appearance on hover.WlSelect, WlMultiSelect and WlAutocomplete disclosure arrows use aligned SVG icons instead of text characters.The first release under the new name on public npm. Setup instructions and publication status are in README.
whitewolf06/gavia-ui.gavia-ui on public npm: installation without a GitHub token after the first release.GAVIA_E2E_BASE_URL; catalog error messages use Gavia UI. The migration lists these changes.GAVIA_E2E_CHROMIUM_CHANNEL.Wl* names, props, events, models, slots, icon names, wl-* classes and --wl-* tokens are preserved.The required package-path change and consumer checks are described in the 0.7 migration. Application setup and the 0.6.0 design system are preserved.
prefers-reduced-motion.Application setup and table changes are described in the 0.6 migration and migration from 0.3. Work labeled 0.4/0.5 was included in 0.6.0; it has no separate release tags.
Record changes under “Unreleased” first. At release, move them under the version and actual publication date. Record features, fixes and required upgrade steps; breaking changes require a migration note. Root and package changelogs must have the same content; package documentation links are absolute. Verify publication separately from pushing the tag.