RATATOSK
← All releases

Backstagev1.47.0

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

Get Backstage alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Upgrade guide2
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).
github.com/backstage/backstage/releases/tag/v1.47.0
Upgrade Helper for upgrading to v1.47.0
Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.47.0
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

Security2

Security fixes for Software Templates and external content reading

Affectssetups using Software Templates or reading external content
Show release-note lines
This release contains security fixes for Software Templates and reading external content.
github.com/backstage/backstage/releases/tag/v1.47.0

Redirect allow-list validation added to coreServices.urlReader

Affectssetups 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.

Show release-note lines
-
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]
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

Breaking changes25

Updated @backstage/ui colors and removed -tint tokens

Affectssetups 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.

Show release-note lines
### 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).
github.com/backstage/backstage/releases/tag/v1.47.0

TechDocs AWS S3 authentication priority changed

AffectsTechDocs 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.

Show release-note lines
### 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
github.com/backstage/backstage/releases/tag/v1.47.0

Home plugin widget configuration requires explicit Save

Affectswidget configuration in the home plugin UI(Inferred)

The new Cancel button discards unsaved changes.

Show release-note lines
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
github.com/backstage/backstage/releases/tag/v1.47.0

Custom homepage widget configuration now saves only on Save

Affectscustom 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.” backstage/backstage/pull/31198 ↗
Show release-note lines
Contributed by [@kmikko](https://github.com/kmikko) in [#31198](https://github.com/backstage/backstage/pull/31198)
github.com/backstage/backstage/releases/tag/v1.47.0

Select popover list content wrapper changed

AffectsSelect implementations or stylesheets relying on list content being a direct child of .bui-SelectPopover
Action requiredCSS 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.

Show release-note lines
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.
ui.backstage.io/changelog

Dark-theme neutral background tokens updated

Affectssetups 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.

Show release-note lines
-
Updated the dark theme neutral background tokens to provide clearer contrast between neutral surfaces. #34567
ui.backstage.io/changelog

Searchable Select layout and theme classes updated

AffectsSearchable 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.

Show release-note lines
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
ui.backstage.io/changelog

Background token color values updated

Affectsuse of --bui-bg-app and --bui-bg-neutral-1 through --bui-bg-neutral-4 in light or dark themes
Action requiredNo token renaming is required.

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

Show release-note lines
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.
ui.backstage.io/changelog

Backstage UI background tokens shifted to neutral colors

AffectsBackstage 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.

Show release-note lines
-
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
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

Backstage home widget configurations now require explicit saving

AffectsBackstage home widget configurations(Inferred)

Cancel discards unsaved edits and restores the last saved state.

Show release-note lines
- 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.
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

@backstage/ui Table wrapper renamed and useTable redesigned

AffectsTable 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.

Show release-note lines
### 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).
github.com/backstage/backstage/releases/tag/v1.47.0

coreServices.urlReader checks redirect chains against the allow list

AffectsApp configurations using coreServices.urlReader(Inferred)
Action requiredRedirected-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.

Show release-note lines
`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.
github.com/backstage/backstage/releases/tag/v1.47.0

FetchUrlReader public constructor removed

Affectssetups or integrations that instantiate FetchUrlReader directly(Inferred)
Show release-note lines
To support this, the `FetchUrlReader` class no longer has a public constructor, but instead has a `fromConfig` static factory method.
github.com/backstage/backstage/releases/tag/v1.47.0

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

AffectsSetups that use one or more of the seven listed blueprints for app customization(Inferred)
Action requiredFor use outside the app plugin, an app plugin override or a module with pluginId set to app is required.
Removed innot stated

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

Show release-note lines
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`
github.com/backstage/backstage/releases/tag/v1.47.0

ComboboxProps becomes a union type

AffectsCombobox setups needing async collections, incremental loading, client or server search, or rich or custom item rendering
Action requiredType 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.

Show release-note lines
-
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 .
ui.backstage.io/changelog

SelectProps changed to a union type

AffectsTypeScript declarations extending SelectProps
Action requiredType intersections in place of interfaces extending SelectProps

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

Show release-note lines
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 ;
+ };
ui.backstage.io/changelog

Plugin API overrides limited to the owning plugin

Affectsplugins that override APIs belonging to another plugin(Inferred)
Action requiredOverrides of core APIs provided by the app plugin must instead be done with an app module.
Show release-note lines
- 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.
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

Table and useTable APIs redesigned

Affectssetups using Table, TableRoot, TablePagination, or useTable from @backstage/ui
Action requiredUpdate 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.

Show release-note lines
@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
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

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

Affectssetups importing the listed blueprints from @backstage/frontend-plugin-api(Inferred)
Show release-note lines
-
9ccf84e: Moved the following blueprints from @backstage/frontend-plugin-api :
- AppRootWrapperBlueprint
- IconBundleBlueprint
- NavContentBlueprint
- RouterBlueprint
- SignInPageBlueprint
- SwappableComponentBlueprint
- ThemeBlueprint
- TranslationBlueprint
-
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

TechDocs AWS S3 integration credentials supported

AffectsTechDocs AWS S3 publishers configured with integrations.awsS3(Inferred)
Action requiredA 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.

Show release-note lines
-
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
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

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

Affectssetups 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.

Show release-note lines
- 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.
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

FetchUrlReader constructor made private

Affectscode that constructs FetchUrlReader directly
Action requiredUse FetchUrlReader.fromConfig instead of the now-private constructor
Show release-note lines
- 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.
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

Deprecations9

Blueprint use outside the app plugin deprecated

Affectssetups using these blueprints outside the app plugin
Removed innot 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.

Show release-note lines
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.
github.com/backstage/backstage/releases/tag/v1.47.0

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

AffectsFactory overrides for other plugins' Utility APIs, including core APIs provided by the app plugin
Removed innot 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.

Show release-note lines
### 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.
github.com/backstage/backstage/releases/tag/v1.47.0

Top-level Combobox input state props deprecated

AffectsCombobox setups controlling input state or custom filtering
Removed innot 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.

Show release-note lines
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 .
ui.backstage.io/changelog

Select gains async collections, search, and custom item rendering

AffectsSelect setups using async collections, client/server search, or rich and custom item rendering(Inferred)
Removed innot stated

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

Show release-note lines
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 .
ui.backstage.io/changelog

id recommended for plain Select options

Affectsplain options in Select
Removed innot stated

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

Show release-note lines
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 .
ui.backstage.io/changelog

Select search props deprecated in favor of nested search configuration

AffectsSelect search configured with searchable, searchPlaceholder, or nested search
Removed innot 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.

Show release-note lines
Replace searchable and searchPlaceholder with nested search configuration:
- < Select searchable searchPlaceholder = "Search owners" />
+ < Select search = {{ placeholder : 'Search owners' }} />
ui.backstage.io/changelog

Legacy color tokens deprecated

Affectssetups referencing the legacy color tokens listed in the migration mappings
Removed innot stated

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

Show release-note lines
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 |
ui.backstage.io/changelog

Neutral background interaction variants deprecated

Affectsneutral background tokens with -hover, -pressed, or -disabled variants
Removed innot stated

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

Show release-note lines
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.
ui.backstage.io/changelog

App blueprints moved and deprecated

Affectsuses of the eight blueprints outside app plugin overrides or modules
Removed innot 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.

Show release-note lines
-
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
github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

Important fixes10

  • Header tab links now respect the router basename
    AffectsBackstage 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
    ui.backstage.io/changelog
  • CSS module class-name collisions fixed with content-based hashing
    Affectssetups 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.
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • MarkdownContent now matches GitHub when rendering HTML in GitHub-flavored Markdown
    AffectsMarkdownContent 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
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • More targeted team fetching and entity updates in GithubOrgEntityProvider
    Affectssetups 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.
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • GithubOrgEntityProvider avoids unnecessary entity deletions during edit handling
    AffectsSetups 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.
    github.com/backstage/backstage/releases/tag/v1.47.0
  • Async pagination scrolling fixed in Combobox and Select popovers
    Affectssetups 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.
    ui.backstage.io/changelog
  • BUI Combobox crash with searchable plain options fixed
    AffectsBUI 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
    ui.backstage.io/changelog
  • SQLite error in user_created_at migration fixed
    Affectsuser_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
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Backend stop now cleans up process event listeners
    Affectsbackends 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
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • PuppetDB catalog backend crash fixed
    Affectsinstallations 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
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

Enhancements34

  • Configurable action filtering in ActionsService

    To use Configure actions.filter with include and/or exclude rules to filter exposed actions.

    `ActionsService` in `@backstage/backend-defaults` now supports action filtering based on configuration to enable control over which actions are exposed to consumers like the MCP backend.
    At the time of writing, this is primarily documented in [the relevant configuration schema](https://github.com/backstage/backstage/blob/master/packages/backend-defaults/config.d.ts).
    github.com/backstage/backstage/releases/tag/v1.47.0
  • Configurable GitHub Actions workflow access for repository creation

    To use workflowAccess configured in the github:repo:create action input; the example uses organization.

    ### `scaffolder` now supports configuration for `workflowAccess` level for creating Github repositories
    Workflow files can now configure the level of access to Github Actions for workflows outside of a repository.
    This is useful when creating repositories for GitHub Actions to manage access to the workflows for `github:repo:create`.
    ```diff
       - action: github:repo:create
          id: create-repo
          input:
            repoUrl: github.com?owner=owner&repo=repo
            visibility: private
    +       workflowAccess: organization
    ```
    Github Actions access-level documentation can be found [here](https://docs.github.com/en/rest/actions/permissions?apiVersion=2022-11-28#set-the-level-of-access-for-workflows-outside-of-the-repository).
    github.com/backstage/backstage/releases/tag/v1.47.0
  • Kafka consumers can start from the earliest message

    To use Set fromBeginning: true to start at the earliest available message; the default is false.

    The Kafka event module now supports `fromBeginning` offsets and `autoCommit`.
    github.com/backstage/backstage/releases/tag/v1.47.0
  • Configurable Kafka offset commits

    To use Set autoCommit to false for manual commits.

    The Kafka event module now supports `fromBeginning` offsets and `autoCommit`.
    github.com/backstage/backstage/releases/tag/v1.47.0
  • Kafka consumers can pause after processing errors

    To use Set pauseOnError: true to enable the behavior.

    The Kafka event module now supports `fromBeginning` offsets and `autoCommit`.
    github.com/backstage/backstage/releases/tag/v1.47.0
  • Combobox loading and stale-result styling hooks exposed
    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 .
    ui.backstage.io/changelog
  • Select loading and stale-result styling hooks added
    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 .
    ui.backstage.io/changelog
  • Numeric NumberField component added to @backstage/ui
    -
    Added a new NumberField component for numeric input with support for min, max, step, and keyboard increment/decrement. #34264
    ui.backstage.io/changelog
  • Expanded @backstage/ui color token set
    -
    Introduces a new set of semantic color token families — Accent, Announcement, Warning, Negative, and Positive — each providing a consistent set of background, foreground, and border tokens for both light and dark themes. A gray scale ( --bui-gray-1 through --bui-gray-11 ) and updated foreground tokens are also included.
    ui.backstage.io/changelog
  • Configurable action filtering in ActionsService
    -
    6fc00e6: Added action filtering support with glob patterns and attribute constraints.
    The ActionsService now supports filtering actions based on configuration. This allows controlling which actions are exposed to consumers like the MCP backend.
    Configuration example:
    backend :
    actions :
    pluginSources :
    - catalog
    - scaffolder
    filter :
    include :
    - id : ' catalog:* '
    attributes :
    destructive : false
    - id : ' scaffolder:* '
    exclude :
    - id : ' *:delete-* '
    - attributes :
    readOnly : false
    Filtering logic:
    - include : Rules for actions to include. Each rule can specify an id glob pattern and/or attributes constraints. An action must match at least one rule to be included. If no include rules are specified, all actions are included by default.
    - exclude : Rules for actions to exclude. Takes precedence over include rules.
    - Each rule combines id and attributes with AND logic (both must match if specified).
    -
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • GoogleGcsReader adds readTree support
    - 3afeab4: Implementing readTree for GoogleGcsReader
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • New ToggleButton and ToggleButtonGroup components in Backstage UI
    -
    ea0c6d8: Introduce new ToggleButton & ToggleButtonGroup components in Backstage UI
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Indeterminate state support for the Checkbox component
    -
    d2fdded: Added indeterminate state support to the Checkbox component for handling partial selection scenarios like table header checkboxes.
    Affected components: Checkbox
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Backstage UI adds a Popover component
    133d5c6: Added new Popover component for Backstage UI with automatic overflow handling, and full placement support. Also introduced --bui-shadow token for consistent elevation styling across overlay components (Popover, Tooltip, Menu).
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • New --bui-shadow elevation token
    133d5c6: Added new Popover component for Backstage UI with automatic overflow handling, and full placement support. Also introduced --bui-shadow token for consistent elevation styling across overlay components (Popover, Tooltip, Menu).
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Responsive width controls for Table columns

    To use Use the width, defaultWidth, minWidth, and/or maxWidth props on Table columns to configure column widths.

    -
    b01ab96: Added support for column width configuration in Table component. Columns now accept width , defaultWidth , minWidth , and maxWidth props for responsive layout control.
    Affected components: Table, Column
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Configurable pagination for useTable and Table
    -
    fe7fe69: Added support for custom pagination options in useTable hook and Table component. You can now configure pageSizeOptions to customize the page size dropdown, and hook into pagination events via onPageSizeChange , onNextPage , and onPreviousPage callbacks. When pageSize doesn't match any option, the first option is used and a warning is logged.
    Affected components: Table, TablePagination
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Table accepts className and style props
    -
    2532d2a: Added className and style props to the Table component.
    Affected components: Table
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Initial release of the @backstage/plugin-app-react web library
    - 9ccf84e: Initial release of this web library for @backstage/plugin-app .
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • New Frontend support for additional Devtools tabs
    - be6cef5: Add support for adding unprocessed-entities and other tabs to devtools when using the New Frontend system
    - be6cef5: Add support for adding unprocessed-entities and other tabs to devtools when using the New Frontend system
    - be6cef5: Add support for adding unprocessed-entities and other tabs to devtools when using the New Frontend system
    - be6cef5: Add support for adding unprocessed-entities and other tabs to devtools when using the New Frontend system
    - be6cef5: Add support for adding unprocessed-entities and other tabs to devtools when using the New Frontend system
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Kafka offset configuration added to the events backend module
    @backstage/plugin-events-backend-module-kafka@0.3.0
    Minor Changes
    - ef5bbd8: Add support for Kafka offset configuration ( fromBeginning ) and autoCommit
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Kafka offset configuration with fromBeginning and autoCommit

    To use Kafka offset configuration using fromBeginning and autoCommit

    - ef5bbd8: Add support for Kafka offset configuration ( fromBeginning ) and autoCommit
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Configurable API Base URL for the Sentry scaffolder backend
    - ab606b2: Add ability to configure the API Base URL
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • @swc/core adds ES2023 and ES2024 transpilation support
    - 320c6a9: Bump @swc/core to support ES2023 and ES2024
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Package inclusion and output format options for backstage-cli info
    - c0d7bf6: Added --include and --format options to backstage-cli info command for including additional packages via glob patterns and outputting as JSON or Text.
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • @backstage/backend-test-utils added to backend package templates
    - 140cbc2: Added @backstage/backend-test-utils to backend package templates.
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Updated @backstage/create-app to 0.7.8
    - fea3e39: Bumped create-app version.
    - 9f1ee3e: Bumped create-app version.
    - 880310b: Bumped create-app version.
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • create-app Dockerfile updated for Node 24 and Debian Trixie
    - f1fe6fe: Updated Dockerfile to use Node 24 and Debian Trixie
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Alpha PluginWrapperBlueprint for wrapping plugin elements

    To use the alpha export from @backstage/frontend-plugin-api/alpha

    -
    4554a4e: Added an alpha PluginWrapperBlueprint exported from @backstage/frontend-plugin-api/alpha , which can install components that will wrap all plugin elements.
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • GoogleGcs ScmIntegration implementation added
    - 3afeab4: Implementing ScmIntegration for GoogleGcs
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Support for PluginWrapperBlueprint in @backstage/plugin-app

    To use PluginWrapperBlueprint from @backstage/frontend-plugin-api/alpha

    -
    4554a4e: Implemented support for the new PluginWrapperBlueprint from @backstage/frontend-plugin-api/alpha .
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Custom start URL search parameters for the OIDC provider

    To use startUrlSearchParams config property

    - e54fcb2: Added support for custom start URL search parameters (with the new startUrlSearchParams config property)
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
  • Notifications plugin adds i18n support
  • Workflow access level option for github:repo:create repositories

    To use workflowAccess input

    -
    bb7088b: Added options to set workflow access level for repositories to github:repo:create
    This is useful when creating repositories for GitHub Actions to manage access
    to the workflows during creation.
    - action: github:repo:create
    id: create-repo
    input:
    repoUrl: github.com?owner=owner&repo=repo
    visibility: private
    + workflowAccess: organization
    github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md

Dependency updates258

    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 changes45

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