# Backstage v1.47.0

2026-01-20 · [Original release notes](https://github.com/backstage/backstage/releases/tag/v1.47.0) · [Full summary](https://ratatosk.io/en/releases/backstage/v1.47.0)

Security 2 · Breaking changes 25 · Deprecations 9 · Important fixes 10 · Enhancements 34 · Dependency updates 258 · Other changes 45

## Check before upgrading

### Upgrade guide

- **Keeping Backstage up to date**
  > We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for [keeping Backstage updated](https://backstage.io/docs/getting-started/keeping-backstage-updated).
- **Upgrade Helper for upgrading to v1.47.0**
  > Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.47.0

  https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

## Security (2)

### Security fixes for Software Templates and external content reading

- Affects: setups using Software Templates or reading external content

> This release contains security fixes for Software Templates and reading external content.

### Redirect allow-list validation added to `coreServices.urlReader`

- Affects: setups using `coreServices.urlReader`

Previously, redirects could point to URLs outside `backend.reading.allow` and still be relied on. Redirect chains are now checked against that allow list, so targets not listed there must be added to the configuration.

> -
> 27f9061: BREAKING : coreServices.urlReader now validates that redirect chains are subject to the allow list in reading.allow of your app config. If you were relying on redirects that pointed to URLs that were not allowlisted, you will now have to add those to your config as well.
> Example:
> backend:
> reading:
> allow:
> - host: example.com
> + - host: storage-api.example.com
> - 27f9061: REwrite]

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

## Breaking changes (25)

### Updated `@backstage/ui` colors and removed `-tint` tokens

- Affects: setups using `@backstage/ui` color tokens, especially `-tint` tokens (Inferred)

Appropriate status or neutral colors are the alternatives for tint colors used in backgrounds, foregrounds, and borders.

> ### BREAKING: Updated color tokens in `@backstage/ui`
> UI color tokens have been updated to align with the new neutral surface-based design system, and the `-tint` tokens have been removed.
> More information can be found in the [BUI Changelog](https://ui.backstage.io/changelog).

### TechDocs AWS S3 authentication priority changed

- Affects: TechDocs setups using AWS S3 authentication (Inferred)

After upgrading, TechDocs checks `aws.accounts`, `techdocs.publisher.awsS3.credentials`, and `integrations.awsS3` in that order, then falls back to the default credential chain.

> ### BREAKING: Better AWS S3 auth handling in techdocs
> Techdocs now knows how to properly use `integrations.awsS3` config to authenticate with AWS S3. Since this affects the priority order of which auth setting is being used, it’s technically a breaking change.
> The new priority is:
> 1. `aws.accounts`
> 2. `techdocs.publisher.awsS3.credentials`
> 3. `integrations.awsS3`
> 4. Default credential chain

### Home plugin widget configuration requires explicit Save

- Affects: widget configuration in the `home` plugin UI (Inferred)

The new Cancel button discards unsaved changes.

> Widget configuration changes are now only saved when the Save button is explicitly clicked. A new Cancel button has been added to enable users to discard unsaved changes

### Custom homepage widget configuration now saves only on Save

- Affects: custom homepage widget configuration (Inferred)

Previously, edits were saved continuously, and entering edit mode could trigger extra HTTP requests with the user settings backend even when nothing changed. Cancel now discards unsaved edits and restores the last saved configuration.

Evidence: “Custom homepage widget configuration is now only saved when Save button is explicitly clicked. Previously the modified configuration was constantly saved making the use of Save button redundant. Also enabling the edit mode unnecessarily saved the unchanged configuration which combined with user settings backend caused extra HTTP requests.” https://github.com/backstage/backstage/pull/31198

> Contributed by [@kmikko](https://github.com/kmikko) in [#31198](https://github.com/backstage/backstage/pull/31198)

### Select popover list content wrapper changed

- Affects: Select implementations or stylesheets relying on list content being a direct child of `.bui-SelectPopover`
- Action required: CSS selectors updated to account for the new wrapper

Previously, list content was a direct child of `.bui-SelectPopover`; it is now wrapped in `.bui-Box.bui-PopoverContent`.

> The public SelectProps interface is now a union type, and Select popover list content is no longer a direct child of .bui-SelectPopover . #34489
> Update CSS selectors that rely on list content being a direct child of .bui-SelectPopover . Select popovers now use the standard BUI Popover content structure, with contents wrapped in .bui-Box.bui-PopoverContent . The existing .bui-Popover.bui-SelectPopover root classes are unchanged.

https://ui.backstage.io/changelog

### Dark-theme neutral background tokens updated

- Affects: setups using dark-theme neutral background tokens (Inferred)

In the general dark theme, neutral levels 1–4 change from `#1a1a1a`, `#282828`, `#393939`, and `#474747` to `#424141`, `#504f4f`, `#5c5c5c`, and `#676767`. The Spotify dark theme sets these levels to `#121212`, `#2a2a2a`, `#3a3a3a`, and `#484848`.

> -
> Updated the dark theme neutral background tokens to provide clearer contrast between neutral surfaces. #34567

https://ui.backstage.io/changelog

### Searchable Select layout and theme classes updated

- Affects: Searchable Select variants with public-class theme customizations

The search field stays fixed while results scroll. The public `classNames` root is `.bui-SelectContent`, with additional `searchWrapper` and `results` class names; `.bui-SelectResults` is the results container.

> Searchable Select keeps its search field fixed while results scroll. The new public classes .bui-SelectContent and .bui-SelectResults expose this layout for theme customization. #34591

https://ui.backstage.io/changelog

### Background token color values updated

- Affects: use of `--bui-bg-app` and `--bui-bg-neutral-1` through `--bui-bg-neutral-4` in light or dark themes
- Action required: No token renaming is required.

Existing references to these tokens now resolve to the updated solid-color values in both themes.

> Neutral backgrounds
> The neutral background tokens keep their existing names ( --bui-bg-app , --bui-bg-neutral-1 through --bui-bg-neutral-4 ) but are updated with new solid-color values for both light and dark themes. No token renaming is required. The -hover , -pressed , and -disabled interaction variants of these tokens are deprecated and should be removed.

https://ui.backstage.io/changelog

### Backstage UI background tokens shifted to neutral colors

- Affects: Backstage UI color-token usage, especially the listed `--bui-bg-tint` variables (Inferred)

The old tint tokens have no direct replacements; the new neutral color tokens on surface 0 or 1 can be used instead.

> -
> 95246eb: Breaking Updating color tokens to match the new neutral style on different surfaces.
> Migration notes
> There's no direct replacement for the old tint tokens but you can use the new neutral set of color tokens on surface 0 or 1 as a replacement.
> - --bui-bg-tint can be replaced by --bui-bg-neutral-on-surface-0
> - --bui-bg-tint-hover can be replaced by --bui-bg-neutral-on-surface-0-hover
> - --bui-bg-tint-pressed can be replaced by --bui-bg-neutral-on-surface-0-pressed
> - --bui-bg-tint-disabled can be replaced by --bui-bg-neutral-on-surface-0-disabled

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### `--bui-bg` renamed to `--bui-bg-surface-0`

- Affects: styles or configuration referencing `--bui-bg` (Inferred)

> -
> 4ea1d15: BREAKING : Renamed CSS variable --bui-bg to --bui-bg-surface-0 for consistency.

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### Backstage home widget configurations now require explicit saving

- Affects: Backstage home widget configurations (Inferred)

Cancel discards unsaved edits and restores the last saved state.

> - e091a83: Widget configurations are now only saved to storage when the Save button is explicitly clicked. Added a Cancel button that allows users to discard unsaved changes and revert to the last saved state.

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### TechDocs default Docker image updated to v1.2.8

- Affects: TechDocs setups using the default Docker image (Inferred)

> - f0951aa: Updated the defaultDockerImage to reflect the latest TechDocs Container version of v1.2.8

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### `@backstage/ui` `Table` wrapper renamed and `useTable` redesigned

- Affects: `Table` or `useTable` usage from `@backstage/ui` (Inferred)

The low-level React Aria wrapper is now `TableRoot`, while the new higher-level `Table` supports data display, pagination, sorting, and selection. The old `useTable` API used `data` and returned `data` and `paginationProps`; the redesigned API supports `complete`, `offset`, and `cursor` modes, with the migration example using `tableProps`, `mode: 'complete'`, and `getData`.

> ### BREAKING: Redesigned `Table` and `useTable` in `@backstage/ui`
> The `Table` component and accompanying `useTable` hook have been redesigned. The low-level React Aria wrapper `Table` is now `TableRoot`, while a higher level `Table` component now handles pagination, sorting, selection, and data display. The `useTable` also has a new API, that supports 3 pagination modes: `complete`, `offset`, and `cursor`.
> More information along with a migration guide can be found in the [BUI Changelog](https://ui.backstage.io/changelog).

### `coreServices.urlReader` checks redirect chains against the allow list

- Affects: App configurations using `coreServices.urlReader` (Inferred)
- Action required: Redirected-to URLs must also be added to `backend.reading.allow` in the app config if relying on redirects to them.

Before this release, redirects to URLs outside the allow list could work without those URLs being added to the app config.

> `coreServices.urlReader` now validates that redirect chains are subject to the allow list in `backend.reading.allow` of your app config. If you were relying on redirects that pointed to URLs that were not allowlisted, you will now have to add those to your config as well.

### `FetchUrlReader` public constructor removed

- Affects: setups or integrations that instantiate `FetchUrlReader` directly (Inferred)

> To support this, the `FetchUrlReader` class no longer has a public constructor, but instead has a `fromConfig` static factory method.

### App customization blueprints deprecated and moved to `@backstage/plugin-app-react`

- Affects: Setups that use one or more of the seven listed blueprints for app customization (Inferred)
- Action required: For use outside the `app` plugin, an `app` plugin override or a module with `pluginId` set to `app` is required.
- Removed in: not stated

Use currently triggers deprecation warnings; a future release will reject it.

> There were several blueprints in `@backstage/frontend-plugin-api` that were intended only for use in customization of the central app. For example `SignInPageBlueprint` that replaces the sign-in page, or `NavContentBlueprint` that replaces the sidebar content. The following blueprints have all been deprecated and moved to a new `@backstage/plugin-app-react` package:
> - `IconBundleBlueprint`
> - `NavContentBlueprint`
> - `RouterBlueprint`
> - `SignInPageBlueprint`
> - `SwappableComponentBlueprint`
> - `ThemeBlueprint`
> - `TranslationBlueprint`

### `ComboboxProps` becomes a union type

- Affects: Combobox setups needing async collections, incremental loading, client or server search, or rich or custom item rendering
- Action required: Type intersections instead of interfaces extending `ComboboxProps`

Array-valued options using `value` remain supported as a deprecated compatibility path. Top-level input state props also remain supported for plain-array options.

> -
> Combobox Breaking Combobox now supports async collections, incremental loading, client and server search, and rich or custom item rendering. Loading placeholders expose .bui-ComboboxLoading and .bui-ComboboxLoadingRow , and stale visible results expose data-stale on .bui-ComboboxList .

https://ui.backstage.io/changelog

### `SelectProps` changed to a union type

- Affects: TypeScript declarations extending `SelectProps`
- Action required: Type intersections in place of interfaces extending `SelectProps`

Custom interfaces could previously extend `SelectProps`; those declarations no longer compile with the new type.

> The public SelectProps interface is now a union type, and Select popover list content is no longer a direct child of .bui-SelectPopover . #34489
> Replace interfaces that extend SelectProps with type intersections.
> 
> - interface MySelectProps extends SelectProps {
> - trackingId : string ;
> - }
> + type MySelectProps = SelectProps & {
> + trackingId : string ;
> + };
> The public ComboboxProps interface is now a union type. #34489
> Replace interfaces that extend ComboboxProps with type intersections.
> - interface MyComboboxProps extends ComboboxProps {
> - trackingId : string ;
> - }
> + type MyComboboxProps = ComboboxProps & {
> + trackingId : string ;
> + };

https://ui.backstage.io/changelog

### Plugin API overrides limited to the owning plugin

- Affects: plugins that override APIs belonging to another plugin (Inferred)
- Action required: Overrides of core APIs provided by the app plugin must instead be done with an app module.

> - 3bd2a1a: BREAKING: The ability for plugins to override APIs has been restricted to only allow overrides of APIs within the same plugin. For example, a plugin can no longer override any of the core APIs provided by the app plugin, this must be done with an app module instead.

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### Table and useTable APIs redesigned

- Affects: setups using `Table`, `TableRoot`, `TablePagination`, or `useTable` from `@backstage/ui`
- Action required: Update imports and use the new `useTable` API; define columns and render with the new `Table` API.

Previously, `Table` was the React Aria wrapper, and `useTable` accepted `data` and `pagination` for rendering through `TableHeader`, `TableBody`, and `TablePagination`. Now the wrapper is `TableRoot`; the high-level `Table` uses columns and `tableProps` returned by `useTable`.

> @backstage/ui@0.11.0
> Minor Changes
> -
> 243e5e7: BREAKING : Redesigned Table component with new useTable hook API.
> - The Table component (React Aria wrapper) is renamed to TableRoot
> - New high-level Table component that handles data display, pagination, sorting, and selection
> - The useTable hook is completely redesigned with a new API supporting three pagination modes (complete, offset, cursor)
> - New types: ColumnConfig , TableProps , TableItem , UseTableOptions , UseTableResult
> New features include unified pagination modes, debounced query changes, stale data preservation during reloads, and row selection with toggle/replace behaviors.
> Migration guide:
> - Update imports and use the new useTable hook:
> - import { Table, useTable } from '@backstage/ui';
> - const { data, paginationProps } = useTable({ data: items, pagination: {...} });
> + import { Table, useTable, type ColumnConfig } from '@backstage/ui';
> + const { tableProps } = useTable({
> + mode: 'complete',
> + getData: () => items,
> + });
> - Define columns and render with the new Table API:
> - <Table aria-label="My table">
> - <TableHeader>...</TableHeader>
> - <TableBody items={data}>...</TableBody>
> - </Table>
> - <TablePagination {...paginationProps} />
> + const columns: ColumnConfig<Item>[] = [
> + { id: 'name', label: 'Name', isRowHeader: true, cell: item => <CellText title={item.name} /> },
> + { id: 'type', label: 'Type', cell: item => <CellText title={item.type} /> },
> + ];
> +
> + <Table columnConfig={columns} {...tableProps} />
> Affected components: Table, TableRoot, TablePagination

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### Frontend blueprints moved out of `@backstage/frontend-plugin-api`

- Affects: setups importing the listed blueprints from `@backstage/frontend-plugin-api` (Inferred)

> -
> 9ccf84e: Moved the following blueprints from @backstage/frontend-plugin-api :
> - AppRootWrapperBlueprint
> - IconBundleBlueprint
> - NavContentBlueprint
> - RouterBlueprint
> - SignInPageBlueprint
> - SwappableComponentBlueprint
> - ThemeBlueprint
> - TranslationBlueprint
> -

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### TechDocs AWS S3 integration credentials supported

- Affects: TechDocs AWS S3 publishers configured with `integrations.awsS3` (Inferred)
- Action required: A single `integrations.awsS3` configuration must have access to the TechDocs bucket; no action is required for the other listed credential configurations.

Before this release, `integrations.awsS3` credentials did not provide an authentication path for the TechDocs publisher. Credentials are now checked in this order: `aws.accounts`, `techdocs.publisher.awsS3.credentials`, `integrations.awsS3`, then the default credential chain; with multiple integrations, `accessKeyId` in `techdocs.publisher.awsS3.credentials` selects the target when provided, otherwise the default credential chain is used.

> -
> 63c459c: BREAKING: It's now possible to use the credentials from the integrations.awsS3 config to authenticate with AWS S3. The new priority is:
> - aws.accounts
> - techdocs.publisher.awsS3.credentials
> - integrations.awsS3
> - Default credential chain
> In case of multiple integrations.awsS3 are present, the target integration is determined by the accessKeyId in techdocs.publisher.awsS3.credentials if provided. Otherwise, the default credential chain is used.
> This means that depending on your setup, this feature may break your existing setup.
> In general:
> - if you are configuring aws.accounts , no action is required
> - if you are configuring techdocs.publisher.awsS3.credentials , no action is required
> - if you are configuring multiple integrations under integrations.awsS3 , no action is required
> - if you are configuring a single integration under integrations.awsS3 , make sure that the integration has access to the bucket you are using for TechDocs

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### Minimum required `@swc/core` version raised

- Affects: setups using `@backstage/cli` with an `@swc/core` version below the new minimum (Inferred)

> - 9ee5996: Bump minimum required @swc/core to avoid transpilation bug

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### `@backstage/plugin-catalog-graph` sets a high array limit

- Affects: setups using `@backstage/plugin-catalog-graph` (Inferred)

Previously, a limit of zero meant unlimited. The package now uses an arbitrary high limit above the default of 20.

> - 5c49a00: Update for the qs library bump: the old array limit setting has changed to be more strict; you can no longer just give a zero to mean unlimited. So we choose an arbitrary high value, to at least go higher than the default 20.
> - 5c49a00: Update for the qs library bump: the old array limit setting has changed to be more strict; you can no longer just give a zero to mean unlimited. So we choose an arbitrary high value, to at least go higher than the default 20.

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### `FetchUrlReader` constructor made private

- Affects: code that constructs `FetchUrlReader` directly
- Action required: Use `FetchUrlReader.fromConfig` instead of the now-private constructor

> - 27f9061: REwrite]
> 27f9061: BREAKING : The constructor for FetchUrlReader is now private. If you have to construct an instance of it, please use FetchUrlReader.fromConfig instead.

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

## Deprecations (9)

### Blueprint use outside the `app` plugin deprecated

- Affects: setups using these blueprints outside the `app` plugin
- Removed in: not stated

This use triggers deprecation warnings in this release and will be rejected in a future release. The allowed paths are an `app` plugin override or a module with `pluginId` set to `app`.

> These blueprints are also being restricted from use outside of the `app` plugin. This means that you have to either use an `app` plugin override or a module with `pluginId` set to `app`. These currently trigger deprecation warnings, but will instead be rejected in a future release.

### Deprecation warnings for cross-plugin and app-core Utility API factory overrides

- Affects: Factory overrides for other plugins' Utility APIs, including core APIs provided by the app plugin
- Removed in: not stated

These overrides still work in this release; the restriction takes effect in a future release. The note says to make them using a plugin override or module instead.

> ### Deprecations and upcoming restrictions for API factories in new frontend system
> Similar to the above change, restrictions are being introduced that limit the ability for plugins to override both core Utility APIs and API factories from other plugins. Plugins will be restricted from installing factory overrides for Utility APIs that belong to other plugins. This restriction also applies to the core APIs provided by the app plugin. These overrides now instead need to be made using a plugin override or module.
> Just like the blueprint changes, this release will only trigger deprecation warnings, with the change taking effect in a future release.

### Top-level Combobox input state props deprecated

- Affects: Combobox setups controlling input state or custom filtering
- Removed in: not stated

Top-level `inputValue` and `onInputChange` remain supported with plain-array `options`, but are deprecated; nested `search` can carry them instead. Custom filtering can also be configured through nested `search`.

> Move input state and custom filtering into the nested search configuration:
> - < Combobox inputValue = {query} onInputChange = {setQuery} />
> + < Combobox search = {{ inputValue : query , onInputChange : setQuery }} />
> The existing top-level input state props remain supported as a deprecated compatibility path for plain-array options .

https://ui.backstage.io/changelog

### Select gains async collections, search, and custom item rendering

- Affects: Select setups using async collections, client/server search, or rich and custom item rendering (Inferred)
- Removed in: not stated

The new capabilities are available through the collection and search APIs; existing convenience options remain supported.

> Select Breaking Select now supports async collections, incremental loading, client and server search, and rich or custom item rendering. Loading placeholders expose .bui-SelectLoading and .bui-SelectLoadingRow , and stale retained results expose data-stale on .bui-SelectList .

https://ui.backstage.io/changelog

### `id` recommended for plain Select options

- Affects: plain options in Select
- Removed in: not stated

Array-valued options using `value` continue to work through a deprecated compatibility path; new option content fields and async option sources require `id`.

> Prefer id instead of value for plain options. Existing array-valued options using value remain supported as a deprecated compatibility path, but new option content fields and async option sources require id .
> Prefer id instead of value for plain options. Existing array-valued options using value remain supported as a deprecated compatibility path, but new option content fields and async option sources require id .

https://ui.backstage.io/changelog

### Select search props deprecated in favor of nested `search` configuration

- Affects: Select search configured with `searchable`, `searchPlaceholder`, or nested `search`
- Removed in: not stated

The nested configuration uses `placeholder` in place of `searchPlaceholder`. The old props still work on their existing paths, but are deprecated; client-side search is enabled through the nested `search` API.

> Replace searchable and searchPlaceholder with nested search configuration:
> - < Select searchable searchPlaceholder = "Search owners" />
> + < Select search = {{ placeholder : 'Search owners' }} />

https://ui.backstage.io/changelog

### Legacy color tokens deprecated

- Affects: setups referencing the legacy color tokens listed in the migration mappings
- Removed in: not stated

Their existing values remain unchanged for backward compatibility. The migration mappings identify replacements in the new semantic color families.

> The previous tokens remain in place for backward compatibility but are now deprecated and will be removed in a future release. #34400
> Migration Guide:
> Foreground
> | Deprecated | Replacement |
> | --bui-fg-danger | --bui-fg-negative |
> | --bui-fg-success | --bui-fg-positive |
> | --bui-fg-info | --bui-fg-announcement |
> Accent
> | Deprecated | Replacement |
> | --bui-bg-solid | --bui-accent-bg |
> | --bui-bg-solid-hover | --bui-accent-bg-hover |
> | --bui-bg-solid-disabled | --bui-accent-bg-disabled |
> | --bui-fg-solid | --bui-accent-fg |
> | --bui-fg-solid-disabled | --bui-accent-fg-disabled |
> Positive
> | Deprecated | Replacement |
> | --bui-bg-success | --bui-positive-bg-subdued |
> | --bui-fg-success-on-bg | --bui-positive-fg-subdued |
> | --bui-border-success | --bui-positive-border |
> Negative
> | Deprecated | Replacement |
> | --bui-bg-danger | --bui-negative-bg-subdued |
> | --bui-fg-danger-on-bg | --bui-negative-fg-subdued |
> | --bui-border-danger | --bui-negative-border |
> Warning
> | Deprecated | Replacement |
> | --bui-bg-warning | --bui-warning-bg-subdued |
> | --bui-fg-warning-on-bg | --bui-warning-fg-subdued |
> | --bui-border-warning | --bui-warning-border |
> Announcement
> | Deprecated | Replacement |
> | --bui-bg-info | --bui-announcement-bg-subdued |
> | --bui-fg-info-on-bg | --bui-announcement-fg-subdued |
> | --bui-border-info | --bui-announcement-border |

https://ui.backstage.io/changelog

### Neutral background interaction variants deprecated

- Affects: neutral background tokens with `-hover`, `-pressed`, or `-disabled` variants
- Removed in: not stated

The variants remain in place with their values unchanged for backward compatibility, but are slated for removal in a future release.

> The neutral background tokens keep their existing names ( --bui-bg-app , --bui-bg-neutral-1 through --bui-bg-neutral-4 ) but are updated with new solid-color values for both light and dark themes. No token renaming is required. The -hover , -pressed , and -disabled interaction variants of these tokens are deprecated and should be removed.

https://ui.backstage.io/changelog

### App blueprints moved and deprecated

- Affects: uses of the eight blueprints outside app plugin overrides or modules
- Removed in: not stated

`AppRootWrapperBlueprint`, `IconBundleBlueprint`, `NavContentBlueprint`, `RouterBlueprint`, `SignInPageBlueprint`, `SwappableComponentBlueprint`, `ThemeBlueprint`, and `TranslationBlueprint` are now in `@backstage/plugin-app-react`. Using them outside app plugin overrides or modules produces a deprecation warning.

> -
> 9ccf84e: The following blueprints are being restricted to only be used in app plugin overrides and modules. They are being moved to the @backstage/plugin-app-react package and have been deprecated:
> - AppRootWrapperBlueprint
> - IconBundleBlueprint
> - NavContentBlueprint
> - RouterBlueprint
> - SignInPageBlueprint
> - SwappableComponentBlueprint
> - ThemeBlueprint
> - TranslationBlueprint
> -
> 9ccf84e: The following blueprints are being restricted to only be used in app plugin overrides and modules. They will now produce a deprecation warning when used outside of the app plugin:
> - AppRootWrapperBlueprint
> - IconBundleBlueprint
> - NavContentBlueprint
> - RouterBlueprint
> - SignInPageBlueprint
> - SwappableComponentBlueprint
> - ThemeBlueprint
> - TranslationBlueprint

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

## Important fixes (10)

### Header tab links now respect the router basename

- Affects: Backstage hosted below a subpath with Header tabs and a configured router basename

When Backstage was hosted below a subpath, tab links omitted the configured basename, so copied links and browser-native navigation could target the wrong URL. Rendered links now include the basename for flat and grouped tabs, and active-tab detection works with a configured basename.

> -
> Header Fixed header tab links to respect the configured router basename . #34469

https://ui.backstage.io/changelog

### CSS module class-name collisions fixed with content-based hashing

- Affects: setups running multiple package versions simultaneously

Before this fix, CSS module class names could collide when multiple package versions ran at the same time. They are now generated using content-based hashing.

> - f6a5d2f: Fixed CSS module class name collisions when running multiple versions of packages simultaneously by using content-based hashing for class name generation.

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### `MarkdownContent` now matches GitHub when rendering HTML in GitHub-flavored Markdown

- Affects: `MarkdownContent` rendering GitHub-flavored Markdown that contains HTML (Inferred)

> - a723b8a: The MarkdownContent component now handles HTML content the same way as GitHub when rendering GitHub-flavored Markdown

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### More targeted team fetching and entity updates in `GithubOrgEntityProvider`

- Affects: setups using `GithubOrgEntityProvider` membership-event handling or edit-team handling (Inferred)

Membership events previously fetched all organization users and used `replaceEntitiesOperation`, which could delete entities unnecessarily. They now fetch only the specific user's teams and use `addEntitiesOperation` instead.

> - cb4b907: Improved efficiency of GithubOrgEntityProvider membership event handling and edit team. The provider now fetches only the specific user's teams instead of all organization users when processing membership events, and uses addEntitiesOperation instead of replaceEntitiesOperation to avoid unnecessary entity deletions.

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### GithubOrgEntityProvider avoids unnecessary entity deletions during edit handling

- Affects: Setups using `GithubOrgEntityProvider` for edit team handling (Inferred)

When `GithubOrgEntityProvider` handled an edit team, `replaceEntitiesOperation` could cause unnecessary entity deletions. It now uses `addEntitiesOperation` instead.

> `GithubOrgEntityProvider` membership event handling and edit team has been improved. The provider now fetches only the specific user's teams instead of all organization users when processing membership events, and uses `addEntitiesOperation` instead of `replaceEntitiesOperation` to avoid unnecessary entity deletions.

### Async pagination scrolling fixed in Combobox and Select popovers

- Affects: setups using async pagination in Combobox or Select popovers (Inferred)

Previously, unconstrained list scroll containers left the pagination sentinel visible, causing every page to load recursively. Now, additional pages load as users scroll.

> -
> Combobox Select Fixed async pagination in Combobox and Select popovers so additional pages load as users scroll instead of loading every page immediately. Combobox now uses .bui-PopoverContent as its scroll container, while all Select variants use the new .bui-SelectResults results container.

https://ui.backstage.io/changelog

### BUI `Combobox` crash with searchable plain options fixed

- Affects: BUI `Combobox` setups with plain options and client-side search under `react-aria-components` 1.17

The component could crash with `state.collection.filter is not a function`. Searchable plain options now go through React Aria’s filterable collection path, avoiding the crash.

> -
> Combobox Fixed Combobox client search crashing when used with plain options. #34590

https://ui.backstage.io/changelog

### SQLite error in `user_created_at` migration fixed

- Affects: `user_created_at` migrations using SQLite (Inferred)

When the `user_created_at` migration used non-constant defaults with SQLite, it could fail with a `SQLiteError`.

> - 7ffc873: Fix user_created_at migration causing SQLiteError regarding use of non-constants for defaults

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### Backend stop now cleans up process event listeners

- Affects: backends using `@backstage/backend-app-api` (Inferred)

> @backstage/backend-app-api@1.4.1
> Patch Changes
> - 04db26b: Clean up process event listeners on backend stop to prevent leaks

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

### PuppetDB catalog backend crash fixed

- Affects: installations using `@backstage/plugin-catalog-backend-module-puppetdb`

The module crashed when `latest_report_status` was undefined; that crash is fixed.

> @backstage/plugin-catalog-backend-module-puppetdb@0.2.18
> Patch Changes
> - a307700: Fixed crash when latest_report_status is undefined

https://github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

## Enhancements (34)

- Configurable action filtering in `ActionsService` (To use: Configure `actions.filter` with include and/or exclude rules to filter exposed actions.)
- Configurable GitHub Actions workflow access for repository creation (To use: `workflowAccess` configured in the `github:repo:create` action input; the example uses `organization`.)
- Kafka consumers can start from the earliest message (To use: Set `fromBeginning: true` to start at the earliest available message; the default is `false`.)
- Configurable Kafka offset commits (To use: Set `autoCommit` to `false` for manual commits.)
- Kafka consumers can pause after processing errors (To use: Set `pauseOnError: true` to enable the behavior.)
- Combobox loading and stale-result styling hooks exposed
- Select loading and stale-result styling hooks added
- Numeric `NumberField` component added to `@backstage/ui`
- Expanded `@backstage/ui` color token set
- Configurable action filtering in ActionsService
- `GoogleGcsReader` adds `readTree` support
- New `ToggleButton` and `ToggleButtonGroup` components in Backstage UI
- Indeterminate state support for the Checkbox component
- Backstage UI adds a Popover component
- New `--bui-shadow` elevation token
- Responsive width controls for Table columns (To use: Use the `width`, `defaultWidth`, `minWidth`, and/or `maxWidth` props on Table columns to configure column widths.)
- Configurable pagination for `useTable` and Table
- Table accepts `className` and `style` props
- Initial release of the `@backstage/plugin-app-react` web library
- New Frontend support for additional Devtools tabs
- Kafka offset configuration added to the events backend module
- Kafka offset configuration with `fromBeginning` and `autoCommit` (To use: Kafka offset configuration using `fromBeginning` and `autoCommit`)
- Configurable API Base URL for the Sentry scaffolder backend
- `@swc/core` adds `ES2023` and `ES2024` transpilation support
- Package inclusion and output format options for `backstage-cli info`
- `@backstage/backend-test-utils` added to backend package templates
- Updated `@backstage/create-app` to 0.7.8
- create-app Dockerfile updated for Node 24 and Debian Trixie
- Alpha `PluginWrapperBlueprint` for wrapping plugin elements (To use: the alpha export from `@backstage/frontend-plugin-api/alpha`)
- GoogleGcs `ScmIntegration` implementation added
- Support for `PluginWrapperBlueprint` in `@backstage/plugin-app` (To use: `PluginWrapperBlueprint` from `@backstage/frontend-plugin-api/alpha`)
- Custom start URL search parameters for the OIDC provider (To use: `startUrlSearchParams` config property)
- Notifications plugin adds i18n support
- Workflow access level option for `github:repo:create` repositories (To use: `workflowAccess` input)

## Dependency updates (258)

258 more, none mentioning security

- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/backend-app-api@1.4.1 - @backstage/integration@1.19.2 - @backstage/plugin-auth-node@0.6.11 - @backstage/plugin-permission-node@0.10.8`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/frontend-defaults@0.3.5`
- `- 9c76682: build(deps-dev): bump storybook from 10.1.9 to 10.1.10`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/backend-plugin-api@1.6.1`
- `- @backstage/plugin-auth-node@0.6.11`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1`
- `Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5 - @backstage/plugin-catalog-react@1.21.5 - @backstage/plugin-home-react@0.1.34`
- `- @backstage/backend-plugin-api@1.6.1`
- `- @backstage/plugin-scaffolder-node@0.12.3`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1`
- `- @backstage/integration@1.19.2`
- `@backstage/app-defaults@1.7.4 Patch Changes - Updated dependencies - @backstage/core-components@0.18.5`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1`
- `@backstage/backend-dynamic-feature-service@0.7.8 Patch Changes - Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/cli-common@0.1.17 - @backstage/plugin-app-node@0.1.41 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/backend-openapi-utils@0.6.5 - @backstage/plugin-auth-node@0.6.11 - @backstage/plugin-permission-common@0.9.4 - @backstage/plugin-permission-node@0.10.8 - @backstage/plugin-catalog-backend@3.3.1 - @backstage/plugin-events-backend@0.5.10`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1`
- `- @backstage/cli-common@0.1.17`
- `- @backstage/plugin-auth-node@0.6.11`
- `- @backstage/plugin-permission-common@0.9.4`
- `- @backstage/plugin-permission-node@0.10.8`
- `- Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/backend-app-api@1.4.1 - @backstage/plugin-auth-node@0.6.11 - @backstage/plugin-permission-common@0.9.4`
- `- 4eeba9e: Upgrade zod-validation-error to version 4`
- `- @backstage/cli-common@0.1.17`
- `- @backstage/integration@1.19.2`
- `@backstage/core-compat-api@0.5.6 Patch Changes - Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/plugin-catalog-react@1.21.5`
- `- Updated dependencies - @backstage/cli-common@0.1.17`
- `- Updated dependencies - @backstage/ui@0.11.0 - @backstage/core-components@0.18.5 - @backstage/app-defaults@1.7.4 - @backstage/integration-react@1.2.14 - @backstage/plugin-catalog-react@1.21.5`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- @backstage/plugin-app@0.3.4`
- `- @backstage/frontend-app-api@0.14.0`
- `@backstage/frontend-test-utils@0.4.3 - Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/plugin-app@0.3.4 - @backstage/frontend-app-api@0.14.0`
- `@backstage/integration-react@1.2.14 Patch Changes - Updated dependencies - @backstage/integration@1.19.2`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/cli-common@0.1.17`
- `@techdocs/cli@1.10.4`
- `- @backstage/backend-defaults@0.15.0`
- `- @backstage/cli-common@0.1.17`
- `- @backstage/plugin-techdocs-node@1.14.0`
- `- 0216090: Updated dependency @types/swagger-ui-react to ^5.0.0 .`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/plugin-catalog@1.32.2`
- `- @backstage/core-components@0.18.5`
- `- @backstage/plugin-catalog-react@1.21.5`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/plugin-app-react@0.1.0`
- `- @backstage/core-components@0.18.5`
- `- @backstage/integration-react@1.2.14`
- `- @backstage/backend-plugin-api@1.6.1`
- `- @backstage/plugin-app-node@0.1.41`
- `- @backstage/plugin-auth-node@0.6.11`
- `- @backstage/backend-plugin-api@1.6.1`
- `@backstage/plugin-app-visualizer@0.1.27 Patch Changes - Updated dependencies - @backstage/ui@0.11.0 - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- @backstage/backend-plugin-api@1.6.1`
- `- @backstage/plugin-auth-backend@0.26.0`
- `- @backstage/plugin-auth-node@0.6.11`
- `- @backstage/backend-plugin-api@1.6.1`
- `- @backstage/plugin-auth-backend@0.26.0`
- `- @backstage/plugin-auth-node@0.6.11`
- `- 4eeba9e: Upgrade zod-validation-error to version 4`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1`
- `@backstage/plugin-auth-react@0.1.23 Patch Changes - Updated dependencies - @backstage/core-components@0.18.5`
- `@backstage/plugin-bitbucket-cloud-common@0.3.6 Patch Changes - Updated dependencies - @backstage/integration@1.19.2`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- @backstage/core-compat-api@0.5.6`
- `- @backstage/plugin-search-react@1.10.2`
- `- @backstage/integration-react@1.2.14`
- `- @backstage/plugin-catalog-react@1.21.5`
- `- @backstage/plugin-scaffolder-common@1.7.5`
- `- @backstage/plugin-techdocs-react@1.3.7`
- `@backstage/plugin-catalog-backend@3.3.1 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2 - @backstage/backend-openapi-utils@0.6.5 - @backstage/plugin-permission-common@0.9.4 - @backstage/plugin-permission-node@0.10.8`
- `@backstage/plugin-catalog-backend-module-aws@0.4.19 Patch Changes - Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2`
- `@backstage/plugin-catalog-backend-module-azure@0.3.13 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2`
- `@backstage/plugin-catalog-backend-module-backstage-openapi@0.5.10 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/backend-openapi-utils@0.6.5`
- `@backstage/plugin-catalog-backend-module-bitbucket-cloud@0.5.7 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2 - @backstage/plugin-bitbucket-cloud-common@0.3.6`
- `@backstage/plugin-catalog-backend-module-bitbucket-server@0.5.7 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2`
- `@backstage/plugin-catalog-backend-module-gerrit@0.3.10 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2`
- `@backstage/plugin-catalog-backend-module-gitea@0.1.8 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2`
- `- @backstage/backend-plugin-api@1.6.1`
- `- @backstage/integration@1.19.2`
- `- @backstage/backend-plugin-api@1.6.1`
- `- @backstage/plugin-catalog-backend-module-github@0.12.1`
- `@backstage/plugin-catalog-backend-module-gitlab@0.7.7 Patch Changes - Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2`
- `@backstage/plugin-catalog-backend-module-gitlab-org@0.2.17 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-catalog-backend-module-gitlab@0.7.7`
- `@backstage/plugin-catalog-backend-module-incremental-ingestion@0.7.8 Patch Changes - Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-permission-common@0.9.4 - @backstage/plugin-catalog-backend@3.3.1`
- `@backstage/plugin-catalog-backend-module-logs@0.1.18 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-catalog-backend@3.3.1`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1`
- `@backstage/plugin-catalog-backend-module-openapi@0.2.18 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1`
- `@backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.2.16 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-common@1.7.5`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5 - @backstage/plugin-catalog-react@1.21.5`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5 - @backstage/integration@1.19.2 - @backstage/integration-react@1.2.14 - @backstage/plugin-catalog-react@1.21.5`
- `@backstage/plugin-catalog-react@1.21.5 Patch Changes - Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5 - @backstage/plugin-permission-common@0.9.4 - @backstage/core-compat-api@0.5.6 - @backstage/frontend-test-utils@0.4.3 - @backstage/integration-react@1.2.14`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5 - @backstage/plugin-devtools-react@0.1.0 - @backstage/core-compat-api@0.5.6`
- `@backstage/plugin-config-schema@0.1.76 Patch Changes - Updated dependencies - @backstage/core-components@0.18.5`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- @backstage/plugin-devtools-react@0.1.0`
- `- @backstage/plugin-devtools-common@0.1.21`
- `- @backstage/core-compat-api@0.5.6`
- `- @backstage/backend-defaults@0.15.0`
- `- @backstage/backend-plugin-api@1.6.1`
- `- @backstage/cli-common@0.1.17`
- `@backstage/plugin-events-backend@0.5.10 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/backend-openapi-utils@0.6.5`
- `@backstage/plugin-events-backend-module-github@0.4.8 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2`
- `@backstage/plugin-home-react@0.1.34 Patch Changes - Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5`
- `@backstage/plugin-kubernetes@0.12.15 Patch Changes - Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5 - @backstage/plugin-catalog-react@1.21.5 - @backstage/plugin-kubernetes-react@0.5.15`
- `@backstage/plugin-kubernetes-cluster@0.0.33 Patch Changes - Updated dependencies - @backstage/core-components@0.18.5 - @backstage/plugin-catalog-react@1.21.5 - @backstage/plugin-kubernetes-react@0.5.15`
- `@backstage/plugin-kubernetes-react@0.5.15 Patch Changes - Updated dependencies - @backstage/core-components@0.18.5`
- `@backstage/plugin-mcp-actions-backend@0.1.7 Patch Changes - 4d82a35: build(deps): bump @modelcontextprotocol/sdk from 1.24.3 to 1.25.2 - Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1`
- `- Updated dependencies - @backstage/ui@0.11.0 - @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5 - @backstage/plugin-catalog-react@1.21.5`
- `- Updated dependencies - @backstage/core-components@0.18.5 - @backstage/plugin-catalog-react@1.21.5`
- `@backstage/plugin-permission-common@0.9.4 Patch Changes - 872eb91: Upgrade zod-to-json-schema to latest version`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-auth-node@0.6.11 - @backstage/plugin-permission-common@0.9.4`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- @backstage/integration@1.19.2`
- `- @backstage/plugin-scaffolder-react@1.19.5`
- `- @backstage/integration-react@1.2.14`
- `- @backstage/plugin-catalog-react@1.21.5`
- `- @backstage/plugin-techdocs-react@1.3.7`
- `- Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2 - @backstage/backend-openapi-utils@0.6.5 - @backstage/plugin-scaffolder-backend-module-github@0.9.4 - @backstage/plugin-auth-node@0.6.11 - @backstage/plugin-scaffolder-backend-module-azure@0.2.17 - @backstage/plugin-permission-common@0.9.4 - @backstage/plugin-permission-node@0.10.8 - @backstage/plugin-bitbucket-cloud-common@0.3.6 - @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.2.16 - @backstage/plugin-scaffolder-backend-module-bitbucket@0.3.18 - @backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.3.1 - @backstage/plugin-scaffolder-backend-module-bitbucket-server@0.2.17 - @backstage/plugin-scaffolder-backend-module-gerrit@0.2.17 - @backstage/plugin-scaffolder-backend-module-gitea@0.2.17 - @backstage/plugin-scaffolder-backend-module-gitlab@0.11.1 - @backstage/plugin-scaffolder-common@1.7.5`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `@backstage/plugin-scaffolder-backend-module-bitbucket@0.3.18 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2 - @backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.3.1 - @backstage/plugin-scaffolder-backend-module-bitbucket-server@0.2.17`
- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.3.1 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2 - @backstage/plugin-bitbucket-cloud-common@0.3.6`
- `@backstage/plugin-scaffolder-backend-module-bitbucket-server@0.2.17 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `@backstage/plugin-scaffolder-backend-module-confluence-to-markdown@0.3.17 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `@backstage/plugin-scaffolder-backend-module-cookiecutter@0.3.19 Patch Changes - Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `@backstage/plugin-scaffolder-backend-module-gcp@0.2.17 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `@backstage/plugin-scaffolder-backend-module-gerrit@0.2.17 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `@backstage/plugin-scaffolder-backend-module-gitea@0.2.17 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `@backstage/plugin-scaffolder-backend-module-gitlab@0.11.1 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `@backstage/plugin-scaffolder-backend-module-notifications@0.1.18 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3`
- `@backstage/plugin-scaffolder-backend-module-rails@0.5.17 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/integration@1.19.2`
- `@backstage/plugin-scaffolder-backend-module-yeoman@0.4.18 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/plugin-scaffolder-node-test-utils@0.3.7`
- `@backstage/plugin-scaffolder-common@1.7.5 Patch Changes - Updated dependencies - @backstage/integration@1.19.2 - @backstage/plugin-permission-common@0.9.4`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2 - @backstage/plugin-permission-common@0.9.4 - @backstage/plugin-scaffolder-common@1.7.5`
- `- Updated dependencies - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-scaffolder-node@0.12.3 - @backstage/backend-test-utils@1.10.3`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- @backstage/plugin-catalog-react@1.21.5`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- @backstage/plugin-search-react@1.10.2`
- `- @backstage/plugin-catalog-react@1.21.5`
- `@backstage/plugin-search-backend@2.0.10`
- `Patch Changes - Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/backend-openapi-utils@0.6.5 - @backstage/plugin-permission-common@0.9.4 - @backstage/plugin-permission-node@0.10.8`
- `@backstage/plugin-search-backend-module-techdocs@0.4.10 Patch Changes - Updated dependencies - @backstage/backend-plugin-api@1.6.1`
- `- @backstage/plugin-techdocs-node@1.14.0`
- `@backstage/plugin-search-react@1.10.2 Patch Changes - Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5 - @backstage/integration@1.19.2 - @backstage/plugin-search-react@1.10.2 - @backstage/integration-react@1.2.14 - @backstage/plugin-auth-react@0.1.23 - @backstage/plugin-catalog-react@1.21.5 - @backstage/plugin-techdocs-react@1.3.7`
- `@backstage/plugin-techdocs-addons-test-utils@2.0.1 Patch Changes - Updated dependencies - @backstage/plugin-catalog@1.32.2 - @backstage/plugin-techdocs@1.16.2 - @backstage/plugin-search-react@1.10.2 - @backstage/integration-react@1.2.14 - @backstage/plugin-catalog-react@1.21.5 - @backstage/plugin-techdocs-react@1.3.7`
- `- Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/integration@1.19.2 - @backstage/plugin-techdocs-node@1.14.0`
- `@backstage/plugin-techdocs-module-addons-contrib@1.1.32 Patch Changes - Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5 - @backstage/integration@1.19.2 - @backstage/integration-react@1.2.14 - @backstage/plugin-techdocs-react@1.3.7`
- `@backstage/plugin-techdocs-react@1.3.7 Patch Changes - Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/core-components@0.18.5`
- `- Updated dependencies - @backstage/backend-defaults@0.15.0 - @backstage/backend-plugin-api@1.6.1 - @backstage/plugin-auth-node@0.6.11`
- `- @backstage/ui@0.11.0`
- `- @backstage/plugin-catalog@1.32.2`
- `- @backstage/plugin-home@0.9.0`
- `- @backstage/cli@0.35.2`
- `- @backstage/core-components@0.18.5`
- `- @backstage/plugin-org@0.6.48`
- `- @backstage/plugin-mui-to-bui@0.2.3`
- `- @backstage/plugin-notifications@0.5.13`
- `- @backstage/frontend-app-api@0.14.0`
- `- @backstage/plugin-api-docs@0.13.3`
- `- @backstage/plugin-techdocs@1.16.2`
- `- @backstage/plugin-catalog-unprocessed-entities@0.2.25`
- `- @backstage/plugin-devtools@0.1.35`
- `- @backstage/plugin-scaffolder@1.35.1`
- `- @backstage/plugin-catalog-graph@0.5.6`
- `- @backstage/plugin-search@1.5.3`
- `- @backstage/plugin-search-react@1.10.2`
- `- @backstage/app-defaults@1.7.4`
- `- @backstage/integration-react@1.2.14`
- `- @backstage/plugin-auth-react@0.1.23`
- `- @backstage/plugin-catalog-import@0.13.9`
- `- @backstage/plugin-catalog-react@1.21.5`
- `- @backstage/plugin-kubernetes@0.12.15`
- `- @backstage/plugin-kubernetes-cluster@0.0.33`
- `- @backstage/plugin-signals@0.0.27`
- `- @backstage/plugin-techdocs-module-addons-contrib@1.1.32`
- `- @backstage/plugin-techdocs-react@1.3.7`
- `- @backstage/plugin-user-settings@0.8.31`
- `- @backstage/ui@0.11.0`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/plugin-catalog@1.32.2`
- `- @backstage/plugin-home@0.9.0`
- `- @backstage/cli@0.35.2`
- `- @backstage/core-components@0.18.5`
- `- @backstage/plugin-org@0.6.48`
- `- @backstage/plugin-app@0.3.4`
- `- @backstage/plugin-notifications@0.5.13`
- `- @backstage/frontend-app-api@0.14.0`
- `- @backstage/plugin-api-docs@0.13.3`
- `- @backstage/plugin-techdocs@1.16.2`
- `- @backstage/plugin-devtools@0.1.35`
- `- @backstage/plugin-scaffolder@1.35.1`
- `- @backstage/plugin-catalog-graph@0.5.6`
- `- @backstage/plugin-search@1.5.3`
- `- @backstage/core-compat-api@0.5.6`
- `- @backstage/frontend-defaults@0.3.5`
- `- @backstage/plugin-search-react@1.10.2`
- `- @backstage/app-defaults@1.7.4`
- `- @backstage/integration-react@1.2.14`
- `- @backstage/plugin-app-visualizer@0.1.27`
- `- @backstage/plugin-auth@0.1.4`
- `- @backstage/plugin-auth-react@0.1.23`
- `- @backstage/plugin-catalog-import@0.13.9`
- `- @backstage/plugin-catalog-react@1.21.5`
- `- @backstage/plugin-kubernetes@0.12.15`
- `- @backstage/plugin-signals@0.0.27`
- `- @backstage/plugin-techdocs-react@1.3.7`
- `- @backstage/plugin-user-settings@0.8.31`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- @backstage/backend-defaults@0.15.0`
- `- @backstage/backend-plugin-api@1.6.1`
- `- @backstage/plugin-app-backend@0.5.10`
- `- @backstage/plugin-techdocs-backend@2.1.4`
- `- @backstage/plugin-scaffolder-backend@3.1.1`
- `- @backstage/plugin-mcp-actions-backend@0.1.7`
- `- @backstage/plugin-auth-backend@0.26.0`
- `- @backstage/plugin-scaffolder-backend-module-github@0.9.4`
- `- @backstage/plugin-devtools-backend@0.5.13`
- `- @backstage/plugin-auth-node@0.6.11`
- `- @backstage/plugin-catalog-backend@3.3.1`
- `- @backstage/plugin-catalog-backend-module-backstage-openapi@0.5.10`
- `- @backstage/plugin-catalog-backend-module-openapi@0.2.18`
- `- @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.2.16`
- `- @backstage/plugin-events-backend@0.5.10`
- `- @backstage/plugin-search-backend@2.0.10`
- `- @backstage/plugin-search-backend-module-techdocs@0.4.10`
- `- @backstage/cli-common@0.1.17`
- `- @backstage/create-app@0.7.8`
- `- Updated dependencies - @backstage/frontend-plugin-api@0.13.3 - @backstage/plugin-scaffolder-react@1.19.5`
- `- Updated dependencies - @backstage/ui@0.11.0`
- `- @backstage/plugin-catalog@1.32.2`
- `- @backstage/cli@0.35.2`
- `- @backstage/core-components@0.18.5`
- `- @backstage/plugin-techdocs@1.16.2`
- `- @backstage/app-defaults@1.7.4`
- `- @backstage/integration-react@1.2.14`
- `- @backstage/plugin-techdocs-react@1.3.7`
- `@internal/plugin-todo-list@1.0.47 Patch Changes - Updated dependencies - @backstage/core-components@0.18.5`
- `- @backstage/frontend-plugin-api@0.13.3`
- `- @backstage/core-components@0.18.5`
- `- @backstage/plugin-catalog-react@1.21.5`

## Other changes (45)

- `GithubOrgEntityProvider` fetches only the specific user's teams for membership events
- Hard refreshes fixed for internal `Link` routes
- Table overflow styling moved to a wrapper
- Skeleton background colors adjust for neutral surfaces
- Switch colors adapt to parent backgrounds
- Dark-mode `--bui-fg-disabled` color changed to `#707070`
- Tab indicators track changes in tab width
- Header breadcrumb typography preserved across stylesheet load orders
- `@backstage/no-deprecated-bui-tokens` rule added to the recommended ESLint config
- Action file fetching uses `resolveSafeChildPath` with changed symlink handling
- Root health service shutdown response spelling corrected
- App background color fixed in dark mode
- Accessibility warnings fixed for SearchField components
- Disabled state fixed for primary and secondary Backstage UI buttons
- Disabled tertiary buttons no longer show hover effects on surfaces
- Disabled tertiary button hover effects on surfaces fixed
- Table sorting indicator visibility fixed
- Menu trigger button toggle behavior fixed
- SearchField collapsed behavior and layout styling fixed
- Internal routes in the `Link` component now use React Router
- Table selection-cell border styles restored
- WidgetOverlay background color follows the theme
- `@backstage/backend-openapi-utils` uses native base path determination
- Some symlink resolution moved to `isChildPath` in `@backstage/cli-common`
- Table toolbar layout fixed
- `ItemCardHeader` colour token now respects the theme definition
- Clarified `createApiRef` documentation on API ownership IDs
- GitHub integration config lowercase-replacement behavior rolled back
- Help text fixed for the `backstage-repo-tools` `schema openapi generate` command
- Fixed types in `@backstage/plugin-api-docs`
- Updated metadata for `@backstage/plugin-app-backend`
- Metadata updated for `@backstage/plugin-app-node`
- EntityLayout header stays visible during Async Entity refresh
- MS Graph catalog backend photo load failures logged at debug level
- Installation command for `@backstage/plugin-mui-to-bui` fixed
- `--bui-bg` token renamed to `--bui-bg-surface-0`
- Resources included by default in group ownership cards
- Repository name autocomplete fixed in `RepoUrlPickerComponent`
- Unused abort controller removed from the `debug:wait` action
- 27f9061: REwrite]
- README setup and usage guidance clarified
- Grid card and table colors corrected
- TechDocs code-block copy button positioning corrected
- TechDocs AWS publisher options marked `@visibility backend`
- 404s for slash-containing user setting keys fixed

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
