docs/releases/v1.45.0-next.3-changelog.md
Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.45.0-next.3
coreServices.rootInstanceMetadata as a root service.package-docs command will now automatically use a typedoc.json file if one exists at the root of your project.83c100e: BREAKING: Removed Collapsible component. Migrate to Accordion or use React Aria Disclosure.
Accordion provides preset styling with a similar component structure.
- import { Collapsible } from '@backstage/ui';
+ import { Accordion, AccordionTrigger, AccordionPanel } from '@backstage/ui';
- <Collapsible.Root>
- <Collapsible.Trigger render={(props) => <Button {...props}>Toggle</Button>} />
- <Collapsible.Panel>Content</Collapsible.Panel>
- </Collapsible.Root>
+ <Accordion>
+ <AccordionTrigger title="Toggle" />
+ <AccordionPanel>Content</AccordionPanel>
+ </Accordion>
CSS classes: .bui-CollapsibleRoot → .bui-Accordion, .bui-CollapsibleTrigger → .bui-AccordionTrigger (now on heading element), .bui-CollapsiblePanel → .bui-AccordionPanel
For custom styling without preset styles:
import { Disclosure, Button, DisclosurePanel } from 'react-aria-components';
<Disclosure>
<Button slot="trigger">Toggle</Button>
<DisclosurePanel>Content</DisclosurePanel>
</Disclosure>;
816af0f: BREAKING: The SelectProps interface now accepts a generic type parameter for selection mode.
Added searchable and multiple selection support to Select component. The component now accepts searchable, selectionMode, and searchPlaceholder props to enable filtering and multi-selection modes.
Migration: If you're using SelectProps type directly, update from SelectProps to SelectProps<'single' | 'multiple'>. Component usage remains backward compatible.
@base-ui-components/react dependency as all components now use React Aria Components.loading prop to Button and ButtonIcon components for displaying spinner during async operations.87e597c: Adds support for default configuration for an entire notification channel. This setting will also be inherited down to origins and topics while still respecting the users individual choices.
This will be handy if you want to use a "opt-in" strategy.
87e597c: Adds support for default configuration for an entire notification channel. This setting will also be inherited down to origins and topics while still respecting the users individual choices.
This will be handy if you want to use a "opt-in" strategy.
7c6a66d: Added support for plugin-relative attachTo declarations for extension definitions. This allows for the creation of extension and extension blueprints that attach to other extensions of a particular kind in the same plugin, rather than needing to provide the exact extension ID. This is particularly useful when wanting to provide extension blueprints with a built-in hierarchy where the extensions created from one blueprint attach to extensions created from the other blueprint, for example:
// kind: 'tabbed-page'
const parentPage = TabbedPageBlueprint.make({
params: {....}
})
// attachTo: { kind: 'tabbed-page', input: 'tabs' }
const child1 = TabContentBlueprint.make({
name: 'tab1',
params: {....}
})
Updated dependencies
@backstage/ui.@kubernetes/client-node to 1.4.0.@kubernetes/client-node to 1.4.0.@kubernetes/client-node to 1.4.0.@kubernetes/client-node to 1.4.0.