Skip to main content
Version: Next

Release v1.57.0-next.1

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

@backstage/frontend-app-api@0.17.0-next.1​

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.

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

  • Updated dependencies

    • @backstage/frontend-defaults@0.5.8-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/core-app-api@1.20.7-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/frontend-plugin-api@0.19.0-next.1​

Minor Changes​

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

  • 62268a9: BREAKING: Removed 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.

  • 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} />;
    }

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

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

@backstage/frontend-test-utils@0.7.0-next.1​

Minor Changes​

  • 76b1c3d: Removed the deprecated standalone mock API type exports. 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]>
    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. MockFetchApiOptions remains exported for configuring mockApis.fetch.

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

  • 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​

  • Updated dependencies
    • @backstage/frontend-app-api@0.17.0-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/plugin-app@0.6.0-next.1
    • @backstage/core-app-api@1.20.7-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-app-react@0.3.0-next.1

@backstage/plugin-app@0.6.0-next.1​

Minor Changes​

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

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

Patch Changes​

  • e55a4a8: Updated plugin identity handling to use pluginId, while preserving support for older plugin instances that only expose id.
  • 8f36712: Updated the app runtime to use the analytics implementation APIs from @backstage/plugin-app-react.
  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-app-react@0.3.0-next.1

@backstage/plugin-app-react@0.3.0-next.1​

Minor Changes​

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

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-events-node@0.5.0-next.1​

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.

@backstage/plugin-scaffolder-backend@4.3.0-next.1​

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​

  • 2fac95b: Group the Software Templates API documentation by functionality instead of placing all endpoints under "Untagged".
  • Updated dependencies
    • @backstage/plugin-scaffolder-common@2.4.0-next.0
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1
    • @backstage/plugin-scaffolder-node@0.13.9-next.1

@backstage/plugin-scaffolder-common@2.4.0-next.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.

@backstage/plugin-scaffolder-react@3.0.0-next.1​

Minor Changes​

  • 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​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-scaffolder-common@2.4.0-next.0
    • @backstage/plugin-catalog-react@4.0.0-next.1

@backstage/app-defaults@1.7.14-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/core-app-api@1.20.7-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/backend-defaults@0.18.2-next.1​

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.
  • 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-next.0
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-auth-node@0.7.8-next.1

@backstage/backend-dynamic-feature-service@0.8.9-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-defaults@0.18.2-next.1
    • @backstage/plugin-catalog-backend@4.0.3-next.1
    • @backstage/cli-node@0.3.6-next.1
    • @backstage/plugin-events-backend@0.6.8-next.1
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-auth-node@0.7.8-next.1
    • @backstage/plugin-scaffolder-node@0.13.9-next.1

@backstage/backend-test-utils@1.11.9-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-defaults@0.18.2-next.1
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-auth-node@0.7.8-next.1

@backstage/catalog-client@1.16.4-next.0​

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.

@backstage/cli@0.36.8-next.1​

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.

  • Updated dependencies

    • @backstage/cli-node@0.3.6-next.1
    • @backstage/cli-module-build@0.1.10-next.1

@backstage/cli-module-build@0.1.10-next.1​

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.

  • Updated dependencies

    • @backstage/cli-node@0.3.6-next.1

@backstage/cli-module-catalog@0.2.1-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/cli-node@0.3.6-next.1

@backstage/cli-module-migrate@0.2.3-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6-next.1
    • @backstage/release-manifests@0.0.16-next.0

@backstage/cli-module-new@0.1.9-next.1​

Patch Changes​

  • 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-next.1

@backstage/cli-module-package-manager-yarn@0.1.5-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/cli-node@0.3.6-next.1
    • @backstage/release-manifests@0.0.16-next.0

@backstage/cli-module-scaffolder@0.2.1-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/cli-node@0.3.6-next.1

@backstage/cli-node@0.3.6-next.1​

Patch Changes​

  • 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().

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

@backstage/core-app-api@1.20.7-next.1​

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.
  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1

@backstage/core-compat-api@0.5.17-next.1​

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/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-app-react@0.3.0-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1

@backstage/core-plugin-api@1.12.12-next.1​

Patch Changes​

  • 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@0.19.0-next.1

@backstage/create-app@0.9.4-next.1​

Patch Changes​

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

@backstage/frontend-defaults@0.5.8-next.1​

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.
  • Updated dependencies
    • @backstage/frontend-app-api@0.17.0-next.1
    • @backstage/plugin-app@0.6.0-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/frontend-dev-utils@0.1.8-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-defaults@0.5.8-next.1
    • @backstage/plugin-app@0.6.0-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/frontend-dynamic-feature-loader@0.1.18-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/integration-aws-node@0.2.4-next.0​

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.

@backstage/release-manifests@0.0.16-next.0​

Patch Changes​

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

@techdocs/cli@1.14.1-next.0​

Patch Changes​

  • Bumped version to account for a patch release.

@backstage/plugin-api-docs@0.14.7-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-catalog@2.0.11-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1

@backstage/plugin-app-module-user-settings@0.1.4-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-user-settings@0.9.9-next.1

@backstage/plugin-app-visualizer@0.2.10-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-auth@0.1.14-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-auth-backend@0.30.3-next.1​

Patch Changes​

  • 97ee785: Allow Cursor clients to use Client ID Metadata Documents by default.
  • Updated dependencies
    • @backstage/plugin-auth-node@0.7.8-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-auth-node@0.7.8-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0

@backstage/plugin-catalog@2.0.11-next.1​

Patch Changes​

  • 118d84a: Updated catalog tabs to render icon elements through the current frontend icon API.
  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/core-compat-api@0.5.17-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-scaffolder-common@2.4.0-next.0
    • @backstage/plugin-search-react@1.11.10-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1
    • @backstage/plugin-techdocs-react@1.4.1-next.1

@backstage/plugin-catalog-backend@4.0.3-next.1​

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.
  • 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.
  • 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.
  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

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

Patch Changes​

  • f74cd6a: Document how to declare relation pairs for custom kinds when using the catalog model layer.
  • Updated dependencies
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-catalog-backend-module-aws@0.4.30-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4-next.0
    • @backstage/backend-defaults@0.18.2-next.1
    • @backstage/plugin-kubernetes-common@0.9.15-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-catalog-backend-module-azure@0.3.24-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

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

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

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

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-catalog-backend-module-github@0.14.2-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

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

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1
    • @backstage/plugin-catalog-backend-module-github@0.14.2-next.1

@backstage/plugin-catalog-backend-module-gitlab@0.8.10-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-defaults@0.18.2-next.1
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

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

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1
    • @backstage/plugin-catalog-backend-module-gitlab@0.8.10-next.1

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

Patch Changes​

  • 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.18.2-next.1
    • @backstage/plugin-catalog-backend@4.0.3-next.1
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-catalog-backend-module-logs@0.1.28-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-catalog-backend@4.0.3-next.1
    • @backstage/plugin-events-node@0.5.0-next.1

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

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-scaffolder-common@2.4.0-next.0
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-catalog-graph@0.6.10-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1

@backstage/plugin-catalog-import@0.13.20-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1

@backstage/plugin-catalog-node@2.2.7-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0

@backstage/plugin-catalog-react@4.0.0-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/core-compat-api@0.5.17-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-catalog-unprocessed-entities@0.2.37-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-compat-api@0.5.17-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-devtools@0.1.45-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-compat-api@0.5.17-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-devtools-react@0.2.8-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-events-backend@0.6.8-next.1​

Patch 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.
  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

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

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

@backstage/plugin-events-backend-module-azure@0.2.37-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

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

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

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

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

@backstage/plugin-events-backend-module-gerrit@0.2.37-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

@backstage/plugin-events-backend-module-github@0.4.18-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

@backstage/plugin-events-backend-module-gitlab@0.3.18-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

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

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/plugin-events-node@0.5.0-next.1

@backstage/plugin-events-backend-module-kafka@0.3.10-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

@backstage/plugin-events-backend-test-utils@0.1.61-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

@backstage/plugin-home@0.9.12-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/core-compat-api@0.5.17-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/core-app-api@1.20.7-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1
    • @backstage/plugin-home-react@0.1.44-next.1

@backstage/plugin-home-react@0.1.44-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-compat-api@0.5.17-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-kubernetes@0.12.25-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-kubernetes-common@0.9.15-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1

@backstage/plugin-kubernetes-backend@0.21.13-next.1​

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.
  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4-next.0
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/plugin-kubernetes-common@0.9.15-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-kubernetes-common@0.9.15-next.1​

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.

@backstage/plugin-mcp-actions-backend@0.2.4-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-mui-to-bui@0.2.13-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-notifications@0.6.2-next.1​

Patch Changes​

  • 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/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-home-react@0.1.44-next.1

@backstage/plugin-notifications-backend@0.6.11-next.1​

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.
  • Updated dependencies
    • @backstage/plugin-catalog-node@2.2.7-next.1
    • @backstage/plugin-signals-node@0.2.7-next.1

@backstage/plugin-notifications-backend-module-email@0.3.27-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4-next.0
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-org@0.8.1-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1

@backstage/plugin-org-react@0.1.56-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1

@backstage/plugin-scaffolder@1.41.0-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-scaffolder-common@2.4.0-next.0
    • @backstage/plugin-scaffolder-react@3.0.0-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1
    • @backstage/plugin-home-react@0.1.44-next.1
    • @backstage/plugin-techdocs-react@1.4.1-next.1

@backstage/plugin-scaffolder-node@0.13.9-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-scaffolder-common@2.4.0-next.0

@backstage/plugin-search@1.7.10-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-search-react@1.11.10-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1
    • @backstage/plugin-home-react@0.1.44-next.1

@backstage/plugin-search-backend-module-catalog@0.3.21-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-search-backend-module-elasticsearch@2.0.2-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4-next.0

@backstage/plugin-search-backend-module-techdocs@0.4.20-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/plugin-techdocs-node@2.2.1-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-search-react@1.11.10-next.1​

Patch Changes​

  • 6c8a6b1: Fixed SearchFilter.Autocomplete with multiple clearing the typed text on every keystroke once a value was selected.
  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-signals@0.0.37-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-signals-backend@0.3.21-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1
    • @backstage/plugin-signals-node@0.2.7-next.1

@backstage/plugin-signals-node@0.2.7-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/plugin-events-node@0.5.0-next.1

@backstage/plugin-techdocs@1.19.1-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-search-react@1.11.10-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1
    • @backstage/plugin-techdocs-react@1.4.1-next.1

@backstage/plugin-techdocs-backend@2.4.2-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/plugin-techdocs-node@2.2.1-next.1
    • @backstage/plugin-catalog-node@2.2.7-next.1

@backstage/plugin-techdocs-module-addons-contrib@1.1.42-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-techdocs-react@1.4.1-next.1

@backstage/plugin-techdocs-node@2.2.1-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/integration-aws-node@0.2.4-next.0

@backstage/plugin-techdocs-react@1.4.1-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1

@backstage/plugin-user-settings@0.9.9-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/core-app-api@1.20.7-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1

example-app@0.0.41-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-app-api@0.17.0-next.1
    • @backstage/frontend-defaults@0.5.8-next.1
    • @backstage/cli@0.36.8-next.1
    • @backstage/core-compat-api@0.5.17-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/plugin-app@0.6.0-next.1
    • @backstage/core-app-api@1.20.7-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-app-react@0.3.0-next.1
    • @backstage/plugin-scaffolder-react@3.0.0-next.1
    • @backstage/plugin-search-react@1.11.10-next.1
    • @backstage/plugin-catalog@2.0.11-next.1
    • @backstage/plugin-notifications@0.6.2-next.1
    • @backstage/plugin-catalog-graph@0.6.10-next.1
    • @backstage/plugin-catalog-import@0.13.20-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1
    • @backstage/plugin-home@0.9.12-next.1
    • @backstage/plugin-org@0.8.1-next.1
    • @backstage/plugin-scaffolder@1.41.0-next.1
    • @backstage/plugin-techdocs@1.19.1-next.1
    • @backstage/app-defaults@1.7.14-next.1
    • @backstage/plugin-api-docs@0.14.7-next.1
    • @backstage/plugin-app-module-user-settings@0.1.4-next.1
    • @backstage/plugin-app-visualizer@0.2.10-next.1
    • @backstage/plugin-auth@0.1.14-next.1
    • @backstage/plugin-catalog-unprocessed-entities@0.2.37-next.1
    • @backstage/plugin-devtools@0.1.45-next.1
    • @backstage/plugin-home-react@0.1.44-next.1
    • @backstage/plugin-kubernetes@0.12.25-next.1
    • @backstage/plugin-search@1.7.10-next.1
    • @backstage/plugin-signals@0.0.37-next.1
    • @backstage/plugin-techdocs-module-addons-contrib@1.1.42-next.1
    • @backstage/plugin-techdocs-react@1.4.1-next.1
    • @backstage/plugin-user-settings@0.9.9-next.1

app-example-plugin@0.0.41-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@0.19.0-next.1

example-app-legacy@0.2.127-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-app-api@0.17.0-next.1
    • @backstage/cli@0.36.8-next.1
    • @backstage/core-plugin-api@1.12.12-next.1
    • @backstage/core-app-api@1.20.7-next.1
    • @backstage/plugin-scaffolder-react@3.0.0-next.1
    • @backstage/plugin-search-react@1.11.10-next.1
    • @backstage/plugin-catalog@2.0.11-next.1
    • @backstage/plugin-notifications@0.6.2-next.1
    • @backstage/plugin-catalog-graph@0.6.10-next.1
    • @backstage/plugin-catalog-import@0.13.20-next.1
    • @backstage/plugin-catalog-react@4.0.0-next.1
    • @backstage/plugin-home@0.9.12-next.1
    • @backstage/plugin-org@0.8.1-next.1
    • @backstage/plugin-scaffolder@1.41.0-next.1
    • @backstage/plugin-techdocs@1.19.1-next.1
    • @backstage/app-defaults@1.7.14-next.1
    • @backstage/plugin-api-docs@0.14.7-next.1
    • @backstage/plugin-catalog-unprocessed-entities@0.2.37-next.1
    • @backstage/plugin-devtools@0.1.45-next.1
    • @backstage/plugin-home-react@0.1.44-next.1
    • @backstage/plugin-kubernetes@0.12.25-next.1
    • @backstage/plugin-mui-to-bui@0.2.13-next.1
    • @backstage/plugin-search@1.7.10-next.1
    • @backstage/plugin-signals@0.0.37-next.1
    • @backstage/plugin-techdocs-module-addons-contrib@1.1.42-next.1
    • @backstage/plugin-techdocs-react@1.4.1-next.1
    • @backstage/plugin-user-settings@0.9.9-next.1

example-backend@0.0.56-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-defaults@0.18.2-next.1
    • @backstage/plugin-auth-backend@0.30.3-next.1
    • @backstage/plugin-catalog-backend@4.0.3-next.1
    • @backstage/plugin-notifications-backend@0.6.11-next.1
    • @backstage/plugin-catalog-backend-module-ai-model@0.1.6-next.1
    • @backstage/plugin-events-backend-module-google-pubsub@0.2.9-next.1
    • @backstage/plugin-kubernetes-backend@0.21.13-next.1
    • @backstage/plugin-scaffolder-backend@4.3.0-next.1
    • @backstage/plugin-events-backend@0.6.8-next.1
    • @backstage/plugin-search-backend-module-elasticsearch@2.0.2-next.1
    • @backstage/plugin-auth-node@0.7.8-next.1
    • @backstage/plugin-mcp-actions-backend@0.2.4-next.1
    • @backstage/plugin-search-backend-module-catalog@0.3.21-next.1
    • @backstage/plugin-search-backend-module-techdocs@0.4.20-next.1
    • @backstage/plugin-techdocs-backend@2.4.2-next.1
    • @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.2.26-next.1
    • @backstage/plugin-catalog-backend-module-logs@0.1.28-next.1
    • @backstage/plugin-signals-backend@0.3.21-next.1

@internal/frontend@0.0.26-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@0.19.0-next.1

@internal/scaffolder@0.0.27-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-scaffolder-react@3.0.0-next.1

techdocs-cli-embedded-app@0.2.126-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/frontend-defaults@0.5.8-next.1
    • @backstage/cli@0.36.8-next.1
    • @backstage/core-app-api@1.20.7-next.1
    • @backstage/frontend-plugin-api@0.19.0-next.1
    • @backstage/plugin-app-react@0.3.0-next.1
    • @backstage/plugin-catalog@2.0.11-next.1
    • @backstage/plugin-techdocs@1.19.1-next.1
    • @backstage/plugin-techdocs-react@1.4.1-next.1

yarn-plugin-backstage@0.0.16-next.0​

Patch Changes​

  • Updated dependencies
    • @backstage/release-manifests@0.0.16-next.0

@backstage/plugin-connections-example-backend@0.1.6-next.1​

Patch Changes​

  • Updated dependencies
    • @backstage/backend-defaults@0.18.2-next.1
    • @backstage/catalog-client@1.16.4-next.0
    • @backstage/plugin-catalog-node@2.2.7-next.1