Security fixes for Software Templates and external content reading
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
Security 2Breaking changes 25Deprecations 9Important fixes 10Enhancements 34Dependency updates 258Other changes 45
Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.
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: https://backstage.github.io/upgrade-helper/?to=1.47.0github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
This release contains security fixes for Software Templates and reading external content.github.com/backstage/backstage/releases/tag/v1.47.0
coreServices.urlReadercoreServices.urlReaderPreviously, 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]github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/ui colors and removed -tint tokens@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).github.com/backstage/backstage/releases/tag/v1.47.0
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 chaingithub.com/backstage/backstage/releases/tag/v1.47.0
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 changesgithub.com/backstage/backstage/releases/tag/v1.47.0
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.
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
.bui-SelectPopoverPreviously, 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.ui.backstage.io/changelog
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. #34567ui.backstage.io/changelog
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. #34591ui.backstage.io/changelog
--bui-bg-app and --bui-bg-neutral-1 through --bui-bg-neutral-4 in light or dark themesExisting 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.ui.backstage.io/changelog
--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-disabledgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
--bui-bg renamed to --bui-bg-surface-0--bui-bg(Inferred)- 4ea1d15: BREAKING : Renamed CSS variable --bui-bg to --bui-bg-surface-0 for consistency.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
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.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- f0951aa: Updated the defaultDockerImage to reflect the latest TechDocs Container version of v1.2.8github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/ui Table wrapper renamed and useTable redesignedTable 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).github.com/backstage/backstage/releases/tag/v1.47.0
coreServices.urlReader checks redirect chains against the allow listcoreServices.urlReader(Inferred)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.github.com/backstage/backstage/releases/tag/v1.47.0
FetchUrlReader public constructor removedFetchUrlReader directly(Inferred)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
@backstage/plugin-app-reactapp plugin, an app plugin override or a module with pluginId set to app is required.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`github.com/backstage/backstage/releases/tag/v1.47.0
ComboboxProps becomes a union typeComboboxPropsArray-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 .ui.backstage.io/changelog
SelectProps changed to a union typeSelectPropsSelectPropsCustom 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 ;
+ };ui.backstage.io/changelog- 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, TableRoot, TablePagination, or useTable from @backstage/uiuseTable 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, TablePaginationgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md@backstage/frontend-plugin-api@backstage/frontend-plugin-api(Inferred)- 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
integrations.awsS3(Inferred)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 TechDocsgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@swc/core version raised@backstage/cli with an @swc/core version below the new minimum(Inferred)- 9ee5996: Bump minimum required @swc/core to avoid transpilation buggithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/plugin-catalog-graph sets a high array limit@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.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
FetchUrlReader constructor made privateFetchUrlReader directlyFetchUrlReader.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.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
app plugin deprecatedapp pluginThis 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.github.com/backstage/backstage/releases/tag/v1.47.0
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.github.com/backstage/backstage/releases/tag/v1.47.0
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 .ui.backstage.io/changelogThe 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 .ui.backstage.io/changelog
id recommended for plain Select optionsArray-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 .ui.backstage.io/changelog
search configurationsearchable, searchPlaceholder, or nested searchThe 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' }} />ui.backstage.io/changelogTheir 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 |ui.backstage.io/changelog
-hover, -pressed, or -disabled variantsThe 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.ui.backstage.io/changelog
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 - TranslationBlueprintgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
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 . #34469ui.backstage.io/changelog
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 MarkdownMarkdownContent 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 Markdowngithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
GithubOrgEntityProviderGithubOrgEntityProvider 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 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
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
Combobox crash with searchable plain options fixedCombobox setups with plain options and client-side search under react-aria-components 1.17The 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. #34590ui.backstage.io/changelog
user_created_at migration fixeduser_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 defaultsgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@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 leaksgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/plugin-catalog-backend-module-puppetdbThe 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 undefinedgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
ActionsServiceTo 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
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.0To 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
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
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 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 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
NumberField component added to @backstage/ui- Added a new NumberField component for numeric input with support for min, max, step, and keyboard increment/decrement. #34264ui.backstage.io/changelog
@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
- 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 GoogleGcsReadergithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
ToggleButton and ToggleButtonGroup components in Backstage UI- ea0c6d8: Introduce new ToggleButton & ToggleButtonGroup components in Backstage UIgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- d2fdded: Added indeterminate state support to the Checkbox component for handling partial selection scenarios like table header checkboxes. Affected components: Checkboxgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
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
--bui-shadow elevation token133d5c6: 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
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, Columngithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
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, TablePaginationgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
className and style props- 2532d2a: Added className and style props to the Table component. Affected components: Tablegithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@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
- 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 systemgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/plugin-events-backend-module-kafka@0.3.0 Minor Changes - ef5bbd8: Add support for Kafka offset configuration ( fromBeginning ) and autoCommitgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
fromBeginning and autoCommitTo use Kafka offset configuration using fromBeginning and autoCommit
- ef5bbd8: Add support for Kafka offset configuration ( fromBeginning ) and autoCommitgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- ab606b2: Add ability to configure the API Base URLgithub.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 ES2024github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
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
@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
- f1fe6fe: Updated Dockerfile to use Node 24 and Debian Trixiegithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
PluginWrapperBlueprint for wrapping plugin elementsTo 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
ScmIntegration implementation added- 3afeab4: Implementing ScmIntegration for GoogleGcsgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
PluginWrapperBlueprint in @backstage/plugin-appTo 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
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
- 4452d15: Added i18n support.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
github:repo:create repositoriesTo 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: organizationgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
GithubOrgEntityProvider fetches only the specific user's teams for membership events`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
Link routes### `Link` component now uses React Router’s navigation system Previously the `Link` component would cause hard page refreshes for internal routes. With this update, the component now properly uses React Router’s navigation instead of full page reloads.github.com/backstage/backstage/releases/tag/v1.47.0
- Fixed the Table component not filling its container width in Firefox. The overflow style is now applied to a wrapper element instead of the <table> element directly, which avoids a Firefox behavior where non-visible overflow on tables causes them to shrink-wrap to content size. #34539ui.backstage.io/changelog
- Skeleton Make Skeleton component background aware, automatically adjusting its color to maintain visible contrast against neutral parent surfaces. #34582ui.backstage.io/changelog
- Switch Switch now adapts its track and thumb colors based on the background context of its parent container, and uses the accent token family when selected. #34455ui.backstage.io/changelog
--bui-fg-disabled color changed to #707070Switch Switch now adapts its track and thumb colors based on the background context of its parent container, and uses the accent token family when selected. #34455ui.backstage.io/changelog
- Fixed tab indicator not updating position when tab content changes width dynamically. #34557ui.backstage.io/changelog
- Header Fixed Header breadcrumb typography so it remains consistent when component styles are loaded in different orders. #34448ui.backstage.io/changelog
@backstage/no-deprecated-bui-tokens rule added to the recommended ESLint configThe previous tokens remain in place for backward compatibility but are now deprecated and will be removed in a future release. #34400ui.backstage.io/changelog
resolveSafeChildPath with changed symlink handling- c641c14: Wrap some of the action logic with resolveSafeChildPath and improve symlink handling when fetching remote and local files - c641c14: Wrap some of the action logic with resolveSafeChildPath and improve symlink handling when fetching remote and local files - c641c14: Wrap some of the action logic with resolveSafeChildPath and improve symlink handling when fetching remote and local filesgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 7126bf2: Fixed a spelling mistake in root health service shutdown response.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 1880402: Fixes app background color on dark mode.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 4fb15d2: Added missing aria-label attributes to SearchField components in Select , MenuAutocomplete , and MenuAutocompleteListbox to fix accessibility warnings. Affected components: Select, MenuAutocomplete, MenuAutocompleteListboxgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 21c87cc: Fixes disabled state in primary and secondary buttons in Backstage UI.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- de80336: Fixed disabled tertiary buttons incorrectly showing hover effects on surfaces.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- de80336: Fixed disabled tertiary buttons incorrectly showing hover effects on surfaces. -github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 973c839: Fixed Table sorting indicator not being visible when a column is actively sorted. Affected components: Table, Columngithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- df40cfc: Fixed Menu component trigger button not toggling correctly. Removed custom click-outside handler that was interfering with React Aria's built-in state management, allowing the menu to properly open and close when clicking the trigger button.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- b4a4911: Fixed SearchField startCollapsed prop not working correctly in Backstage UI. The field now properly starts in a collapsed state, expands when clicked and focused, and collapses back when unfocused with no input. Also fixed CSS logic to work correctly in all layout contexts (flex row, flex column, and regular containers). Affected components: SearchFieldgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
Link component now use React Router- b3253b6: Fixed Link component causing hard page refreshes for internal routes. The component now properly uses React Router's navigation instead of full page reloads.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- cfac8a4: Fixed missing border styles on table selection cells in multi-select mode. Affected components: Tablegithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- bdda543: Updated WidgetOverlay color to use alpha(theme.palette.background.paper, 0.93) for better theme alignment instead of hardcoded RGBAgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/backend-openapi-utils uses native base path determination@backstage/backend-openapi-utils@0.6.5 Patch Changes - 6678b78: Internal update to use native feature from our request validation library for handling base path determination.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
isChildPath in @backstage/cli-common@backstage/cli-common@0.1.17 Patch Changes - ae4dd5d: Move some of the symlink resolution to isChildPath - ae4dd5d: Move some of the symlink resolution to isChildPathgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- c671db9: Fixed bug in Table component where the toolbar layout would break when both a title and filters were present.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
ItemCardHeader colour token now respects the theme definition- 55a9dc2: Update colour token again in ItemCardHeader to respect theme definition.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
createApiRef documentation on API ownership IDs- 3bd2a1a: Updated documentation for createApiRef to clarify the role of the ID in specifying the owning plugin of an API.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 9083273: Rollback the lowercase replacing in GitHub integration configgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
backstage-repo-tools schema openapi generate command- 498f9dd: Fixed help text for backstage-repo-tools package schema openapi generate command.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/plugin-api-docs- abeba2b: Fix types with new bumped dependencygithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/plugin-app-backend- 9ccf84e: Updated plugin metadata.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/plugin-app-node- 9ccf84e: Updated plugin metadata.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 7ca91e8: Header in EntityLayout should always be shown. Monitoring the loading status caused flickering when the refresh() method of the Async Entity was invoked.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/plugin-catalog-backend-module-msgraph@0.8.4 Patch Changes - 115b378: Changed the logger level from 'warning' to 'debug' when we are unable to load the user's photo.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@backstage/plugin-mui-to-bui fixed- f157f43: Fix installation commandgithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
--bui-bg token renamed to --bui-bg-surface-0- e4a1180: Updated tokens from --bui-bg to --bui-bg-surface-0github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- db3cfd7: Adds the Resource kind to the useGetEntities fallback so that Resources are included by default when no specific kinds are provided in the group ownership card.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
RepoUrlPickerComponent- 9d75495: Fixed bug in RepoUrlPickerComponent component where repository names were not being autocompleted.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
debug:wait action- 5012852: Remove unused abort controller in debug:wait actiongithub.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 88abcc6: Improved README with clearer setup and usage guidance.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 0afb8a6: Corrected color of some elements such as Grid cards and Tables.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- 94ff7ab: Code block "Copy to clipboard" button was not positioned correctly for docs built with mkdocs-material>=9.7github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
@visibility backend- b6ff2a5: Some AWS publisher config options such as region , endpoint , accountId are now marked as @visibility backend instead of secret .github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
- ad01e54: Resolves an issue where user setting keys containing slashes returned 404 not found.github.com/backstage/backstage/tree/master/docs/releases/v1.47.0-changelog.md
Summaries are produced by AI, so they can be wrong, and they are provided without warranty.