@aceshooting/lyra-ui 18.3.0 → 19.0.0

package/CHANGELOG.md

@@ -1,5 +1,44 @@
 # Changelog
 
+## 19.0.0
+
+### Major Changes
+
+- 6e31ab9: Distinguish omitted text overrides from explicit empty strings in `lr-agent-workspace` (`label`, `composerPlaceholder`), `lr-copy-button` (`copyLabel`, `successLabel`, `errorLabel`), `lr-file-input` (`label`), and `lr-retrieval-search` (`placeholder`). Omission uses the localized fallback; an explicit empty string suppresses it.
+  
+  These properties now read `undefined` when unset. Code that assumes an unset value is a string must handle the optional value, for example with `value ?? ''`. Remove an empty override to restore the localized fallback.
+
+### Minor Changes
+
+- 27ca436: Export the shared `LyraImageFit` type from granular media entries and preserve safe primitive point ids in chart activation details.
+
+### Patch Changes
+
+- c485895: Keep overflowing dialog and drawer bodies reachable by keyboard after resizing or changing their content. Preserve intermediate scroll-region stops in the shared overlay focus order, and expand coverage for chart point identities, granular image-fit types, and required-input descriptions.
+
+## 18.4.0
+
+### Minor Changes
+
+- cd2c1e9: `<lr-export-button>`: expose the trigger's paint as public custom properties.
+  
+  The component resolved nine paint values — resting, hover and active fill/label/border — but only
+  through private `--_lr-export-button-*` names, so the one and only way to repaint a trigger was to
+  reach for `::part(trigger)`. Its sibling `lr-button` has layered the same nine over public
+  `--lr-button-*` names for a long time; this is that pattern, applied here.
+  
+  `--lr-export-button-background`, `--lr-export-button-color`, `--lr-export-button-border` and the
+  matching `--lr-export-button-hover-*` / `--lr-export-button-active-*` triples each layer over
+  whatever the current `appearance` resolves to and leave the other paints untouched.
+  
+  That last point is the reported case. `appearance="outlined"` paints the label `--lr-color-brand`,
+  and `lr-export-button` — unlike `lr-button` — has no `variant` of its own to return it to neutral
+  text, so an outlined trigger sitting next to neutral-text buttons could not be matched through
+  documented properties at all. `--lr-export-button-color` is now that escape hatch.
+  
+  Nothing changes for a consumer who sets none of them: every `appearance` still resolves exactly the
+  values it did, and the private defaults are untouched.
+
 ## 18.3.0
 
 ### Minor Changes