Skip to main content

Release v1.57.0

Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.57.0

@backstage/frontend-app-api@1.0.0​

Major Changes​

  • b3befd0: Released version 1.0 of this frontend framework package. Its public APIs are now stable under the package versioning policy. Alpha and beta APIs retain their existing stability levels.

Minor Changes​

  • 8c6c842: BREAKING: Removed the deprecated createSpecializedApp and CreateSpecializedAppOptions exports. Use prepareSpecializedApp(options).finalize() and PrepareSpecializedAppOptions instead. For sign-in or asynchronous session preparation, render the bootstrap app and subscribe with onFinalized() instead of calling finalize().

    Replace advanced.apis with advanced.sessionState from a previously finalized app to reuse its APIs, identity, and predicate context. Register custom APIs through ApiBlueprint extensions rather than passing an arbitrary API holder. Pass a supplied config API through the top-level config option. To reuse an identity supplied through the API holder, configure a sign-in page that calls onSignInSuccess(identityApi) and use the bootstrap/onFinalized() flow; an ApiBlueprint cannot override the app's identity proxy.

Patch Changes​

  • d514e4d: Updated app options to use the ExtensionFactoryMiddleware type from @backstage/frontend-app-api instead of the deprecated export from @backstage/frontend-plugin-api. Middleware behavior is unchanged.

  • e55a4a8: Updated plugin identity handling to use pluginId, while preserving support for older plugin instances that only expose id.

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

  • 9d0a31b: Removed an unused use-sync-external-store dependency, which is no longer needed now that React 18 is the minimum supported version.

  • c147b7a: Fixed disabled external route bindings falling back to their default targets during link resolution.

    Navigation analytics now use the most specific routed extension even when it has no route reference, including nested extensions with an empty path.

  • 2aa14e3: The new frontend system now owns app history independently of page routing libraries, so page matching, route references, and navigation analytics use the same location and route hierarchy. Href creation and navigation require app-absolute paths starting with /, excluding the deployment basename, and custom factories for coreApis.appHistory must be available during initialization without an if predicate. See the 1.57 migration notes for detailed migration steps.

    Query and state synchronization through direct browser history replacements stays silent across rerenders. In browsers with the Navigation API, third-party pushes and replacements that change the pathname or hash are still reported as navigation.

  • Updated dependencies

    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/frontend-defaults@0.5.8
    • @backstage/errors@1.4.0
    • @backstage/core-app-api@1.20.7
    • @backstage/version-bridge@1.1.0
    • @backstage/config@1.3.11
    • @backstage/filter-predicates@0.2.1

@backstage/frontend-dev-utils@1.0.0​

Major Changes​

  • b3befd0: Released version 1.0 of this frontend framework package. Its public APIs are now stable under the package versioning policy. Alpha and beta APIs retain their existing stability levels.

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/plugin-app@0.6.0
    • @backstage/frontend-defaults@0.5.8
    • @backstage/ui@0.20.0

@backstage/frontend-plugin-api@1.0.0​

Major Changes​

  • b3befd0: Released version 1.0 of this frontend framework package. Its public APIs are now stable under the package versioning policy. Alpha and beta APIs retain their existing stability levels.

Minor Changes​

  • 5a539ca: BREAKING: The pluginId property of plugins passed as a FrontendFeature is now required. Plugins built against framework versions that predate pluginId must be rebuilt against a current version.

  • 6540a44: BREAKING: useApi now unwraps promise-valued APIs, suspending while pending and throwing rejection reasons to an error boundary. Its return type is Awaited<T>. Existing consumers that intentionally used the promise returned by useApi must use a direct holder lookup instead.

    Declare lazy implementations with ApiRef<Promise<MyApi>>. API holders, factories, and dependencies keep their existing contracts and pass the declared value through unchanged.

    See the Utility API documentation for lazy implementations, Suspense boundaries, and migration requirements.

  • d514e4d: BREAKING: Removed the deprecated ExtensionFactoryMiddleware type export. Import it from @backstage/frontend-app-api instead:

    -import type { ExtensionFactoryMiddleware } from '@backstage/frontend-plugin-api';
    +import type { ExtensionFactoryMiddleware } from '@backstage/frontend-app-api';

    Add @backstage/frontend-app-api as a dependency of your app package if it is not already declared. Middleware behavior is unchanged.

  • 0a552cf: BREAKING: Removed the ExtensionAttachTo type export. Use Extension<unknown>['attachTo'] if you need to reference the attachment type.

  • 62268a9: BREAKING: Removed the AnalyticsImplementation type and the deprecated AnalyticsImplementationBlueprint and AnalyticsImplementationFactory exports. Import them from @backstage/plugin-app-react instead. No changes to their usage are needed beyond updating the imports.

  • 86ff5a3: Removed the deprecated PageTab and PluginOptions types. Use PageLayoutTab and CreateFrontendPluginOptions instead.

  • 8ae0b8e: BREAKING: Removed the deprecated IconComponent export. Use IconElement and pass <MyIcon /> rather than MyIcon when working with icons in the new frontend system. Legacy integrations that still need a component type can import IconComponent from @backstage/core-plugin-api. Auth provider icons continue to accept components with the same optional fontSize prop.

  • 806a9cf: BREAKING: Removed the /alpha entry point. All of its exports are already available from @backstage/frontend-plugin-api; update imports to use the main entry point instead:

    -import { PluginWrapperBlueprint } from '@backstage/frontend-plugin-api/alpha';
    +import { PluginWrapperBlueprint } from '@backstage/frontend-plugin-api';

    The exported APIs retain the same behavior and identity. For the deprecated pluginWrapperApiRef, prefer coreApis.internal.pluginWrapper from the main entry point.

  • dafdab8: BREAKING: Removed the deprecated withApis export. Wrap class components in a function component that uses useApi instead:

    import { errorApiRef, useApi } from '@backstage/frontend-plugin-api';
    import { MyClassComponent, MyClassComponentProps } from './MyClassComponent';

    export function MyComponent(props: Omit<MyClassComponentProps, 'errorApi'>) {
    const errorApi = useApi(errorApiRef);
    return <MyClassComponent {...props} errorApi={errorApi} />;
    }
  • 0f2ffc9: BREAKING: Removed the ProgressProps type. Replace imports and usages of this type with its existing shape, {}. The Progress component and its props contract are unchanged.

  • a5b3445: Added router-independent navigation and routing APIs: RouterLink, AppHistoryApi (also available as coreApis.appHistory), useAppNavigate, useAppHref, useAppLocation, useAppSearchParams, and RouteResolutionApi.resolvePath for matched routing ancestry. BREAKING: useRouteRefParams returns only parameters declared by the supplied route ref, with undefined for unmatched parameters, and no longer includes the splat *. See the 1.57 migration notes for detailed migration steps.

    The stable public /routing entry point exposes RoutingProvider, RoutingIntegration, and useRoutingIntegration for router and component-library integrations. It has the same stability and compatibility guarantees as the main entry point; app history APIs, plugin navigation hooks, and route refs remain in the main entry point. AppNavigate describes the navigation function returned by useAppNavigate.

  • e55a4a8: BREAKING: Removed the deprecated FrontendPlugin.id property from the public interface. Use pluginId instead. The runtime alias is retained for compatibility with older apps.

  • 7285912: BREAKING PRODUCERS: TranslationSnapshot now requires t even when ready is false. Custom TranslationApi implementations must provide a translator using available messages and language fallbacks.

  • d84cf73: Removed the deprecated DialogApi.show, DialogApi.showModal, and IconsApi.getIcon methods. Use DialogApi.open with your own dialog presentation, and IconsApi.icon to retrieve icon elements.

    The API references now use core.dialog.v2 and core.icons.v2. Upgrade @backstage/plugin-app alongside this package, and update custom API implementations to use the new references.

Patch Changes​

  • ca02018: API reference IDs now use plugin ID validation for each dot-separated component. This accepts numeric dash groups and mixed case, including IDs such as plugin.example-2.todos.

  • ac2de0f: Fixed a "Type instantiation is excessively deep and possibly infinite" error from createFrontendPlugin in plugins with many extensions, in particular with TypeScript 5.9 and later. In rare cases, the extensions in the type of a plugin may be in a different order or include extensions that were missing before.

  • d5e1d51: Deprecated AnyApiRef and AnyApiFactory. Use ApiRef and ApiFactory without type arguments instead; their new defaults match the existing aliases. The deprecated aliases remain available for compatibility.

  • d47986a: Improved type inference for deeply nested and cyclic translation messages. Required replacement values and plural counts are inferred at any depth, and count interpolation requires a numeric value.

  • 8ca78a2: Added coreApis, an object of core Utility API refs, with framework infrastructure APIs grouped under coreApis.internal: app lifecycle, OAuth requests, plugin header actions, plugin wrappers, and swappable components. The nested object is public. The deprecated Alert API is excluded in favor of Toast. The individual refs with object equivalents are deprecated in favor of their matching object members, while remaining compatible. Provider-specific authentication refs remain separate and are not deprecated.

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

  • 9d0a31b: Removed an unused use-sync-external-store dependency, which is no longer needed now that React 18 is the minimum supported version.

  • 6928d62: Fixed swappable components losing their mounted state when their props change. The resolved component remains stable while its props update.

  • 641ac02: Added coreExtensionData.titleTranslation to provide a translation message selection alongside a static title. Consumers can opt in to translated titles. The selection must not require formatting values.

  • 7594fd4: Page and sub-page blueprints now accept typed translation message selections in their title parameter, using existing translation resources. Select a message by calling a translation ref, for example myTranslationRef('page.title'). TypeScript checks the key and rejects messages that require formatting values.

    Resolved translations take precedence over configured titles in every language, including the default language. Titles wait for the selected language on first load and retain resolved values during later loads or failures, preserving page state.

    TranslationRef values are now callable functions. Treat refs as opaque values rather than checking for plain objects or cloning them.

  • Updated dependencies

    • @backstage/errors@1.4.0
    • @backstage/version-bridge@1.1.0
    • @backstage/config@1.3.11
    • @backstage/filter-predicates@0.2.1

@backstage/frontend-test-utils@1.0.0​

Major Changes​

  • b3befd0: Released version 1.0 of this frontend framework package. Its public APIs are now stable under the package versioning policy. Alpha and beta APIs retain their existing stability levels.

Minor Changes​

  • 76b1c3d: Removed the deprecated standalone mock API type exports and the non-deprecated MockFetchApiOptions export. Use the corresponding mockApis helpers to create instances and derive types as follows:

    Removed typeReplacement type
    MockAlertApiReturnType<typeof mockApis.alert>
    MockAnalyticsApiReturnType<typeof mockApis.analytics>
    MockConfigApiReturnType<typeof mockApis.config>
    MockErrorApiReturnType<typeof mockApis.error>
    MockFeatureFlagsApiReturnType<typeof mockApis.featureFlags>
    MockFetchApiReturnType<typeof mockApis.fetch>
    MockPermissionApiReturnType<typeof mockApis.permission>
    MockStorageApiReturnType<typeof mockApis.storage>
    MockTranslationApiReturnType<typeof mockApis.translation>
    MockErrorApiOptionsNonNullable<Parameters<typeof mockApis.error>[0]>
    MockFetchApiOptionsNonNullable<Parameters<typeof mockApis.fetch>[0]>
    MockFeatureFlagsApiOptionsNonNullable<Parameters<typeof mockApis.featureFlags>[0]>
    ErrorWithContextReturnType<ReturnType<typeof mockApis.error>['getErrors']>[number]

    Import mockApis from @backstage/frontend-test-utils. For example, use mockApis.analytics() to create an analytics mock and ReturnType<typeof mockApis.analytics> when you need an explicit instance type. Existing calls to the helpers require no changes. Inspection methods such as getEvents, getErrors, and getAlerts, along with legacy alert support, remain available.

  • 2aa14e3: Added the renderAs: 'chrome' option to renderInTestApp and mock utilities for navigation tests: mockApis.appHistory() and mockApis.routeResolution(). Page matching uses framework routing; wrap test elements in their page adapter when they need routing-library context. See the 1.57 migration notes for detailed migration steps and the routing test guide for examples.

  • 53ab1aa: BREAKING: renderInTestApp, renderTestApp and createExtensionTester now throw for every error reported while creating the test app or extension tree, including the ones a real app only logs as warnings, such as EXTENSION_IGNORED. Previously renderInTestApp and renderTestApp ignored these errors, so a test could pass for an app that is broken. All three helpers accept a new isExpectedError option to allow specific errors.

    Migration: fix the reported error in the test setup. The error message names the code to allow if the error is expected:

    renderInTestApp(<MyComponent />, {
    isExpectedError: error =>
    error.code === 'EXTENSION_INPUT_DATA_IGNORED' &&
    error.context.node.spec.id === 'page:my-plugin',
    });

    A common one is API_FACTORY_CONFLICT from providing an API that another plugin owns, such as a core.* API passed in extensions. That override was always rejected, so remove it, or use the apis option to replace an API in a test.

  • 8ca78a2: BREAKING Updated renderInTestApp and renderTestApp to provide default API implementations that are more suitable for testing. This may break existing tests that rely on the previous defaults:

    • Toasts are collected in memory instead of being displayed. Tests that assert on visible notifications need to provide an API implementation that forwards toasts to the UI, or assert on an explicitly supplied toast fake instead.
    • Storage is isolated in memory for each test app instead of using browser localStorage. Tests that seed or inspect localStorage, or rely on storage persisting between test apps, need to supply an explicit storage implementation.
    • Errors are collected without forwarding them to alerts or installing global error handlers. Error subscriptions no longer receive events from the default implementation. Tests that rely on these behaviors need an explicit error API implementation; tests can also supply a collecting error fake to assert on reported errors.
    • Alerts are collected and delivered to current subscribers, but earlier alerts are no longer replayed to new subscribers. Tests that rely on replay need an explicit alert API implementation.
    • OAuth requests use an in-memory coordinator with the same request coordination behavior as before.

    Explicit API overrides continue to take precedence over the defaults.

    Added mockApis helpers for all APIs in coreApis, including those grouped under coreApis.internal. These cover app state, dialogs, icons, OAuth requests, plugin wrappers and header actions, route resolution, swappable components, and toast notifications. Each .mock() helper provides typed Jest stubs without default behavior that can be registered directly with frontend test utilities.

    Added functional in-memory fakes for language, lifecycle, themes, icons, OAuth requests, plugin header actions, and toast notifications. Except for lifecycle, these can be supplied explicitly through the test app's apis option to configure behavior and inspect state. Use TestApiProvider for the lifecycle fake, since test apps manage their own lifecycle.

    Fixed storage fake isolation for nested buckets with the same name under different parents.

  • e3d50c4: Removed the deprecated show and showModal methods from dialog test helpers, and getIcon from icons test helpers. Update tests to use open for dialogs and icon for icon elements.

Patch Changes​

  • 6540a44: renderInTestApp now handles suspended content with an empty fallback, so promise-valued APIs do not require a Suspense wrapper in each test. Use asynchronous queries such as findByText to await suspended content. Elements that do not suspend still render immediately. When a descendant suspends, the entire element waits unless an inner Suspense boundary isolates it. An inner boundary also controls its own fallback. Tests that relied on an ancestor boundary's loading UI may need updated assertions.

    Test API tuples for promise-valued refs accept both synchronous partial implementations and promises of partial implementations. Synchronous mocks render immediately and pass through unchanged. Use promise mocks to test loading, failures, or code that calls promise methods.

    Fixed test rendering helpers losing their test extensions when a plugin named test is included in features.

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

  • 9d0a31b: Removed an unused use-sync-external-store dependency, which is no longer needed now that React 18 is the minimum supported version.

  • ec245df: Added apis to the results of renderInTestApp and renderTestApp, providing access to the app's Utility APIs using API refs. The holder exposes the same instances used by components, including registered APIs and test overrides.

  • Updated dependencies

    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/plugin-app-react@0.3.0
    • @backstage/plugin-app@0.6.0
    • @backstage/frontend-app-api@1.0.0
    • @backstage/errors@1.4.0
    • @backstage/test-utils@1.8.0
    • @backstage/core-app-api@1.20.7
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/version-bridge@1.1.0
    • @backstage/config@1.3.11
    • @backstage/filter-predicates@0.2.1
    • @backstage/plugin-permission-common@0.9.13

@backstage/app-defaults@1.8.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/core-app-api@1.20.7
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/theme@0.7.4

@backstage/backend-app-api@1.9.0​

Minor Changes​

  • 1c93987: Add optional beginAt timestamps to PluginStartupResult and ModuleStartupResult in the BackendStartupResult returned by backend.start(). The new timestamp marks when a plugin's or module's init function was invoked, i.e. after its dependencies were resolved. Together with the existing resultAt this makes it possible to see how long each individual plugin's or module's init function took, separate from time spent waiting for other plugins to initialize. It is undefined when a plugin or module failed before reaching initialization.

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/connections@0.4.2

@backstage/backend-defaults@0.19.0​

Minor Changes​

  • 250e4c3: Add support for the new WebSocket routing APIs.

    Existing server upgrade listeners can coexist during migration and receive unmatched upgrades. Multiple listeners produce a warning; migrate custom upgrade handling to the router API to avoid handling the same socket twice. Installing a plugin that registers a WebSocket route, such as signals, activates the server-level upgrade listener. Upgrades handled only through Express, such as the Kubernetes proxy, must migrate to this API; otherwise, unmatched upgrades receive 404 responses when this is the only server-level listener.

  • 3beb656: BREAKING: Request logs from the root HTTP router no longer include a date field, and no longer repeat the date at the start of the message. JSON logs, used when NODE_ENV is production, now include a timestamp field on every log line instead. Update any log pipelines or dashboards that read date or parse the date out of the message to use timestamp.

    If you override the root logger with a custom JSON format, use format.combine(format.timestamp(), format.json()) to keep the timestamp field.

Patch Changes​

  • f81ca4e: The AWS S3 URL reader no longer assumes the configured roleArn a second time when the matching account under aws.accounts already provides credentials for that exact role, for example through a web identity token file. Previously the role had to trust itself for this setup to work. The role is still assumed explicitly when the integration sets an externalId.
  • 392710f: The Azure DevOps URL reader now warns at startup when a personal access token is configured for Azure DevOps Services. Global personal access tokens stop working on January 27, 2027, and organization-scoped tokens are now deprecated in favor of Microsoft Entra ID credentials. Errors from rejected credentials are also clearer.
  • 80cc892: Removed the runtime dependency on @backstage/cli-node, which was only used for types. Backends no longer install the CLI tooling packages through @backstage/backend-defaults.
  • 5eb2381: Updated a documentation link for DefaultRootHttpRouter to point to the coreServices.rootHttpRouter service reference.
  • 1892d2f: chore(deps): bump minimatch from 10.2.6 to 11.0.1
  • fbd2535: Fixed a connection and memory leak in the GitHub URL reader, where every failed request with a large error response body, such as the error pages served during a GitHub Enterprise outage, left its connection open indefinitely.
  • da22423: Ensures that the limited user cookie issued for a request always represents the user authenticated on that request. A previously issued cookie belonging to a different user is now replaced during the cookie refresh, instead of being reused.
  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • 9fc68ae: Fixed the valkey cache store sharing keys between plugins. Two plugins that cached a value under the same key could read and overwrite each other's entries. Keys are now stored under the plugin namespace, the same way the redis store does it. Cache entries now use new key names, so existing entries are no longer read and are rebuilt as plugins write new values. Old entries stay in Valkey until their TTL expires. Entries without a TTL, and the per-plugin key index sets that the old layout created, stay until you remove them manually.
  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/backend-app-api@1.9.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/config@1.3.11
    • @backstage/config-loader@1.11.5
    • @backstage/connections@0.4.2
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6

@backstage/backend-plugin-api@1.12.0​

Minor Changes​

  • a5337d0: The coreServices export is now a frozen plain object instead of a TypeScript namespace, and its type is described by the new CoreServices interface. Usage is unchanged, and every service reference keeps its existing type. The object can no longer be modified at runtime.

  • 250e4c3: Add WebSocket upgrade routes to the HTTP router services. Routes require token authentication by default. The unauthenticated override leaves authentication to the handler. Cookie authentication is not supported. Browser clients can pass bearer tokens through the WebSocket protocol header.

    httpRouter.addWebSocketHandler({
    path: '/events',
    handler({ request, socket, head }) {
    webSocketServer.handleUpgrade(request, socket, head, connection => {
    webSocketServer.emit('connection', connection, request);
    });
    },
    });

    BREAKING PRODUCERS: Custom implementations of HttpRouterService and RootHttpRouterService must implement addWebSocketHandler.

  • 6a0de59: Added support for passing a file URL string, such as import.meta.url, to resolvePackagePath to resolve assets relative to the containing package without specifying its name. The nearest ancestor directory containing package.json is used as the package root.

Patch Changes​

  • 2b61a53: Fixed detection of PostgreSQL unique constraint violations when the database returns localized error messages. Catalog ingestion can now fall back to individual entity updates when a provider delivers duplicate entity references in the same batch.
  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/cli-common@0.3.3
    • @backstage/config@1.3.11
    • @backstage/connections@0.4.2
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6

@backstage/backend-test-utils@1.12.0​

Minor Changes​

  • 250e4c3: Support WebSocket upgrade route registration in HTTP router service mocks and test backends.

  • a5337d0: The mockServices export is now a frozen plain object instead of a TypeScript namespace, and its type is described by the new MockServices interface. Usage is unchanged: you can still call each mock service directly, use its factory and mock helpers, and refer to types such as mockServices.rootConfig.Options.

    Both mockServices and each of its services are frozen, so they can no longer be modified at runtime, for example with jest.spyOn(mockServices.urlReader, 'mock'). The mocks and factories they create are not affected.

Patch Changes​

  • ee1c5af: registerMswTestHooks now also fails tests on unhandled requests when used with msw 3.
  • Updated dependencies
    • @backstage/backend-defaults@0.19.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/backend-app-api@1.9.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/config@1.3.11
    • @backstage/plugin-permission-common@0.9.13

@backstage/core-compat-api@0.6.0​

Minor Changes​

  • df2bcee: BREAKING: convertLegacyAppOptions now rejects components.Router: remove plain BrowserRouter wrappers, move global providers to AppRootWrapperBlueprint, and use page router adapters for page-specific routing, with converted legacy pages receiving a scoped React Router v6 adapter automatically. See the 1.57 migration notes for detailed migration steps.

Patch Changes​

  • e55a4a8: Updated compatibility with the FrontendPlugin interface after removal of its deprecated id property, retaining support for older plugin instances.
  • e3d50c4: Added support for the new icons API when rendering plugins in old-system apps, while continuing to provide the original icons API for older plugins. Legacy app context icon lookups continue to return components.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/plugin-app-react@0.3.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/frontend-adapter-react-router-v6@0.2.0
    • @backstage/version-bridge@1.1.0
    • @backstage/filter-predicates@0.2.1

@backstage/core-plugin-api@1.13.0​

Minor Changes​

  • 558c076: Exported the alpha TranslationRefTuple type for messages selected by calling a translation ref. Refs are now callable functions; treat them as opaque values.

    BREAKING PRODUCERS: Translation snapshots require t even when ready is false. Custom translation APIs must provide a translator using available messages and language fallbacks.

Patch Changes​

  • ca02018: API reference IDs now use plugin ID validation for each dot-separated component. This accepts numeric dash groups and mixed case, including IDs such as plugin.example-2.todos.

  • 6540a44: Preserved the legacy useApi hook's direct-value behavior when the frontend system's hook unwraps promise-valued APIs. The legacy hook continues returning promises unchanged.

  • e55a4a8: Updated compatibility with the FrontendPlugin interface after removal of its deprecated id property, retaining support for older plugin instances.

  • 315f7bc: Made the legacy icon component and withApis compatibility APIs independent of @backstage/frontend-plugin-api so that they remain available to legacy frontend apps.

    Deprecated withApis. Wrap class components in a function component that uses useApi instead.

  • e3d50c4: Updated useApp to support the new icons API. Its getSystemIcon and getSystemIcons methods continue to return icon components.

  • Updated dependencies

    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/errors@1.4.0
    • @backstage/version-bridge@1.1.0
    • @backstage/config@1.3.11

@backstage/dev-utils@1.2.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/ui@0.20.0
    • @backstage/core-app-api@1.20.7
    • @backstage/integration-react@1.3.0
    • @backstage/app-defaults@1.8.0
    • @backstage/theme@0.7.4
    • @backstage/catalog-model@1.10.3

@backstage/errors@1.4.0​

Minor Changes​

  • d368d89: Added static type guards such as AuthenticationError.is(value) and ResponseError.is(value) to narrow unknown errors by name and basic shape across package copies.

    Added an isErrorWithName(value, name) helper for implementing custom error guards. CustomErrorBase and ForwardedError have no public is guard; forwarded errors are recognized by their preserved error names.

@backstage/frontend-adapter-react-router-v6@0.2.0​

Minor Changes​

  • 1fba2bb: Added ReactRouterV6PageRouter for page-scoped React Router v6 routing with app-owned history; React Router v6 is a peer dependency. Render it inside a lazily loaded page or sub-page component to support relative links, nested routes, and route parameters. See the 1.57 migration notes for detailed migration steps and the page router guide for setup and nesting examples.

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • 9d0a31b: Removed an unused use-sync-external-store dependency, which is no longer needed now that React 18 is the minimum supported version.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/errors@1.4.0
    • @backstage/version-bridge@1.1.0
    • @backstage/filter-predicates@0.2.1

@backstage/frontend-adapter-react-router-v7@0.2.0​

Minor Changes​

  • 1fba2bb: Added ReactRouterV7PageRouter for page-scoped React Router v7 routing with app-owned history; React Router v7 is a peer dependency. Render it inside a lazily loaded page or sub-page component to support relative links, nested routes, and route parameters. See the 1.57 migration notes for detailed migration steps and the page router guide for setup and nesting examples.

Patch Changes​

  • 9d0a31b: Removed an unused use-sync-external-store dependency, which is no longer needed now that React 18 is the minimum supported version.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/errors@1.4.0
    • @backstage/version-bridge@1.1.0
    • @backstage/filter-predicates@0.2.1

@backstage/frontend-adapter-tanstack-router@0.2.0​

Minor Changes​

  • 1fba2bb: Added TanStackPageRouter for page-scoped TanStack routing with app-owned history, including createTanStackPageRouter and TanStackPageContent for plugin-owned route trees; @tanstack/react-router and @tanstack/history are peer dependencies. See the 1.57 migration notes for detailed migration steps and the TanStack page router guide for setup, navigation blockers, and custom history requirements.

Patch Changes​

  • 9d0a31b: Removed an unused use-sync-external-store dependency, which is no longer needed now that React 18 is the minimum supported version.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/errors@1.4.0
    • @backstage/version-bridge@1.1.0
    • @backstage/filter-predicates@0.2.1

@backstage/integration@2.2.0​

Minor Changes​

  • 2b201b6: Added a ClientCertificate credential kind for the Azure DevOps integration. Configure clientId, tenantId and either clientCertificate (PEM including the private key) or clientCertificatePath to authenticate an App Registration with a certificate instead of a client secret.

Patch Changes​

  • f56086a: Fixed GitHub app credentials failing for every owner with Cannot read properties of null (reading 'account') when the list of app installations returned by GitHub contained null entries. Those entries are now ignored.
  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/connections@0.4.2

@backstage/integration-react@1.3.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • 4c662c9: Removed this package's direct Material UI v4 dependencies. SCM integrations without a registered system icon now use a Remix code icon as the fallback.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/integration@2.2.0
    • @backstage/config@1.3.11

@techdocs/cli@1.15.0​

Minor Changes​

  • a4604d2: Add Zensical support to serve, serve:raw and generate via --engine zensical (or the backstage.io/techdocs-engine annotation in catalog-info.yaml), including live reload in the preview app. The default --docker-image is now chosen per engine instead of always being spotify/techdocs, and matches the image the TechDocs backend uses for that engine, so MkDocs previews now use spotify/techdocs:v1.2.8 instead of latest. Passing --docker-image explicitly behaves as before.

    The serve flags --mkdocs-port, --mkdocs-config-file-name and --mkdocs-parameter-* are deprecated in favor of --engine-port, --config-file-name and --parameter-*. If both the old and new flag are given, the new one wins and the warning says the old one is ignored.

Patch Changes​

  • bc73976: Restricts markdown_extensions in mkdocs.yml to known extension names before documentation generation, in both the MkDocs and Zensical engines. Extension names outside the permitted set are removed from the configuration with a warning. Allow additional extensions, for example from a custom build image, with the new techdocs.generator.mkdocs.dangerouslyAllowAdditionalExtensions configuration, or the --dangerouslyAllowAdditionalExtensions flag when using the TechDocs CLI.
  • Updated dependencies
    • @backstage/backend-defaults@0.19.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-techdocs-node@2.3.0
    • @backstage/catalog-model@1.10.3
    • @backstage/cli-common@0.3.3
    • @backstage/config@1.3.11

@backstage/test-utils@1.8.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • ee1c5af: registerMswTestHooks now also fails tests on unhandled requests when used with msw 3.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-app-api@1.20.7
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/theme@0.7.4
    • @backstage/config@1.3.11
    • @backstage/plugin-permission-common@0.9.13

@backstage/ui@0.20.0​

Minor Changes​

  • f4d8adf: BREAKING: Backstage UI now uses explicit routing integration and React Aria's native link behavior: standalone apps that relied on automatic React Router integration must supply BUIProvider with a useNavigation hook, React Router is no longer a peer dependency, and routerOptions now supports only the router-neutral replace and state fields. BREAKING: Link targets using javascript:, data:, or vbscript: become inert about:blank links with a console warning. See the 1.57 migration notes for detailed migration steps and the BUI routing migration guide for integration requirements.

    Affected components: BUIProvider, ButtonLink, Card, Combobox, Header, Link, List, Menu, PluginHeader, SearchAutocomplete, Select, Table, Tabs, TagGroup

Patch Changes​

  • 9d0a31b: Removed an unused use-sync-external-store dependency, which is no longer needed now that React 18 is the minimum supported version.

  • 9120c46: Updated dependency glob to ^14.0.0.

  • 724657a: Header tabs no longer make the page scroll horizontally when they do not fit. The tabs now stay in a single row that scrolls on its own, with a visible scrollbar. When more tabs are hidden on a side, that edge of the row fades out. The fade is removed while a tab has keyboard focus. The row scrolls to show the active tab when the page loads and whenever the active tab changes. With a mouse or other precise pointer, a scroll button also appears on each side that has hidden tabs. Small touch screens show only the fade. The buttons respect the reduced motion setting. Screen readers do not announce them, because every tab is still reachable with the keyboard.

    Affected components: Header

  • 065d1e3: Fixed useTable in complete mode showing an empty page labelled "NaN - NaN of N" when paginationOptions switched from type: 'none' to paged pagination after mount.

    Affected components: useTable

  • Updated dependencies

    • @backstage/version-bridge@1.1.0

@backstage/version-bridge@1.1.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

@backstage/plugin-app@0.6.0​

Minor Changes​

  • f9f794b: BREAKING: Icon bundles created with IconBundleBlueprint now accept only icon elements. Replace component values such as icons: { user: MyIcon } with icons: { user: <MyIcon /> }. For Material UI icons, use <MyIcon fontSize="inherit" />. Icons supplied through convertLegacyAppOptions continue to accept components and are converted automatically.

  • cedb355: The deprecated DialogApi.show and DialogApi.showModal methods now throw errors. Use DialogApi.open and provide your own dialog surface and dismissal handling.

    Added support for the new icons API while preserving IconsApi.getIcon for older plugins.

  • 86681bf: Removed the ignored anchorOrigin option from the built-in alert display extension and toast display props. Remove this option from your extension configuration. Toasts continue to appear at the bottom center of the screen.

  • df2bcee: Pages and sub-pages now share app-owned navigation and can use different routing libraries, with implicit React Router v6 compatibility for existing pages. BREAKING: Removed the router input from app/root; remove root router extensions, move global providers to AppRootWrapperBlueprint, and use page adapters where needed. See the 1.57 migration notes for detailed migration steps.

  • 24bde66: Custom navigation components now receive navItems without the deprecated flat items collection.

Patch Changes​

  • 9bac36e: Fixed the app remounting during finalization when root elements are added, for example ones deferred with an if predicate. Root elements are now keyed by their extension ID and rendered in a single fixed position, so adding one no longer moves the rest of the app in the React tree.
  • edf309d: Ensure dismissed toasts are marked as closed in ToastApiForwarder so they are not replayed when ToastDisplay remounts (such as during theme changes).
  • e55a4a8: Updated plugin identity handling to use pluginId, while preserving support for older plugin instances that only expose id.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • 9d0a31b: Removed an unused use-sync-external-store dependency, which is no longer needed now that React 18 is the minimum supported version.
  • ff23578: Added support for translated titles in navigation, page headers, tabs, and breadcrumbs.
  • 8f36712: Updated the app runtime to use the analytics implementation APIs from @backstage/plugin-app-react.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/plugin-app-react@0.3.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/ui@0.20.0
    • @backstage/integration-react@1.3.0
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/theme@0.7.4
    • @backstage/version-bridge@1.1.0
    • @backstage/config@1.3.11
    • @backstage/filter-predicates@0.2.1

@backstage/plugin-app-react@0.3.0​

Minor Changes​

  • f9f794b: BREAKING: Icon bundles created with IconBundleBlueprint now accept only icon elements. Replace component values such as icons: { user: MyIcon } with icons: { user: <MyIcon /> }. For Material UI icons, use <MyIcon fontSize="inherit" />. Icons supplied through convertLegacyAppOptions continue to accept components and are converted automatically.

  • 5c29a89: BREAKING: Removed the deprecated flat items prop from custom navigation components. Use the navItems collection instead.

    Use navItems.rest() instead of iterating over items. Replace item.to with item.href and item.text with item.title. The item.icon value is a React element, so render it directly instead of using it as a component type.

  • df2bcee: BREAKING: Removed RouterBlueprint; remove overrides that only install BrowserRouter, move global providers to AppRootWrapperBlueprint, and render routing adapters inside lazily loaded page components. For custom navigation, provide AppHistoryApi through an ApiBlueprint factory for coreApis.appHistory that is available during initialization without an if predicate. See the 1.57 migration notes for detailed migration steps.

Patch Changes​

  • 77c1622: Added the AnalyticsImplementation type, moved from @backstage/frontend-plugin-api, alongside AnalyticsImplementationBlueprint and AnalyticsImplementationFactory.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0

@backstage/plugin-auth-backend@0.31.0​

Minor Changes​

  • 352ad44: BREAKING: The deprecated experimental Dynamic Client Registration (DCR) support has been removed. Use Client ID Metadata Documents (CIMD) instead and remove auth.experimentalDynamicClientRegistration from your configuration. The database migration deletes registered clients and their authorization and offline sessions, invalidating existing DCR authorization codes and refresh tokens. Users must sign in again through a CIMD client. Already-issued user tokens remain valid until they expire. See the migration guide.

  • 9e22c4b: Added support for pre-registered OAuth clients through the new auth.staticClients configuration. This allows integrations that support neither Client ID Metadata Documents nor Dynamic Client Registration to act on behalf of signed-in users using a fixed client ID, an optional client secret, and exact redirect URIs. All clients must use PKCE. Clients with a secret must also authenticate at the token endpoint.

    The token endpoint verifies client credentials for both authorization code and refresh token grants. Missing or incorrect credentials for confidential clients return invalid_client with HTTP 401. Public clients can identify themselves using HTTP Basic with an empty secret. Codes issued to a different client are rejected.

    Removing a configured client rejects its outstanding authorization codes and refresh tokens. HTTP Basic authentication supports form-encoded client IDs and secrets.

    PKCE now requires the S256 challenge method for all clients, including existing CIMD clients. The plain method is no longer accepted or advertised. Update clients that use plain to generate SHA-256 challenges.

Patch Changes​

  • 5fc15b7: Fixed authorization-code exchanges to reject supplied client IDs that do not match the client that obtained the code. These requests return invalid_grant without consuming the code. Exchanges that omit client_id remain supported for older clients but now log a deprecation warning; a future release will require it.
  • 97ee785: Allow Cursor clients to use Client ID Metadata Documents by default.
  • 8965c27: User tokens issued by sign-in resolvers now always have the entity refs in their sub and ent claims in canonical form, for example user:default/jane.doe rather than User:default/Jane.Doe, and duplicate ent refs are removed. Previously, a custom sign-in resolver could issue valid but non-canonical refs, which then failed to match stored user info and offline sessions on case-sensitive databases.
  • 1892d2f: chore(deps): bump minimatch from 10.2.6 to 11.0.1
  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.
  • 7db7c52: Respect the auth.backstageTokenExpiration configuration when issuing OAuth access and ID tokens from the OIDC service, instead of hard-coding a 1-hour expiry.
  • fa0eb7a: Added a POST /v1/offline-sessions/revoke endpoint that lets other backend services revoke all offline sessions (refresh tokens) of a user. The endpoint only accepts service credentials, records an audit event, and is only available when auth.experimentalRefreshToken.enabled is set.
  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog@2.1.0​

Minor Changes​

  • d4f458e: Added support for translated entity content titles through EntityContentBlueprint.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • 0da6298: Entity page tabs now generate app-absolute links from the entity route, so they work correctly when navigation comes from outside the page router.
  • 57111dc: Migrated the EntityNotFound component from Material UI to Backstage UI.
  • 9d0a31b: Removed an unused use-sync-external-store dependency, which is no longer needed now that React 18 is the minimum supported version.
  • 118d84a: Updated catalog tabs to render icon elements through the current frontend icon API.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/catalog-client@1.16.4
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/core-compat-api@0.6.0
    • @backstage/ui@0.20.0
    • @backstage/integration-react@1.3.0
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/plugin-search-react@1.12.0
    • @backstage/plugin-techdocs-react@1.5.0
    • @backstage/version-bridge@1.1.0
    • @backstage/plugin-scaffolder-common@2.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/filter-predicates@0.2.1
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-search-common@1.2.27
    • @backstage/plugin-techdocs-common@0.1.3

@backstage/plugin-catalog-backend-module-ldap@0.13.0​

Minor Changes​

  • f9a84cb: The LDAP org entity provider now reads users and groups in parallel by default. Set disableParallelReads: true to use one connection and read sequentially. Parallel reads open two binds and two connections per refresh. Directories with per-client connection limits may notice the extra load after upgrading.

    The org entity provider and LdapOrgReaderProcessor request only the attributes used by configured mappings. LDAP connections are closed after each refresh.

    BREAKING: Searches no longer request ['*', '+'] by default. This applies to both the org entity provider and LdapOrgReaderProcessor. When options.attributes is not explicitly configured, attributes required by map (including custom map.* overrides and membership mappings) are requested automatically. When options.attributes is explicitly configured, the provided list is used as-is and must include all attributes required by mappings, vendor configuration, and custom transformers. Custom transformers that access other attributes from LDAP entries may now find those attributes missing.

    If your transformers rely on additional LDAP attributes, include them in options.attributes or use ['*', '+'] to request all attributes:

    catalog:
    providers:
    ldapOrg:
    default:
    users:
    options:
    + attributes: ['*', '+']
    groups:
    options:
    + attributes: ['*', '+']

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-react@4.0.0​

Minor Changes​

  • d4f458e: Added support for translated entity content titles through EntityContentBlueprint.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/catalog-client@1.16.4
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/frontend-test-utils@1.0.0
    • @backstage/core-compat-api@0.6.0
    • @backstage/ui@0.20.0
    • @backstage/integration-react@1.3.0
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/version-bridge@1.1.0
    • @backstage/catalog-model@1.10.3
    • @backstage/filter-predicates@0.2.1
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-events-backend-module-azure@0.3.0​

Minor Changes​

  • 70fd46d: BREAKING Webhook events modules now require a webhook secret by default. Requests to the /api/events/http/github, /api/events/http/gitlab, and /api/events/http/azureDevOps endpoints are rejected with HTTP 403 when no webhook secret is configured, instead of being accepted without validation. To continue accepting unauthenticated events, for example in development environments, set the module's new dangerouslyAllowUnauthenticatedEvents option to true. In addition, the createGitlabTokenValidator function from @backstage/plugin-events-backend-module-gitlab now requires a logger argument.

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11

@backstage/plugin-events-backend-module-github@0.5.0​

Minor Changes​

  • 70fd46d: BREAKING Webhook events modules now require a webhook secret by default. Requests to the /api/events/http/github, /api/events/http/gitlab, and /api/events/http/azureDevOps endpoints are rejected with HTTP 403 when no webhook secret is configured, instead of being accepted without validation. To continue accepting unauthenticated events, for example in development environments, set the module's new dangerouslyAllowUnauthenticatedEvents option to true. In addition, the createGitlabTokenValidator function from @backstage/plugin-events-backend-module-gitlab now requires a logger argument.

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11

@backstage/plugin-events-backend-module-gitlab@0.4.0​

Minor Changes​

  • 70fd46d: BREAKING Webhook events modules now require a webhook secret by default. Requests to the /api/events/http/github, /api/events/http/gitlab, and /api/events/http/azureDevOps endpoints are rejected with HTTP 403 when no webhook secret is configured, instead of being accepted without validation. To continue accepting unauthenticated events, for example in development environments, set the module's new dangerouslyAllowUnauthenticatedEvents option to true. In addition, the createGitlabTokenValidator function from @backstage/plugin-events-backend-module-gitlab now requires a logger argument.

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11

@backstage/plugin-events-node@0.5.0​

Minor Changes​

  • a70aaea: The requests passed to request validators now include the parsed query string. The request rejection details now also support an optional contentType option for the provided payload, defaulting to application/json but also allowing text/plain.

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0

@backstage/plugin-scaffolder@1.41.0​

Minor Changes​

  • 3fe82f6: Added a ScaffolderTemplateFilterBlueprint that lets apps filter the new frontend system's template list using identity, catalog, or other viewer-specific state.
  • ae86338: Added GitLab branch autocompletion to RepoBranchPicker using user SCM credentials.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • 111c6ce: Keep the task button bar at the user's chosen visibility when a task completes, so log visibility and start-over controls remain accessible. Action availability continues to depend on task state and permissions.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/integration@2.2.0
    • @backstage/catalog-client@1.16.4
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/plugin-scaffolder-react@3.0.0
    • @backstage/ui@0.20.0
    • @backstage/integration-react@1.3.0
    • @backstage/plugin-home-react@0.1.44
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/plugin-techdocs-react@1.5.0
    • @backstage/plugin-scaffolder-common@2.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/filter-predicates@0.2.1
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-techdocs-common@0.1.3

@backstage/plugin-scaffolder-backend@4.3.0​

Minor Changes​

  • ff0ef74: Added support for when conditions on parameter steps. Steps whose condition evaluates to false are skipped during validation, and their values are removed before the task runs. Also updated Nunjitsu to 0.7.0, with no change to existing templating behavior.

Patch Changes​

  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.

  • 2fac95b: Group the Software Templates API documentation by functionality instead of placing all endpoints under "Untagged".

  • eda8ede: Check the host that relative fetch URLs resolve to when user credentials are required.

    When scaffolder.requireScmUserCredentials is enabled, the fetch actions now apply the user-credential requirement to the host that the fetch URL resolves to, rather than the host of the template location. This makes the requirement effective also for fetch URLs that are not parseable as absolute URLs on their own.

  • e318672: Fixed matching of action input values in scaffolder permission policies, including identifiers that are provided either as numbers or as strings.

  • be5074c: Preserve public task log values when rendering without secrets omits an earlier object field, while continuing to redact secret-derived keys and values.

  • 62eaba9: Fixed custom task permission rules registered by backend modules being ignored when authorizing task access and filtering task lists.

  • Updated dependencies

    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/backend-openapi-utils@0.7.4
    • @backstage/plugin-scaffolder-common@2.4.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-gcp@0.3.0​

Minor Changes​

  • 44d5ba2: BREAKING: The backend's Google Cloud credentials now require the storage.objects.list permission on the configured task recovery bucket, in addition to the existing object permissions. Grant this permission before upgrading.

    Fixed task recovery workspace saves failing with Google Cloud Storage rate limit errors when template steps finish in quick succession. Each snapshot is saved to a separate object, and recovery continues to support snapshots from older versions.

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-common@2.4.0​

Minor Changes​

  • ff0ef74: Added support for when conditions on parameter steps, allowing templates to show or hide wizard steps based on earlier answers, for example ${{ parameters.cloudProvider === 'AWS' }}. Also added the alpha resolveParameterSteps and filterHiddenStepValues helpers for working out which steps are visible and removing values from hidden steps.

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-scaffolder-react@3.0.0​

Minor Changes​

  • 3fe82f6: Added a ScaffolderTemplateFilterBlueprint that lets apps filter the new frontend system's template list using identity, catalog, or other viewer-specific state.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • ff0ef74: The scaffolder wizard now shows or hides parameter steps based on their when condition, and values from hidden steps are left out of the submitted parameters.

Patch Changes​

  • 1c461ca: Fixed BUI array item headings to use the item schema title and honor an explicit item ui:title without adding a numeric suffix. Untitled items retain the numbered fallback.
  • e8c4fb9: Improved screen reader support in the BUI scaffolder form theme: array item controls include the item name in their labels.
  • 818fbd6: The BUI form theme now renders a multi-select dropdown for array fields with unique enum items, and focus/blur events now report the selected values correctly.
  • 70bbe4b: The review step now applies ui:backstage.review.mask, ui:backstage.review.show: false, ui:widget: password and ui:field: Secret to fields and items nested inside arrays and inside objects with ui:backstage.review.explode: false. Previously these nested values were shown in clear text.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/catalog-client@1.16.4
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/frontend-test-utils@1.0.0
    • @backstage/ui@0.20.0
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/theme@0.7.4
    • @backstage/version-bridge@1.1.0
    • @backstage/plugin-scaffolder-common@2.4.0
    • @backstage/catalog-model@1.10.3

@backstage/plugin-search@1.8.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/ui@0.20.0
    • @backstage/plugin-home-react@0.1.44
    • @backstage/plugin-search-react@1.12.0
    • @backstage/version-bridge@1.1.0
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-search-react@1.12.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • 6c8a6b1: Fixed SearchFilter.Autocomplete with multiple clearing the typed text on every keystroke once a value was selected.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/theme@0.7.4
    • @backstage/version-bridge@1.1.0
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-techdocs@1.20.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • 9a1d5cf: Fixed the TechDocs table of contents drifting to the right on wide screens. It now stays aligned with the right edge of the documentation content.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/integration@2.2.0
    • @backstage/catalog-client@1.16.4
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/ui@0.20.0
    • @backstage/integration-react@1.3.0
    • @backstage/plugin-auth-react@0.1.33
    • @backstage/plugin-search-react@1.12.0
    • @backstage/plugin-techdocs-react@1.5.0
    • @backstage/theme@0.7.4
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/filter-predicates@0.2.1
    • @backstage/plugin-search-common@1.2.27
    • @backstage/plugin-techdocs-common@0.1.3

@backstage/plugin-techdocs-addons-test-utils@2.1.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/plugin-catalog@2.1.0
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/test-utils@1.8.0
    • @backstage/core-app-api@1.20.7
    • @backstage/integration-react@1.3.0
    • @backstage/plugin-search-react@1.12.0
    • @backstage/plugin-techdocs@1.20.0
    • @backstage/plugin-techdocs-react@1.5.0

@backstage/plugin-techdocs-backend-module-zensical@0.1.0​

Minor Changes​

  • a4604d2: New module that adds Zensical as an experimental TechDocs documentation engine. Opt entities in with the backstage.io/techdocs-engine: zensical annotation, or set techdocs.generator.defaultEngine: zensical. See Zensical Engine for setup and configuration.

Patch Changes​

  • bc73976: Restricts markdown_extensions in mkdocs.yml to known extension names before documentation generation, in both the MkDocs and Zensical engines. Extension names outside the permitted set are removed from the configuration with a warning. Allow additional extensions, for example from a custom build image, with the new techdocs.generator.mkdocs.dangerouslyAllowAdditionalExtensions configuration, or the --dangerouslyAllowAdditionalExtensions flag when using the TechDocs CLI.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-techdocs-node@2.3.0
    • @backstage/config@1.3.11

@backstage/plugin-techdocs-module-addons-contrib@1.2.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/integration@2.2.0
    • @backstage/core-components@0.18.16
    • @backstage/integration-react@1.3.0
    • @backstage/plugin-techdocs-react@1.5.0

@backstage/plugin-techdocs-node@2.3.0​

Minor Changes​

  • a4604d2: Added a new @backstage/plugin-techdocs-node/alpha entry point with building blocks for implementing additional documentation engines in separate modules: createDockerContainerRunner, createOrUpdateMetadata, storeEtagMetadata, runCommand, validateInputDirectory, patchIndexPreBuild, and the mkdocs.yml helpers MKDOCS_SCHEMA, validateMkdocsYaml and sanitizeMkdocsYml. These are alpha and may change in minor releases.

Patch Changes​

  • 686d3cb: Fixed TechDocs served from Azure Blob Storage or Google Cloud Storage keeping storage connections open when a browser navigates away before a file is fully loaded. Errors that occur while streaming a file from Azure Blob Storage are now also logged and handled, instead of being left unhandled.
  • bc73976: Restricts markdown_extensions in mkdocs.yml to known extension names before documentation generation, in both the MkDocs and Zensical engines. Extension names outside the permitted set are removed from the configuration with a warning. Allow additional extensions, for example from a custom build image, with the new techdocs.generator.mkdocs.dangerouslyAllowAdditionalExtensions configuration, or the --dangerouslyAllowAdditionalExtensions flag when using the TechDocs CLI.
  • 2e98895: Fixed TechDocs served from AWS S3 leaking S3 connections when a browser navigates away before a file is fully loaded. Over time the connection pool was exhausted and all TechDocs pages failed to load with Socket timed out without establishing a connection errors until the backend was restarted.
  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-search-common@1.2.27
    • @backstage/plugin-techdocs-common@0.1.3

@backstage/plugin-techdocs-react@1.5.0​

Minor Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/version-bridge@1.1.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-techdocs-common@0.1.3

@backstage/backend-dynamic-feature-service@0.8.9​

Patch Changes​

  • ed8f1ef: Updated dependency @module-federation/sdk to ~2.9.0. Updated dependency @module-federation/enhanced to ~2.9.0. Updated dependency @module-federation/runtime to ~2.9.0. Updated dependency @module-federation/runtime-core to ~2.9.0.
  • c999b77: Dynamic backend plugins can now require the packages they share with the backend when those packages are not in the root node_modules, as with the pnpm isolated node linker. They are found through the backend package and through this package. With the default pnpm hoisting, this includes the packages that pnpm hoists into node_modules/.pnpm/node_modules. With hoist: false, only the direct dependencies of the backend package and of this package are found. Everything that was searched before is still searched first, so a module that was found before is found in the same place. The exception is plugins inside the Backstage root on Windows, which did not search the root node_modules before, other than through NODE_PATH. It is now searched in the same order as on other platforms.
  • Updated dependencies
    • @backstage/backend-defaults@0.19.0
    • @backstage/plugin-catalog-backend@4.0.3
    • @backstage/cli-node@0.3.6
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-events-backend@0.6.8
    • @backstage/backend-openapi-utils@0.7.4
    • @backstage/plugin-events-node@0.5.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/cli-common@0.3.3
    • @backstage/config@1.3.11
    • @backstage/config-loader@1.11.5
    • @backstage/plugin-app-node@0.1.51
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6
    • @backstage/plugin-scaffolder-node@1.0.0
    • @backstage/plugin-search-backend-node@1.4.10
    • @backstage/plugin-search-common@1.2.27

@backstage/backend-openapi-utils@0.7.4​

Patch Changes​

  • 5695308: Fixed response validation so that an empty response body for a JSON response now reports that the body is required but missing, instead of failing with a JSON parse error when the response schema declares required properties.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0

@backstage/catalog-client@1.16.4​

Patch Changes​

  • 9c76a81: Documented that the entities/by-query endpoint currently applies only the first orderField; any additional order fields are ignored. Updated the OpenAPI spec parameter description and the Software Catalog API docs accordingly. No behavior change. Refs #17560.
  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/filter-predicates@0.2.1
    • @backstage/plugin-catalog-common@1.2.2

@backstage/catalog-model@1.10.3​

Patch Changes​

  • Updated dependencies
    • @backstage/errors@1.4.0

@backstage/cli@0.36.8​

Patch Changes​

  • 04a54e2: Switched the compilation target to ES2024, which all supported Node.js versions fully support. Package builds, app bundles, and the backend development server now compile code for ES2024, and the TypeScript target and lib options in @backstage/cli/config/tsconfig.json are set to ES2024. This requires TypeScript 5.9 or later, which is now the oldest supported version according to the versioning policy.

    The lib change allows code to use ES2024 built-in APIs such as Object.groupBy and Promise.withResolvers. Backstage doesn't include polyfills, so frontend code that uses these APIs needs at least Chrome or Edge 119, Firefox 121, or Safari 17.4.

  • 9120c46: Updated dependency glob to ^14.0.0.

  • Updated dependencies

    • @backstage/cli-node@0.3.6
    • @backstage/eslint-plugin@0.3.4
    • @backstage/cli-module-build@0.1.10
    • @backstage/cli-module-test-jest@0.1.8
    • @backstage/cli-common@0.3.3
    • @backstage/cli-defaults@0.1.8

@backstage/cli-common@0.3.3​

Patch Changes​

  • Updated dependencies
    • @backstage/errors@1.4.0

@backstage/cli-defaults@0.1.8​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-module-auth@0.1.6
    • @backstage/cli-module-new@0.1.9
    • @backstage/cli-module-info@0.1.6
    • @backstage/cli-module-migrate@0.2.3
    • @backstage/cli-module-build@0.1.10
    • @backstage/cli-module-test-jest@0.1.8
    • @backstage/cli-module-package-manager-yarn@0.1.5
    • @backstage/cli-module-actions@0.1.5
    • @backstage/cli-module-catalog@0.2.1
    • @backstage/cli-module-config@0.1.9
    • @backstage/cli-module-github@0.1.6
    • @backstage/cli-module-lint@0.1.7
    • @backstage/cli-module-maintenance@0.1.7
    • @backstage/cli-module-scaffolder@0.2.1
    • @backstage/cli-module-search@0.2.1
    • @backstage/cli-module-translations@0.1.6

@backstage/cli-module-actions@0.1.5​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/errors@1.4.0

@backstage/cli-module-auth@0.1.6​

Patch Changes​

  • 4d94005: Fixed auth logout so that it revokes the refresh token on the server. Previously the revocation request was rejected because it did not identify the CLI client, which left the session valid until it expired.
  • 5fc15b7: Fixed auth login to include the CLI's client ID when exchanging authorization codes, supporting auth backends that enforce client ID binding.
  • 9120c46: Updated dependency glob to ^14.0.0.
  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/errors@1.4.0

@backstage/cli-module-build@0.1.10​

Patch Changes​

  • 04a54e2: Switched the compilation target to ES2024, which all supported Node.js versions fully support. Package builds, app bundles, and the backend development server now compile code for ES2024, and the TypeScript target and lib options in @backstage/cli/config/tsconfig.json are set to ES2024. This requires TypeScript 5.9 or later, which is now the oldest supported version according to the versioning policy.

    The lib change allows code to use ES2024 built-in APIs such as Object.groupBy and Promise.withResolvers. Backstage doesn't include polyfills, so frontend code that uses these APIs needs at least Chrome or Edge 119, Firefox 121, or Safari 17.4.

  • ed81712: Fixed backstage-cli package start and backstage-cli repo start so the --require flag can be repeated again. repo start also forwards every --require from a backend package's start script, instead of only the last one.

  • ed81712: Added --import flag to backstage-cli repo start and backstage-cli package start. This flag can be specified multiple times and is forwarded to the underlying node process.

  • ed8f1ef: Updated dependency @module-federation/sdk to ~2.9.0. Updated dependency @module-federation/enhanced to ~2.9.0. Updated dependency @module-federation/runtime to ~2.9.0. Updated dependency @module-federation/runtime-core to ~2.9.0.

  • 20e14f5: Updated dependency @types/react-dom to 19.3.0. Updated dependency react to 19.3.0. Updated dependency react-dom to 19.3.0. Updated dependency react-refresh to ^0.19.0.

  • 9120c46: Updated dependency glob to ^14.0.0.

  • Updated dependencies

    • @backstage/cli-node@0.3.6
    • @backstage/errors@1.4.0
    • @backstage/module-federation-common@0.1.7
    • @backstage/cli-common@0.3.3
    • @backstage/config@1.3.11
    • @backstage/config-loader@1.11.5

@backstage/cli-module-catalog@0.2.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4
    • @backstage/cli-node@0.3.6
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/filter-predicates@0.2.1

@backstage/cli-module-config@0.1.9​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/cli-common@0.3.3
    • @backstage/config@1.3.11
    • @backstage/config-loader@1.11.5

@backstage/cli-module-github@0.1.6​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/cli-common@0.3.3

@backstage/cli-module-info@0.1.6​

Patch Changes​

  • 1892d2f: chore(deps): bump minimatch from 10.2.6 to 11.0.1
  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/cli-common@0.3.3

@backstage/cli-module-lint@0.1.7​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/cli-common@0.3.3

@backstage/cli-module-maintenance@0.1.7​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/cli-common@0.3.3

@backstage/cli-module-migrate@0.2.3​

Patch Changes​

  • 1892d2f: chore(deps): bump minimatch from 10.2.6 to 11.0.1
  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/errors@1.4.0
    • @backstage/release-manifests@0.0.16
    • @backstage/cli-common@0.3.3

@backstage/cli-module-new@0.1.9​

Patch Changes​

  • b937434: Fixed backstage-cli new rewriting the entire CODEOWNERS file when an owner is provided. Existing content, including comments and formatting, is now preserved and a single repository-relative entry such as /packages/my-lib/ @org/team is appended, rather than an entry with an absolute filesystem path.
  • c009ae4: The frontend-plugin template now declares package info: the generated package.json exports ./package.json, and the plugin passes info: { packageJson: () => import('../package.json') } to createFrontendPlugin.
  • 500f8ff: Templates now depend on @testing-library/react 16 together with @testing-library/dom 10, which React Testing Library 16 requires as a peer dependency and which matches @backstage/frontend-test-utils.
  • c584676: Template version hints are now treated as a minimum version within their caret range, that is the same major version, or the same minor version for 0.x hints. When the lockfile already contains a range for a dependency that resolves to the hinted version or a newer compatible one, backstage-cli new reuses the highest such range instead of adding an older one, which avoids duplicate dependency versions.
  • e769ccb: Fix an issue where creating a new package with the cli-module role would crash during the installation phase due to an unhandled role mapping.
  • 33894d6: Fixed an issue where scaffolding templates on Windows could generate corrupted file names for files in subdirectories.
  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/errors@1.4.0
    • @backstage/cli-common@0.3.3

@backstage/cli-module-package-manager-yarn@0.1.5​

Patch Changes​

  • 1cffd6f: Made @yarnpkg/cli, @yarnpkg/core, and @yarnpkg/plugin-patch optional peer dependencies. @yarnpkg/core@4.9.2 was published with a dependency on a patch file that only exists in the Yarn repository, which made installation fail for all projects depending on this module. To use the pm verify-patches command until this is fixed upstream, add these packages as devDependencies in your root package.json, together with the resolution "@yarnpkg/core/got": "npm:^11.8.6". They will become regular dependencies again once a fixed version of @yarnpkg/core is published.
  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/release-manifests@0.0.16
    • @backstage/cli-common@0.3.3

@backstage/cli-module-scaffolder@0.2.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4
    • @backstage/cli-node@0.3.6
    • @backstage/errors@1.4.0

@backstage/cli-module-search@0.2.1​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/errors@1.4.0

@backstage/cli-module-test-jest@0.1.8​

Patch Changes​

  • 9120c46: Updated dependency glob to ^14.0.0.
  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/cli-common@0.3.3

@backstage/cli-module-translations@0.1.6​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/cli-common@0.3.3

@backstage/cli-node@0.3.6​

Patch Changes​

  • 4294614: Commands run through runCli now exit with the exit code they set, instead of always exiting with 0 on completion. For example, catalog validate and template dry-run now exit with a non-zero code when the input is invalid.

  • a96b99c: The Node.js module transform now uses the synchronous module.registerHooks() API when it is available, which avoids the module.register() deprecation warning printed by Node.js 26. On older Node.js versions it continues to use module.register().

  • 8069934: Fixed the Node.js module transform loading ES module JavaScript files from packages without a "type" field as CommonJS, which broke named imports such as import { DefaultGithubCredentialsProvider } from '@backstage/integration' during local development. The format of these files is now detected by Node.js, while TypeScript files in such packages are still treated as CommonJS.

  • 27b7aaa: Support loading remote frontend features whose default export is a FrontendFeatureLoader and include that feature type in generated package metadata.

  • 04a54e2: Switched the compilation target to ES2024, which all supported Node.js versions fully support. Package builds, app bundles, and the backend development server now compile code for ES2024, and the TypeScript target and lib options in @backstage/cli/config/tsconfig.json are set to ES2024. This requires TypeScript 5.9 or later, which is now the oldest supported version according to the versioning policy.

    The lib change allows code to use ES2024 built-in APIs such as Object.groupBy and Promise.withResolvers. Backstage doesn't include polyfills, so frontend code that uses these APIs needs at least Chrome or Edge 119, Firefox 121, or Safari 17.4.

  • Updated dependencies

    • @backstage/errors@1.4.0
    • @backstage/cli-common@0.3.3

@backstage/config@1.3.11​

Patch Changes​

  • Updated dependencies
    • @backstage/errors@1.4.0

@backstage/config-loader@1.11.5​

Patch Changes​

  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/cli-common@0.3.3
    • @backstage/config@1.3.11

@backstage/connections@0.4.2​

Patch Changes​

  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11

@backstage/core-app-api@1.20.7​

Patch Changes​

  • 9c97ff4: Fixed the OAuth "Login Required" popup (OAuthRequestDialog) appearing after a transient network failure during a background token refresh — for example right after the machine wakes from sleep, when the session has not actually expired.
  • 25297de: Fixed translation subscriptions failing when an abandoned language load rejects after switching to a language whose translations are already available.
  • 2aa14e3: Backstage UI links and collections now use client-side navigation at their consuming route scope, and apps with a custom Router that provides no React Router context render without failing at startup. See the 1.57 migration notes for detailed migration steps.
  • 7285912: Translation snapshots now provide t while resources are loading, using available messages and language fallbacks. Check ready before rendering to wait for the selected language.
  • 8688124: Fix unexpected sign-in prompts when multiple tabs refresh a session at the same time with an auth provider that rotates refresh tokens. Refresh requests are coordinated across tabs in browsers that support the Web Locks API.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/ui@0.20.0
    • @backstage/version-bridge@1.1.0
    • @backstage/config@1.3.11

@backstage/core-components@0.18.16​

Patch Changes​

  • 1c75912: Deprecated components with Backstage UI replacements or compositions: Avatar, Link, LinkButton, Select, Content, BottomLink, HeaderActionMenu, HeaderLabel, HeaderTabs, ItemCardGrid, ItemCardHeader, TabbedCard, CardTab, SubvalueCell, CreateButton, ContentHeader, FavoriteToggle, FavoriteToggleIcon, HeaderIconLinkRow, IconLinkVertical, and OverflowTooltip, along with their associated public types.

    Use the replacements from @backstage/ui described in each component's deprecation notice. These migrations require adapting props and composition, including external-link presentation, selection callbacks, document titles, and error boundaries where applicable. Existing exports and runtime behavior are unchanged.

  • cac9654: MarkdownContent now loads react-markdown and its remark and rehype plugins the first time it renders, instead of with the app. This keeps them out of the app's startup bundle. Markdown appears once the renderer has loaded, so tests that look for rendered markdown right after a synchronous render may need to use findBy* queries instead.

  • 7890ec2: Deprecated legacy page shells (Page, PageWithHeader, Header), routed tabs (TabbedLayout, TabbedLayout.Route, RoutedTabs), AlertDisplay, AppIcon, the named icon wrappers, and their associated public types for new frontend development. Existing exports and behavior remain available, including in migrated plugins.

    Use page and sub-page extensions and PageLayout from @backstage/frontend-plugin-api for framework-managed pages, or compose @backstage/ui headers and tabs with explicit routing for standalone layouts. Legacy themes, arbitrary header content, document titles, and focus behavior need deliberate migration. Rely on the new frontend app's existing alert/toast display. For app-customizable icons, use useApi(coreApis.icons).icon(key) from @backstage/frontend-plugin-api and render the returned element, handling missing icons as needed.

  • Updated dependencies

    • @backstage/core-plugin-api@1.13.0
    • @backstage/errors@1.4.0
    • @backstage/ui@0.20.0
    • @backstage/theme@0.7.4
    • @backstage/version-bridge@1.1.0
    • @backstage/config@1.3.11

@backstage/create-app@0.9.4​

Patch Changes​

  • bdbbe91: Bumped create-app version.

  • 04a54e2: Bumped TypeScript in the app templates to ~5.9.0.

  • b8777d1: New apps now support Node.js 24 and 26, in line with the versioning policy. The engines field in the app template is set to ^24.15.0 || ^26.13.0, and creating a new app now requires Node.js 24 (24.15.0 or later) or Node.js 26 (26.13.0 or later). 24.15.0 is the lowest version that all dependencies support, and 26.13.0 is the first Node.js 26 LTS release.

    To update an existing app, set engines.node in your root package.json to ^24.15.0 || ^26.13.0, and update the Node.js version used in your CI workflows and Dockerfile if needed.

    If your yarn.lock resolves avsc to a version older than 5.7.8, run yarn up -R avsc. Those versions crash on load on Node.js 25 and later, which breaks Jest tests that import the AsyncAPI widget from @backstage/plugin-api-docs. If it resolves node-gyp to 12.3.0, run yarn up -R node-gyp, since that version can't download Node.js headers through a proxy on Node.js 26.

  • 77f9227: New apps now declare support for light and dark color schemes and apply the stored theme choice before the app loads. The browser's default page background, scrollbars and form controls then match the theme during loading, instead of always starting out light. A new public/theme.js applies a stored light or dark choice, and the OS preference is used otherwise.

    To add this to an existing app, copy packages/app/public/theme.js from a newly created app, and add <meta name="color-scheme" content="light dark" /> and <script src="<%= publicPath %>/theme.js"></script> to the <head> of packages/app/public/index.html.

  • Updated dependencies

    • @backstage/cli-common@0.3.3

@backstage/eslint-plugin@0.3.4​

Patch Changes​

  • 1892d2f: chore(deps): bump minimatch from 10.2.6 to 11.0.1
  • 245d9e3: Internal changes for TypeScript 7 compatibility. The rules work the same as before.

@backstage/filter-predicates@0.2.1​

Patch Changes​

  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11

@backstage/frontend-defaults@0.5.8​

Patch Changes​

  • d514e4d: Updated app options to use the ExtensionFactoryMiddleware type from @backstage/frontend-app-api instead of the deprecated export from @backstage/frontend-plugin-api. Middleware behavior is unchanged.
  • f747f16: Removed the outdated warning that the frontend system is in alpha. This package remains on 0.x.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • 2aa14e3: Apps now release their browser history listener when the React root is removed or a hot refresh replaces the app within the existing root. See the 1.57 migration notes for background on app-owned history.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/plugin-app@0.6.0
    • @backstage/frontend-app-api@1.0.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11

@backstage/frontend-dynamic-feature-loader@0.1.18​

Patch Changes​

  • 27b7aaa: Support loading remote frontend features whose default export is a FrontendFeatureLoader and include that feature type in generated package metadata.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • ed8f1ef: Updated dependency @module-federation/sdk to ~2.9.0. Updated dependency @module-federation/enhanced to ~2.9.0. Updated dependency @module-federation/runtime to ~2.9.0. Updated dependency @module-federation/runtime-core to ~2.9.0.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/module-federation-common@0.1.7
    • @backstage/config@1.3.11

@backstage/integration-aws-node@0.2.4​

Patch Changes​

  • f81ca4e: Credential providers returned by DefaultAwsCredentialsManager now include a roleArn field with the ARN of the IAM role the credentials are for, when the account is configured to assume a role.
  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/connections@0.4.2

@backstage/module-federation-common@0.1.7​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • ed8f1ef: Updated dependency @module-federation/sdk to ~2.9.0. Updated dependency @module-federation/enhanced to ~2.9.0. Updated dependency @module-federation/runtime to ~2.9.0. Updated dependency @module-federation/runtime-core to ~2.9.0.
  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11

@backstage/release-manifests@0.0.16​

Patch Changes​

  • b8777d1: Updated the requirements example in the README to the Node.js 24 and 26 range.

@backstage/repo-tools@0.19.3​

Patch Changes​

  • 1892d2f: chore(deps): bump minimatch from 10.2.6 to 11.0.1
  • 11437a9: The type-deps command now fails with a clear error when no packages with built type declarations are found, instead of silently passing. Make sure to build all packages before running it.
  • 7d58727: The peer dependency checks now expect React 18 for frontend packages, following the removal of React 17 support across the workspace. The old frontend system core packages continue to allow React 17.
  • 9120c46: Updated dependency glob to ^14.0.0.
  • 5eb2381: The generated API reference documentation no longer overwrites pages when a package exports declarations whose names only differ in case, or that share a name but are of different kinds, for example a variable and an interface or namespace. One of them keeps the existing page, and the others get a page with their kind added to the filename, for example -interface or -namespace, or a number if they are of the same kind.
  • fbb676e: The package schema openapi generate command now exits with a non-zero code when client or server generation fails, for example when linting the generated code fails. Previously the failure was logged but the command still exited with code 0. Watch mode is unaffected and keeps watching after a failed generation.
  • 1fba2bb: The peer dependency check no longer enforces a shared react-router-dom version, so packages can declare their own supported major version. See the 1.57 migration notes for background on the routing changes this supports.
  • Updated dependencies
    • @backstage/cli-node@0.3.6
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/cli-common@0.3.3
    • @backstage/config-loader@1.11.5

@backstage/theme@0.7.4​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

@backstage/plugin-api-docs@0.14.7​

Patch Changes​

  • a44c5eb: The AsyncAPI definition widget no longer resolves external references by default. References to whole external documents still render, with a placeholder naming the document that was not loaded; references that point into an external document (using a # fragment) fail to render with an error naming the reference. To resolve external references — for example to reach internal schema registries that require authentication — provide the resolvers prop to enable external reference resolution.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/plugin-catalog@2.1.0
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/ui@0.20.0
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-catalog-common@1.2.2

@backstage/plugin-api-docs-module-protoc-gen-doc@0.1.12​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.

@backstage/plugin-app-backend@0.5.20​

Patch Changes​

  • 11f4455: Documented that if your package manager doesn't hoist workspace packages, for example pnpm with hoistWorkspacePackages: false, you need to add the app package to the dependencies of the root package.json.
  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.
  • 2fea3e2: Reduced startup database traffic and memory usage when checking for previously cached static assets.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/config@1.3.11
    • @backstage/config-loader@1.11.5
    • @backstage/plugin-app-node@0.1.51

@backstage/plugin-app-module-user-settings@0.1.4​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/plugin-signals-react@0.0.28
    • @backstage/plugin-user-settings@0.9.9

@backstage/plugin-app-node@0.1.51​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/config-loader@1.11.5

@backstage/plugin-app-visualizer@0.2.10​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/ui@0.20.0

@backstage/plugin-auth@0.1.14​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/errors@1.4.0
    • @backstage/ui@0.20.0
    • @backstage/theme@0.7.4

@backstage/plugin-auth-backend-module-atlassian-provider@0.5.1​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-auth0-provider@0.4.7​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-aws-alb-provider@0.4.22​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/plugin-auth-backend@0.31.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-azure-easyauth-provider@0.2.26​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/catalog-model@1.10.3

@backstage/plugin-auth-backend-module-bitbucket-provider@0.3.21​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-bitbucket-server-provider@0.2.21​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-cloudflare-access-provider@0.5.2​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/config@1.3.11

@backstage/plugin-auth-backend-module-gcp-iap-provider@0.4.21​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-github-provider@0.5.9​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-auth-backend-module-gitlab-provider@0.4.9​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-google-provider@0.3.21​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-guest-provider@0.2.25​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/catalog-model@1.10.3

@backstage/plugin-auth-backend-module-microsoft-provider@0.3.21​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-oauth2-provider@0.4.21​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-oauth2-proxy-provider@0.3.5​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-oidc-provider@0.4.23​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/plugin-auth-backend@0.31.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/config@1.3.11

@backstage/plugin-auth-backend-module-okta-provider@0.2.21​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-onelogin-provider@0.3.21​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8

@backstage/plugin-auth-backend-module-openshift-provider@0.1.13​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/catalog-model@1.10.3

@backstage/plugin-auth-backend-module-pinniped-provider@0.3.20​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/config@1.3.11

@backstage/plugin-auth-backend-module-vmware-cloud-provider@0.5.20​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/catalog-model@1.10.3

@backstage/plugin-auth-node@0.7.8​

Patch Changes​

  • 918ca98: Updated dependency jose to ^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.
  • Updated dependencies
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11

@backstage/plugin-auth-react@0.1.33​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0

@backstage/plugin-bitbucket-cloud-common@0.3.15​

Patch Changes​

  • ed1cb3e: Added BitbucketCloudClient.searchWorkspaceCode and the CodeSearch types for the workspace code search API of Bitbucket Cloud (POST /2.0/workspaces/{workspace}/codesearch). This API needs a credential that identifies a user, with the scopes read:repository:bitbucket and read:workspace:bitbucket. Bitbucket Cloud rejects app passwords, legacy OAuth consumers, and API keys for this API with BitbucketCloudApiError status 403.

    Added BitbucketCloudClient.repositorySourceFileExists, BitbucketCloudClient.listRepositorySource, and BitbucketCloudApiError so callers can fall back to the Bitbucket Cloud source API when workspace code search is unavailable.

    Deprecated BitbucketCloudClient.searchCode, because Bitbucket Cloud removes the endpoint that it uses on 2026-11-15.

  • Updated dependencies

    • @backstage/integration@2.2.0

@backstage/plugin-catalog-backend@4.0.3​

Patch Changes​

  • 9c76a81: Documented that the entities/by-query endpoint currently applies only the first orderField; any additional order fields are ignored. Updated the OpenAPI spec parameter description and the Software Catalog API docs accordingly. No behavior change. Refs #17560.

  • 7d765b6: Improved repository validation for catalog entity placeholders. Placeholder-driven reads, including $openapi and $asyncapi document references, are now restricted to the entity's own repository on SCM hosts; cross-repository references are rejected.

  • 2c223ee: Fixed a Item of type "refresh" was emitted after processing had completed warning that could appear when one of several placeholders in an entity failed to resolve. Processing now waits for all placeholders to finish before reporting the first failure.

  • c4b7cb1: The entities/by-refs endpoint now resolves entity references case-insensitively, matching entities/by-name and the documented entity reference contract where receivers treat refs case-insensitively. Previously, a ref whose casing differed from the stored lowercased ref returned null. Fixes #36743.

  • 3b97016: Improved the performance of entity facets and total item counts on PostgreSQL when the filter contains $any or $not conditions, such as those produced by conditional permission policies for catalog entity reads.

  • 3b97016: Entity filter predicates that combine $all, $any or $not with other keys in the same object, or that give $all or $any a non-array value, are now rejected with a 400 error. Previously the extra keys were silently ignored.

  • cd5fa5f: Improved the performance of entity queries on PostgreSQL when a filter matches a field against a long list of values, such as the ownership claims used by conditional permission policies for catalog entity reads.

  • eb5875d: Improved repository validation for catalog entity placeholders on Azure DevOps. Placeholder-driven reads on a configured Azure DevOps integration are now restricted to the entity's own repository on every Azure DevOps host shape, including legacy {org}.visualstudio.com hosts and Azure DevOps Server hosts, and targets that cannot be attributed to a repository are rejected as well.

  • 32e6642: Adds internal publication bookkeeping as groundwork for future catalog change tracking. Existing catalog APIs and deletion behavior are unchanged.

    The PostgreSQL upgrade builds an index concurrently without rewriting existing entities, but still scans the catalog table. Large installations may need to prepare this index out of band before upgrading; see Upgrading large installations.

  • 2a9f08b: Match URL locations in catalog rules in canonical form.

    URL locations are now matched against catalog rules in a canonical form of the URL, so that rule decisions agree with how the location target is resolved when its content is fetched. URL patterns that relied on percent-encoded characters being matched as written, or on default ports being kept, no longer match and should be updated.

  • 1892d2f: chore(deps): bump minimatch from 10.2.6 to 11.0.1

  • f7ce914: Fixed an issue where /validate-entity would not return after sending a 400 response on invalid entity validation, causing an unhandled ERR_HTTP_HEADERS_SENT error and triggering duplicate success/fail audit events.

  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.

  • 9120c46: Updated dependency glob to ^14.0.0.

  • 20746bc: Location annotations on entities submitted to the validate-entity endpoint can no longer override the location of the request.

  • Updated dependencies

    • @backstage/integration@2.2.0
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/backend-openapi-utils@0.7.4
    • @backstage/plugin-events-node@0.5.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/filter-predicates@0.2.1
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6

@backstage/plugin-catalog-backend-module-ai-model@0.1.6​

Patch Changes​

  • f74cd6a: Document how to declare relation pairs for custom kinds when using the catalog model layer.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-aws@0.4.30​

Patch Changes​

  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4
    • @backstage/backend-defaults@0.19.0
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-kubernetes-common@0.9.15
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-azure@0.3.24​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-backstage-openapi@0.5.20​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/backend-openapi-utils@0.7.4
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-bitbucket-cloud@0.5.17​

Patch Changes​

  • ed1cb3e: The Bitbucket Cloud entity provider now finds catalog files with the workspace code search API of Bitbucket Cloud, because Bitbucket Cloud removes the old code search API on 2026-11-15. The provider finds the same locations for the same configuration.

    The new API needs a credential that identifies a user, for example an Atlassian account email as username with an API token. The token needs the scopes read:repository:bitbucket and read:workspace:bitbucket. The old API did not need read:workspace:bitbucket. Bitbucket Cloud rejects app passwords, legacy OAuth consumers, and API keys for this API. An API token without read:workspace:bitbucket is also rejected with 403. When that happens, or when code search is not enabled, the provider checks catalog files with the source API instead. Adding read:workspace:bitbucket to the API token restores workspace code search.

  • Updated dependencies

    • @backstage/integration@2.2.0
    • @backstage/plugin-bitbucket-cloud-common@0.3.15
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-bitbucket-server@0.5.17​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-gcp@0.3.25​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-kubernetes-common@0.9.15
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-gerrit@0.3.20​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-gitea@0.1.18​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-github@0.14.2​

Patch Changes​

  • 1892d2f: chore(deps): bump minimatch from 10.2.6 to 11.0.1
  • d926160: Added fetchEmailForGithubApps config option to the GitHub org entity providers (GithubOrgEntityProvider and GithubMultiOrgEntityProvider). When enabled, the provider requests the public email field from the GitHub GraphQL API even when using a GitHub App for authentication. By default, the public email is only requested with personal access tokens due to a historical GitHub API limitation that may no longer apply to all instances. If the GitHub instance does not support this, the user sync will fail — only enable it after confirming your GitHub App can access user emails.
  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-github-org@0.3.28​

Patch Changes​

  • d926160: Added fetchEmailForGithubApps config option to the GitHub org entity providers (GithubOrgEntityProvider and GithubMultiOrgEntityProvider). When enabled, the provider requests the public email field from the GitHub GraphQL API even when using a GitHub App for authentication. By default, the public email is only requested with personal access tokens due to a historical GitHub API limitation that may no longer apply to all instances. If the GitHub instance does not support this, the user sync will fail — only enable it after confirming your GitHub App can access user emails.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-catalog-backend-module-github@0.14.2
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-gitlab@0.8.11​

Patch Changes​

  • d586214: GitLab discovery entity provider: catalog locations and refresh keys resulting from push events are now derived from the project record fetched from the GitLab API, instead of fields of the event payload. Committed file paths that do not resolve within the project itself are ignored.
  • ca14116: Moved @gitbeaker/rest to dev dependencies, since it is only used for types.
  • Updated dependencies
    • @backstage/backend-defaults@0.19.0
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-gitlab-org@0.2.27​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-catalog-backend-module-gitlab@0.8.11
    • @backstage/plugin-events-node@0.5.0
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-incremental-ingestion@0.9.1​

Patch Changes​

  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.

  • 7baaad7: Fixed incremental ingestion getting stuck when a provider emits the same entity more than once in a single page or event. Since the previous release, this made every attempt to ingest that page fail on PostgreSQL with ON CONFLICT DO UPDATE command cannot affect row a second time, so the provider never got past it. Now only the last copy of each entity is kept. A warning names the provider and some of the repeated entity refs, at most once every 10 minutes per provider.

    Providers should still emit each entity at most once per page. If the copies differ and arrive in a different order on each run, the stored entity can change on every run.

  • Updated dependencies

    • @backstage/backend-defaults@0.19.0
    • @backstage/plugin-catalog-backend@4.0.3
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-catalog-backend-module-logs@0.1.28​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-catalog-backend@4.0.3
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0

@backstage/plugin-catalog-backend-module-msgraph@0.10.8​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-msgraph-incremental@0.1.6​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-catalog-backend-module-incremental-ingestion@0.9.1
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-backend-module-msgraph@0.10.8
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-openapi@0.2.28​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-puppetdb@0.2.28​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.2.26​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-scaffolder-common@2.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-catalog-backend-module-unprocessed@0.6.18​

Patch Changes​

  • af39b90: Fixed pending entities being returned without their entity ID and entity ref.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-catalog-unprocessed-entities-common@0.0.19
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-catalog-common@1.2.2​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-catalog-graph@0.6.10​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/catalog-client@1.16.4
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/ui@0.20.0
    • @backstage/catalog-model@1.10.3

@backstage/plugin-catalog-import@0.13.20​

Patch Changes​

  • 63d6533: The pull request preview card in the import flow now uses Backstage UI components.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/integration@2.2.0
    • @backstage/catalog-client@1.16.4
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/ui@0.20.0
    • @backstage/integration-react@1.3.0
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2

@backstage/plugin-catalog-node@3.0.0​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6

@backstage/plugin-catalog-unprocessed-entities@0.2.37​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/core-compat-api@0.6.0
    • @backstage/ui@0.20.0
    • @backstage/plugin-catalog-unprocessed-entities-common@0.0.19

@backstage/plugin-catalog-unprocessed-entities-common@0.0.19​

Patch Changes​

  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-config-schema@0.1.86​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0

@backstage/plugin-devtools@0.1.45​

Patch Changes​

  • ca1165d: Fixed an issue in ScheduledTasksContent where actual backend error messages (such as network or authorization errors) were discarded in favor of a hardcoded "No scheduled tasks found" message, and ensured the loading indicator is displayed while switching plugins.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/core-compat-api@0.6.0
    • @backstage/ui@0.20.0
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/plugin-devtools-common@0.1.28

@backstage/plugin-devtools-backend@0.5.23​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/cli-common@0.3.3
    • @backstage/config@1.3.11
    • @backstage/config-loader@1.11.5
    • @backstage/plugin-devtools-common@0.1.28
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6

@backstage/plugin-devtools-common@0.1.28​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-devtools-react@0.2.8​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0

@backstage/plugin-events-backend@0.6.8​

Patch Changes​

  • a1ca033: Fixed the database event bus listener connection inheriting the trace context of the request that first opened it. Its keepalive queries are now recorded as separate root spans instead of being attached to that request's trace for as long as the connection stays open.
  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.
  • a70aaea: The requests passed to request validators now include the parsed query string. The request rejection details now also support an optional contentType option for the provided payload, defaulting to application/json but also allowing text/plain.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/backend-openapi-utils@0.7.4
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11

@backstage/plugin-events-backend-module-aws-sqs@0.4.28​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11

@backstage/plugin-events-backend-module-bitbucket-cloud@0.2.37​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0

@backstage/plugin-events-backend-module-bitbucket-server@0.1.18​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0

@backstage/plugin-events-backend-module-gerrit@0.2.37​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0

@backstage/plugin-events-backend-module-google-pubsub@0.2.9​

Patch Changes​

  • b03427c: Updated dependency @google-cloud/pubsub to ^6.3.2. The new version requires Node.js 22 or later, which matches the Node.js versions that Backstage supports.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11
    • @backstage/filter-predicates@0.2.1

@backstage/plugin-events-backend-module-kafka@0.3.10​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11

@backstage/plugin-events-backend-test-utils@0.1.61​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0

@backstage/plugin-gateway-backend@1.1.11​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0

@backstage/plugin-home@0.9.12​

Patch Changes​

  • 0f93c60: The World Clock home page widget now uses Backstage UI components and styles instead of Material UI.
  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/catalog-client@1.16.4
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/core-compat-api@0.6.0
    • @backstage/ui@0.20.0
    • @backstage/core-app-api@1.20.7
    • @backstage/plugin-home-react@0.1.44
    • @backstage/theme@0.7.4
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11

@backstage/plugin-home-react@0.1.44​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/core-compat-api@0.6.0

@backstage/plugin-kubernetes@0.12.25​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/plugin-kubernetes-common@0.9.15
    • @backstage/plugin-kubernetes-react@0.6.2
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/catalog-model@1.10.3

@backstage/plugin-kubernetes-backend@0.21.13​

Patch Changes​

  • 68abde4: Allow AWS Kubernetes clusters to select credentials from a configured AWS account without assuming another role. Set kubernetes.io/aws-account-id in the cluster's auth metadata to use that account's credentials directly, including credentials obtained through web identity federation.
  • 0915584: Kubernetes proxy: stop forwarding the caller's Authorization and Cookie headers to the target cluster. Upstream requests now carry only credentials from the configured auth strategy or the Backstage-Kubernetes-Authorization header.
  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-kubernetes-common@0.9.15
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-kubernetes-node@0.4.10
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-kubernetes-cluster@0.0.43​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • ca14116: Moved kubernetes-models and @kubernetes-models/apimachinery to dev dependencies, since they are only used for types. Backends no longer install kubernetes-models through @backstage/plugin-kubernetes-common.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/plugin-kubernetes-common@0.9.15
    • @backstage/plugin-kubernetes-react@0.6.2
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/catalog-model@1.10.3

@backstage/plugin-kubernetes-common@0.9.15​

Patch Changes​

  • 68abde4: Allow AWS Kubernetes clusters to select credentials from a configured AWS account without assuming another role. Set kubernetes.io/aws-account-id in the cluster's auth metadata to use that account's credentials directly, including credentials obtained through web identity federation.
  • ca14116: Moved kubernetes-models and @kubernetes-models/apimachinery to dev dependencies, since they are only used for types. Backends no longer install kubernetes-models through @backstage/plugin-kubernetes-common.
  • Updated dependencies
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-kubernetes-node@0.4.10​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-kubernetes-common@0.9.15
    • @backstage/catalog-model@1.10.3

@backstage/plugin-kubernetes-react@0.6.2​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/plugin-kubernetes-common@0.9.15
    • @backstage/catalog-model@1.10.3

@backstage/plugin-mcp-actions-backend@0.2.4​

Patch Changes​

  • 1892d2f: chore(deps): bump minimatch from 10.2.6 to 11.0.1
  • 9e22c4b: OAuth discovery metadata is now also served when pre-registered clients are configured with auth.staticClients.
  • Updated dependencies
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-mui-to-bui@0.2.13​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/ui@0.20.0
    • @backstage/theme@0.7.4

@backstage/plugin-notifications@0.6.2​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • 555d6ff: Updated custom notification icons to use the element-based icons API. Missing icons still fall back to the notification severity icon.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/ui@0.20.0
    • @backstage/plugin-home-react@0.1.44
    • @backstage/plugin-signals-react@0.0.28
    • @backstage/theme@0.7.4
    • @backstage/plugin-notifications-common@0.2.6

@backstage/plugin-notifications-backend@0.6.11​

Patch Changes​

  • c0ea056: Fixed broadcast notifications losing their saved status when marked as read or unread, and losing their read status when saved or unsaved.
  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/backend-openapi-utils@0.7.4
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-notifications-common@0.2.6
    • @backstage/plugin-notifications-node@0.2.32
    • @backstage/plugin-signals-node@0.2.7

@backstage/plugin-notifications-backend-module-email@0.3.27​

Patch Changes​

  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-notifications-common@0.2.6
    • @backstage/plugin-notifications-node@0.2.32

@backstage/plugin-notifications-backend-module-slack@0.4.8​

Patch Changes​

  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-notifications-common@0.2.6
    • @backstage/plugin-notifications-node@0.2.32

@backstage/plugin-notifications-common@0.2.6​

Patch Changes​

  • Updated dependencies
    • @backstage/config@1.3.11

@backstage/plugin-notifications-node@0.2.32​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-notifications-common@0.2.6

@backstage/plugin-org@0.8.1​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/ui@0.20.0
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-catalog-common@1.2.2

@backstage/plugin-org-react@0.1.56​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/catalog-client@1.16.4
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/catalog-model@1.10.3

@backstage/plugin-permission-backend@0.7.18​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/config@1.3.11
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6

@backstage/plugin-permission-backend-module-allow-all-policy@0.2.25​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6

@backstage/plugin-permission-common@0.9.13​

Patch Changes​

  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11

@backstage/plugin-permission-node@0.11.6​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-permission-react@0.5.7​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/config@1.3.11
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-proxy-backend@0.6.20​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-proxy-node@0.1.21

@backstage/plugin-proxy-node@0.1.21​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0

@backstage/plugin-scaffolder-backend-module-azure@0.2.28​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.3.13​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/plugin-bitbucket-cloud-common@0.3.15
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-bitbucket-server@0.2.28​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-confluence-to-markdown@0.3.28​

Patch Changes​

  • 076f478: Fixed the Confluence to Markdown action leaking a file handle for every attachment it downloaded. A download that failed partway through also left the scaffolder step hanging. It now fails with the underlying error.
  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-cookiecutter@0.3.29​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-gerrit@0.2.27​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-gitea@0.2.27​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-github@0.10.2​

Patch Changes​

  • 1368ad3: Added a github:repo:rulesets:create action that creates a ruleset in a GitHub repository. Rules and bypass actors are written in the same format as the GitHub REST API, so any rule type that GitHub supports can be used in templates.
  • 6c43d4f: Validates the targetPath input of the gitlab:repo:push, publish:gitlab:merge-request and publish:github:pull-request scaffolder actions, and the filesToDelete entries of publish:github:pull-request. The values must be relative paths within the target repository; absolute paths and paths containing .. segments are now rejected, so changes are only applied inside the intended subdirectory of the repository.
  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-gitlab@0.12.2​

Patch Changes​

  • ae86338: Added GitLab branch autocompletion to RepoBranchPicker using user SCM credentials.
  • 6c43d4f: Validates the targetPath input of the gitlab:repo:push, publish:gitlab:merge-request and publish:github:pull-request scaffolder actions, and the filesToDelete entries of publish:github:pull-request. The values must be relative paths within the target repository; absolute paths and paths containing .. segments are now rejected, so changes are only applied inside the intended subdirectory of the repository.
  • ed8e58f: Fixed publish:gitlab:merge-request and gitlab:repo:push failing with "A file with this name already exists" when commitAction is auto and the repository file list cannot be fetched, for example when the request times out on a large repository. The actions now check each file individually in that case, instead of treating every file as new.
  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-notifications@0.1.28​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-notifications-common@0.2.6
    • @backstage/plugin-notifications-node@0.2.32
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-rails@0.5.27​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-sentry@0.4.2​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-workspace-database@0.1.2​

Patch Changes​

  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-backend-module-yeoman@0.4.28​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-scaffolder-node-test-utils@0.3.17
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-scaffolder-node@1.0.0​

Patch Changes​

  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-scaffolder-common@2.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6

@backstage/plugin-scaffolder-node-test-utils@0.3.17​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/backend-test-utils@1.12.0
    • @backstage/plugin-scaffolder-node@1.0.0

@backstage/plugin-search-backend@2.1.9​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/backend-openapi-utils@0.7.4
    • @backstage/config@1.3.11
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6
    • @backstage/plugin-search-backend-node@1.4.10
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-search-backend-module-catalog@0.3.21​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-search-backend-node@1.4.10
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-search-backend-module-elasticsearch@2.0.2​

Patch Changes​

  • 8da9c23: Internal changes for TypeScript 7 compatibility. There are no changes to behavior or the public API.
  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/config@1.3.11
    • @backstage/plugin-search-backend-node@1.4.10
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-search-backend-module-explore@0.3.20​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/config@1.3.11
    • @backstage/plugin-search-backend-node@1.4.10
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-search-backend-module-pg@0.5.61​

Patch Changes​

  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.
  • 39cda0c: Avoid recomputing full-text search tsvector data for unchanged documents during indexing.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/config@1.3.11
    • @backstage/plugin-search-backend-node@1.4.10
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-search-backend-module-stack-overflow-collator@0.3.26​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/config@1.3.11
    • @backstage/plugin-search-backend-node@1.4.10
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-search-backend-module-techdocs@0.4.20​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-techdocs-node@2.3.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-search-backend-node@1.4.10
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-search-backend-node@1.4.10​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-search-common@1.2.27

@backstage/plugin-search-common@1.2.27​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-signals@0.0.37​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/plugin-signals-react@0.0.28
    • @backstage/theme@0.7.4

@backstage/plugin-signals-backend@0.3.21​

Patch Changes​

  • bcb1697: Register WebSocket upgrades through the framework router so the first connection works without a prior HTTP request. Preserve user-only authentication and existing token-as-protocol clients, while keeping only the health endpoint public over HTTP.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0
    • @backstage/config@1.3.11
    • @backstage/plugin-signals-node@0.2.7

@backstage/plugin-signals-node@0.2.7​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-events-node@0.5.0

@backstage/plugin-signals-react@0.0.28​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0

@backstage/plugin-techdocs-backend@2.4.3​

Patch Changes​

  • 4d7a3fe: Clarified in the config schema which techdocs.generator.mkdocs settings also apply to the Zensical engine: legacyCopyReadmeMdToIndexMd, dangerouslyAllowAdditionalKeys and dangerouslyAllowAdditionalPlugins.
  • bc73976: Restricts markdown_extensions in mkdocs.yml to known extension names before documentation generation, in both the MkDocs and Zensical engines. Extension names outside the permitted set are removed from the configuration with a warning. Allow additional extensions, for example from a custom build image, with the new techdocs.generator.mkdocs.dangerouslyAllowAdditionalExtensions configuration, or the --dangerouslyAllowAdditionalExtensions flag when using the TechDocs CLI.
  • Updated dependencies
    • @backstage/integration@2.2.0
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-techdocs-node@2.3.0
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-node@3.0.0
    • @backstage/plugin-techdocs-common@0.1.3

@backstage/plugin-techdocs-common@0.1.3​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-permission-common@0.9.13

@backstage/plugin-user-settings@0.9.9​

Patch Changes​

  • 4bbc7a9: Removed explicit support for React 17: the peer dependency range for react, react-dom and @types/react is now ^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.
  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16
    • @backstage/errors@1.4.0
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/ui@0.20.0
    • @backstage/core-app-api@1.20.7
    • @backstage/plugin-signals-react@0.0.28
    • @backstage/theme@0.7.4
    • @backstage/catalog-model@1.10.3

@backstage/plugin-user-settings-backend@0.4.9​

Patch Changes​

  • 6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.
  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/plugin-signals-node@0.2.7

example-app@0.0.41​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-api-docs@0.14.7
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-plugin-api@1.13.0
    • @backstage/plugin-app-react@0.3.0
    • @backstage/plugin-app@0.6.0
    • @backstage/frontend-app-api@1.0.0
    • @backstage/frontend-defaults@0.5.8
    • @backstage/plugin-catalog@2.1.0
    • @backstage/plugin-catalog-import@0.13.20
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/cli@0.36.8
    • @backstage/plugin-scaffolder-react@3.0.0
    • @backstage/plugin-devtools@0.1.45
    • @backstage/plugin-scaffolder@1.41.0
    • @backstage/plugin-home@0.9.12
    • @backstage/core-compat-api@0.6.0
    • @backstage/ui@0.20.0
    • @backstage/core-app-api@1.20.7
    • @backstage/integration-react@1.3.0
    • @backstage/app-defaults@1.8.0
    • @backstage/plugin-app-visualizer@0.2.10
    • @backstage/plugin-auth@0.1.14
    • @backstage/plugin-auth-react@0.1.33
    • @backstage/plugin-catalog-graph@0.6.10
    • @backstage/plugin-catalog-unprocessed-entities@0.2.37
    • @backstage/plugin-home-react@0.1.44
    • @backstage/plugin-kubernetes@0.12.25
    • @backstage/plugin-kubernetes-cluster@0.0.43
    • @backstage/plugin-notifications@0.6.2
    • @backstage/plugin-org@0.8.1
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/plugin-search@1.8.0
    • @backstage/plugin-search-react@1.12.0
    • @backstage/plugin-signals@0.0.37
    • @backstage/plugin-techdocs@1.20.0
    • @backstage/plugin-techdocs-module-addons-contrib@1.2.0
    • @backstage/plugin-techdocs-react@1.5.0
    • @backstage/plugin-user-settings@0.9.9
    • @backstage/theme@0.7.4
    • @backstage/plugin-app-module-user-settings@0.1.4
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-search-common@1.2.27

app-example-plugin@0.0.41​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/core-components@0.18.16

example-app-legacy@0.2.127​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-api-docs@0.14.7
    • @backstage/core-plugin-api@1.13.0
    • @backstage/frontend-app-api@1.0.0
    • @backstage/plugin-catalog@2.1.0
    • @backstage/plugin-catalog-import@0.13.20
    • @backstage/core-components@0.18.16
    • @backstage/plugin-catalog-react@4.0.0
    • @backstage/cli@0.36.8
    • @backstage/plugin-scaffolder-react@3.0.0
    • @backstage/plugin-devtools@0.1.45
    • @backstage/plugin-scaffolder@1.41.0
    • @backstage/plugin-home@0.9.12
    • @backstage/ui@0.20.0
    • @backstage/core-app-api@1.20.7
    • @backstage/integration-react@1.3.0
    • @backstage/app-defaults@1.8.0
    • @backstage/plugin-auth-react@0.1.33
    • @backstage/plugin-catalog-graph@0.6.10
    • @backstage/plugin-catalog-unprocessed-entities@0.2.37
    • @backstage/plugin-home-react@0.1.44
    • @backstage/plugin-kubernetes@0.12.25
    • @backstage/plugin-kubernetes-cluster@0.0.43
    • @backstage/plugin-mui-to-bui@0.2.13
    • @backstage/plugin-notifications@0.6.2
    • @backstage/plugin-org@0.8.1
    • @backstage/plugin-permission-react@0.5.7
    • @backstage/plugin-search@1.8.0
    • @backstage/plugin-search-react@1.12.0
    • @backstage/plugin-signals@0.0.37
    • @backstage/plugin-techdocs@1.20.0
    • @backstage/plugin-techdocs-module-addons-contrib@1.2.0
    • @backstage/plugin-techdocs-react@1.5.0
    • @backstage/plugin-user-settings@0.9.9
    • @backstage/theme@0.7.4
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11
    • @backstage/plugin-catalog-common@1.2.2
    • @backstage/plugin-search-common@1.2.27

example-backend@0.0.56​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-defaults@0.19.0
    • @backstage/plugin-auth-backend@0.31.0
    • @backstage/plugin-catalog-backend@4.0.3
    • @backstage/plugin-app-backend@0.5.20
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/plugin-mcp-actions-backend@0.2.4
    • @backstage/plugin-events-backend@0.6.8
    • @backstage/plugin-notifications-backend@0.6.11
    • @backstage/plugin-scaffolder-backend@4.3.0
    • @backstage/plugin-user-settings-backend@0.4.9
    • @backstage/plugin-catalog-backend-module-ai-model@0.1.6
    • @backstage/plugin-scaffolder-backend-module-github@0.10.2
    • @backstage/plugin-events-backend-module-google-pubsub@0.2.9
    • @backstage/plugin-kubernetes-backend@0.21.13
    • @backstage/plugin-signals-backend@0.3.21
    • @backstage/plugin-auth-node@0.7.8
    • @backstage/plugin-techdocs-backend@2.4.3
    • @backstage/plugin-techdocs-backend-module-zensical@0.1.0
    • @backstage/plugin-search-backend-module-elasticsearch@2.0.2
    • @backstage/plugin-catalog-backend-module-unprocessed@0.6.18
    • @backstage/catalog-model@1.10.3
    • @backstage/plugin-auth-backend-module-github-provider@0.5.9
    • @backstage/plugin-auth-backend-module-guest-provider@0.2.25
    • @backstage/plugin-auth-backend-module-openshift-provider@0.1.13
    • @backstage/plugin-catalog-backend-module-backstage-openapi@0.5.20
    • @backstage/plugin-catalog-backend-module-logs@0.1.28
    • @backstage/plugin-catalog-backend-module-openapi@0.2.28
    • @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.2.26
    • @backstage/plugin-devtools-backend@0.5.23
    • @backstage/plugin-permission-backend@0.7.18
    • @backstage/plugin-permission-backend-module-allow-all-policy@0.2.25
    • @backstage/plugin-permission-common@0.9.13
    • @backstage/plugin-permission-node@0.11.6
    • @backstage/plugin-proxy-backend@0.6.20
    • @backstage/plugin-scaffolder-backend-module-notifications@0.1.28
    • @backstage/plugin-search-backend@2.1.9
    • @backstage/plugin-search-backend-module-catalog@0.3.21
    • @backstage/plugin-search-backend-module-explore@0.3.20
    • @backstage/plugin-search-backend-module-techdocs@0.4.20
    • @backstage/plugin-search-backend-node@1.4.10

@internal/backend@0.0.6​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0

@internal/cli@0.0.7​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6

@backstage/connections-node@0.2.5​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/connections@0.4.2

e2e-test@0.2.46​

Patch Changes​

  • Updated dependencies
    • @backstage/create-app@0.9.4
    • @backstage/errors@1.4.0
    • @backstage/cli-common@0.3.3

@internal/frontend@0.0.26​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/errors@1.4.0
    • @backstage/version-bridge@1.1.0
    • @backstage/filter-predicates@0.2.1

@internal/scaffolder@0.0.27​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/plugin-scaffolder-react@3.0.0

@internal/secrets-node@0.0.1​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0

techdocs-cli-embedded-app@0.2.126​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@1.0.0
    • @backstage/plugin-app-react@0.3.0
    • @backstage/frontend-defaults@0.5.8
    • @backstage/plugin-catalog@2.1.0
    • @backstage/core-components@0.18.16
    • @backstage/cli@0.36.8
    • @backstage/test-utils@1.8.0
    • @backstage/ui@0.20.0
    • @backstage/core-app-api@1.20.7
    • @backstage/integration-react@1.3.0
    • @backstage/plugin-techdocs@1.20.0
    • @backstage/plugin-techdocs-react@1.5.0
    • @backstage/theme@0.7.4
    • @backstage/catalog-model@1.10.3
    • @backstage/config@1.3.11

yarn-plugin-backstage@0.0.16​

Patch Changes​

  • Updated dependencies
    • @backstage/errors@1.4.0
    • @backstage/release-manifests@0.0.16
    • @backstage/cli-common@0.3.3

@backstage/plugin-connections-example-backend@0.1.6​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-defaults@0.19.0
    • @backstage/catalog-client@1.16.4
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/connections@0.4.2
    • @backstage/plugin-catalog-node@3.0.0

@backstage/plugin-connections-example-backend-module-gitlab@0.1.6​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/config@1.3.11
    • @backstage/connections@0.4.2

@internal/plugin-todo-list@1.0.57​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.13.0
    • @backstage/core-components@0.18.16

@internal/plugin-todo-list-backend@1.0.56​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0

@internal/plugin-todo-list-common@1.0.34​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-permission-common@0.9.13

@internal/techdocs-zensical@0.0.1​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-plugin-api@1.12.0
    • @backstage/errors@1.4.0
    • @backstage/plugin-techdocs-node@2.3.0
    • @backstage/config@1.3.11