v2.4.4
Bug Fixes
-
@byline/ui— Select, Autocomplete, and Datepicker popovers were rendering behind modal overlays instead of on top of them. The Modal sits at--z-index-modal: 1050(Base UI'sDialog.Portalmounts intodocument.body, escaping the admin shell's.byline-ui { isolation: isolate }stacking context), while the three popover primitives were hardcoded toz-index: 50— also portaled todocument.body, but losing the root-level stacking race against the modal portal every time. The most visible symptom was the link modal in@byline/richtext-lexical: the "Target collection" Select dropdown would open behind the modal and look empty, masking the underlying feature entirely. A new--z-index-popover: 1075token was added to the z-index scale (between--z-index-modal: 1050and--z-index-toast: 1100) and applied to the Select positioner/popup/list, the Autocomplete positioner/popup, and the Datepicker content. Any popover surface — including the Autocomplete inside the RelationPicker — now layers correctly above any open modal. No consumer action required. -
@byline/richtext-lexical—AutoLinkExtensionwas removed from the default extensions list returned bydefaultExtensionsArray()/defaultExtensionsList()/defaultClientEditorConfig. After the migration to the new Lexical extension API theAutoLinkExtensionregressed and was inserting auto-linked nodes incorrectly under some conditions; rather than ship the broken default while the underlying issue is investigated, the extension is now off out of the box for every consumer. The class itself is still exported from@byline/richtext-lexical(the source file is unchanged), so anyone who has opted in explicitly vialexicalEditor((c) => c.extensions.add(AutoLinkExtension))keeps that wiring — but no host app picks it up implicitly anymore. No migration is required to take the fix; consumers who want auto-linking back will need to add it to their editor config once it's fixed in a follow-up.
All other @byline/* packages bumped to 2.4.4 in lockstep with no behavioural changes this cycle.