fix(deps): update backstage monorepo (major) #39

Open
renovate-bot wants to merge 1 commit from renovate/major-backstage-monorepo into main
Member

This PR contains the following updates:

Package Change Age Confidence
@backstage/frontend-plugin-api (source) ^0.18.2 → ^1.0.0 age confidence
@backstage/frontend-test-utils (source) ^0.6.5 → ^1.0.0 age confidence
@backstage/plugin-catalog-node (source) ^2.2.6 → ^3.0.0 age confidence

Release Notes

backstage/backstage (@​backstage/frontend-plugin-api)

v1.0.0

Compare Source

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/backstage (@​backstage/frontend-test-utils)

v1.0.0

Compare Source

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 type Replacement type
    MockAlertApi ReturnType<typeof mockApis.alert>
    MockAnalyticsApi ReturnType<typeof mockApis.analytics>
    MockConfigApi ReturnType<typeof mockApis.config>
    MockErrorApi ReturnType<typeof mockApis.error>
    MockFeatureFlagsApi ReturnType<typeof mockApis.featureFlags>
    MockFetchApi ReturnType<typeof mockApis.fetch>
    MockPermissionApi ReturnType<typeof mockApis.permission>
    MockStorageApi ReturnType<typeof mockApis.storage>
    MockTranslationApi ReturnType<typeof mockApis.translation>
    MockErrorApiOptions NonNullable<Parameters<typeof mockApis.error>[0]>
    MockFetchApiOptions NonNullable<Parameters<typeof mockApis.fetch>[0]>
    MockFeatureFlagsApiOptions NonNullable<Parameters<typeof mockApis.featureFlags>[0]>
    ErrorWithContext ReturnType<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
backstage/backstage (@​backstage/plugin-catalog-node)

v3.0.0

Compare Source

Patch Changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@backstage/frontend-plugin-api](https://github.com/backstage/backstage) ([source](https://github.com/backstage/backstage/tree/HEAD/packages/frontend-plugin-api)) | [`^0.18.2` → `^1.0.0`](https://renovatebot.com/diffs/npm/@backstage%2ffrontend-plugin-api/0.18.2/1.0.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@backstage%2ffrontend-plugin-api/1.0.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@backstage%2ffrontend-plugin-api/0.18.2/1.0.0?slim=true) | | [@backstage/frontend-test-utils](https://github.com/backstage/backstage) ([source](https://github.com/backstage/backstage/tree/HEAD/packages/frontend-test-utils)) | [`^0.6.5` → `^1.0.0`](https://renovatebot.com/diffs/npm/@backstage%2ffrontend-test-utils/0.6.5/1.0.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@backstage%2ffrontend-test-utils/1.0.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@backstage%2ffrontend-test-utils/0.6.5/1.0.0?slim=true) | | [@backstage/plugin-catalog-node](https://backstage.io) ([source](https://github.com/backstage/backstage/tree/HEAD/plugins/catalog-node)) | [`^2.2.6` → `^3.0.0`](https://renovatebot.com/diffs/npm/@backstage%2fplugin-catalog-node/2.2.6/3.0.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@backstage%2fplugin-catalog-node/3.0.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@backstage%2fplugin-catalog-node/2.2.6/3.0.0?slim=true) | --- ### Release Notes <details> <summary>backstage/backstage (@&#8203;backstage/frontend-plugin-api)</summary> ### [`v1.0.0`](https://github.com/backstage/backstage/blob/HEAD/packages/frontend-plugin-api/CHANGELOG.md#100) [Compare Source](https://github.com/backstage/backstage/compare/40525466a0f70119579cbfc4a60b9d2aa6c8a52d...v1.0.0) ##### Major Changes - [`b3befd0`](https://github.com/backstage/backstage/commit/b3befd0): Released version 1.0 of this frontend framework package. Its public APIs are now stable under the [package versioning policy](https://backstage.io/docs/overview/versioning-policy/#package-versioning-policy). Alpha and beta APIs retain their existing stability levels. ##### Minor Changes - [`5a539ca`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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](https://backstage.io/docs/frontend-system/utility-apis/creating/#lazy-api-implementations) for lazy implementations, Suspense boundaries, and migration requirements. - [`d514e4d`](https://github.com/backstage/backstage/commit/d514e4d): **BREAKING**: Removed the deprecated `ExtensionFactoryMiddleware` type export. Import it from `@backstage/frontend-app-api` instead: ```diff -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`](https://github.com/backstage/backstage/commit/0a552cf): **BREAKING**: Removed the `ExtensionAttachTo` type export. Use `Extension<unknown>['attachTo']` if you need to reference the attachment type. - [`62268a9`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/86ff5a3): Removed the deprecated `PageTab` and `PluginOptions` types. Use `PageLayoutTab` and `CreateFrontendPluginOptions` instead. - [`8ae0b8e`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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: ```diff -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`](https://github.com/backstage/backstage/commit/dafdab8): **BREAKING**: Removed the deprecated `withApis` export. Wrap class components in a function component that uses `useApi` instead: ```tsx 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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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](https://backstage.io/docs/frontend-system/architecture/migrations#157) 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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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](https://backstage.io/docs/frontend-system/architecture/migrations#157). - [`9d0a31b`](https://github.com/backstage/backstage/commit/9d0a31b): Removed an unused `use-sync-external-store` dependency, which is no longer needed now that React 18 is the minimum supported version. - [`6928d62`](https://github.com/backstage/backstage/commit/6928d62): Fixed swappable components losing their mounted state when their props change. The resolved component remains stable while its props update. - [`641ac02`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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 - [@&#8203;backstage/errors](https://github.com/backstage/errors)@1.4.0 - [@&#8203;backstage/version-bridge](https://github.com/backstage/version-bridge)@1.1.0 - [@&#8203;backstage/config](https://github.com/backstage/config)@1.3.11 - [@&#8203;backstage/filter-predicates](https://github.com/backstage/filter-predicates)@0.2.1 </details> <details> <summary>backstage/backstage (@&#8203;backstage/frontend-test-utils)</summary> ### [`v1.0.0`](https://github.com/backstage/backstage/blob/HEAD/packages/frontend-test-utils/CHANGELOG.md#100) [Compare Source](https://github.com/backstage/backstage/compare/40525466a0f70119579cbfc4a60b9d2aa6c8a52d...v1.0.0) ##### Major Changes - [`b3befd0`](https://github.com/backstage/backstage/commit/b3befd0): Released version 1.0 of this frontend framework package. Its public APIs are now stable under the [package versioning policy](https://backstage.io/docs/overview/versioning-policy/#package-versioning-policy). Alpha and beta APIs retain their existing stability levels. ##### Minor Changes - [`76b1c3d`](https://github.com/backstage/backstage/commit/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 type | Replacement type | | ---------------------------- | -------------------------------------------------------------------- | | `MockAlertApi` | `ReturnType<typeof mockApis.alert>` | | `MockAnalyticsApi` | `ReturnType<typeof mockApis.analytics>` | | `MockConfigApi` | `ReturnType<typeof mockApis.config>` | | `MockErrorApi` | `ReturnType<typeof mockApis.error>` | | `MockFeatureFlagsApi` | `ReturnType<typeof mockApis.featureFlags>` | | `MockFetchApi` | `ReturnType<typeof mockApis.fetch>` | | `MockPermissionApi` | `ReturnType<typeof mockApis.permission>` | | `MockStorageApi` | `ReturnType<typeof mockApis.storage>` | | `MockTranslationApi` | `ReturnType<typeof mockApis.translation>` | | `MockErrorApiOptions` | `NonNullable<Parameters<typeof mockApis.error>[0]>` | | `MockFetchApiOptions` | `NonNullable<Parameters<typeof mockApis.fetch>[0]>` | | `MockFeatureFlagsApiOptions` | `NonNullable<Parameters<typeof mockApis.featureFlags>[0]>` | | `ErrorWithContext` | `ReturnType<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`](https://github.com/backstage/backstage/commit/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](https://backstage.io/docs/frontend-system/architecture/migrations#157) for detailed migration steps and the [routing test guide](https://backstage.io/docs/frontend-system/building-plugins/testing#navigation-and-app-history) for examples. - [`53ab1aa`](https://github.com/backstage/backstage/commit/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: ```ts 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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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`](https://github.com/backstage/backstage/commit/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](https://backstage.io/docs/frontend-system/architecture/migrations#157). - [`9d0a31b`](https://github.com/backstage/backstage/commit/9d0a31b): Removed an unused `use-sync-external-store` dependency, which is no longer needed now that React 18 is the minimum supported version. - [`ec245df`](https://github.com/backstage/backstage/commit/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 - [@&#8203;backstage/frontend-plugin-api](https://github.com/backstage/frontend-plugin-api)@1.0.0 - [@&#8203;backstage/core-plugin-api](https://github.com/backstage/core-plugin-api)@1.13.0 - [@&#8203;backstage/plugin-app-react](https://github.com/backstage/plugin-app-react)@0.3.0 - [@&#8203;backstage/plugin-app](https://github.com/backstage/plugin-app)@0.6.0 - [@&#8203;backstage/frontend-app-api](https://github.com/backstage/frontend-app-api)@1.0.0 - [@&#8203;backstage/errors](https://github.com/backstage/errors)@1.4.0 - [@&#8203;backstage/test-utils](https://github.com/backstage/test-utils)@1.8.0 - [@&#8203;backstage/core-app-api](https://github.com/backstage/core-app-api)@1.20.7 - [@&#8203;backstage/plugin-permission-react](https://github.com/backstage/plugin-permission-react)@0.5.7 - [@&#8203;backstage/version-bridge](https://github.com/backstage/version-bridge)@1.1.0 - [@&#8203;backstage/config](https://github.com/backstage/config)@1.3.11 - [@&#8203;backstage/filter-predicates](https://github.com/backstage/filter-predicates)@0.2.1 - [@&#8203;backstage/plugin-permission-common](https://github.com/backstage/plugin-permission-common)@0.9.13 </details> <details> <summary>backstage/backstage (@&#8203;backstage/plugin-catalog-node)</summary> ### [`v3.0.0`](https://github.com/backstage/backstage/blob/HEAD/plugins/catalog-node/CHANGELOG.md#300) [Compare Source](https://github.com/backstage/backstage/compare/40525466a0f70119579cbfc4a60b9d2aa6c8a52d...6b4aecbbe1159f48a3937dfd839e3018b85b608d) ##### Patch Changes - Updated dependencies - [@&#8203;backstage/catalog-client](https://github.com/backstage/catalog-client)@1.16.4 - [@&#8203;backstage/backend-plugin-api](https://github.com/backstage/backend-plugin-api)@1.12.0 - [@&#8203;backstage/errors](https://github.com/backstage/errors)@1.4.0 - [@&#8203;backstage/catalog-model](https://github.com/backstage/catalog-model)@1.10.3 - [@&#8203;backstage/plugin-catalog-common](https://github.com/backstage/plugin-catalog-common)@1.2.2 - [@&#8203;backstage/plugin-permission-common](https://github.com/backstage/plugin-permission-common)@0.9.13 - [@&#8203;backstage/plugin-permission-node](https://github.com/backstage/plugin-permission-node)@0.11.6 </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xODEuMCIsInVwZGF0ZWRJblZlciI6IjQ0LjE4MS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
fix(deps): update backstage monorepo to v1
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
16e67bee5b
renovate-bot force-pushed renovate/major-backstage-monorepo from 16e67bee5b
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
to d26a292580
Some checks failed
renovate/artifacts Artifact file update failure
ci/woodpecker/push/renovate-lint Pipeline was successful
ci/woodpecker/pr/pr-review Pipeline was successful
ci/woodpecker/pr/application-checks Pipeline failed
2026-11-21 23:10:28 +00:00
Compare
renovate-bot changed title from fix(deps): update backstage monorepo to v1 to fix(deps): update backstage monorepo (major) 2026-11-21 23:10:33 +00:00
Author
Member

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: bun.lock
2 |   "lockfileVersion": 2,
                         ^
error: Unknown lockfile version
    at bun.lock:2:22
UnknownLockfileVersion: failed to parse lockfile: 'bun.lock'

warn: Ignoring lockfile
Resolving dependencies
Resolved, downloaded and extracted [3]
warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "eslint-plugin-react-hooks@5.2.0"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "@codemirror/language@6.13.1"

error: Package "app" is not linked

To install a linked package:
   bun link my-pkg-name-from-package-json

Tip: the package name is from package.json, which can differ from the folder name.

error: app@link:../app failed to resolve

File name: bun.lock
2 |   "lockfileVersion": 2,
                         ^
error: Unknown lockfile version
    at bun.lock:2:22
UnknownLockfileVersion: failed to parse lockfile: 'bun.lock'

warn: Ignoring lockfile
Resolving dependencies
Resolved, downloaded and extracted [1]
warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "eslint-plugin-react-hooks@5.2.0"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react@18.3.1"

warn: incorrect peer dependency "react-dom@18.3.1"

warn: incorrect peer dependency "@codemirror/language@6.13.1"

error: Package "app" is not linked

To install a linked package:
   bun link my-pkg-name-from-package-json

Tip: the package name is from package.json, which can differ from the folder name.

error: app@link:../app failed to resolve

### ⚠️ Artifact update problem Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: bun.lock ``` 2 | "lockfileVersion": 2, ^ error: Unknown lockfile version at bun.lock:2:22 UnknownLockfileVersion: failed to parse lockfile: 'bun.lock' warn: Ignoring lockfile Resolving dependencies Resolved, downloaded and extracted [3] warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "eslint-plugin-react-hooks@5.2.0" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "@codemirror/language@6.13.1" error: Package "app" is not linked To install a linked package: bun link my-pkg-name-from-package-json Tip: the package name is from package.json, which can differ from the folder name. error: app@link:../app failed to resolve ``` ##### File name: bun.lock ``` 2 | "lockfileVersion": 2, ^ error: Unknown lockfile version at bun.lock:2:22 UnknownLockfileVersion: failed to parse lockfile: 'bun.lock' warn: Ignoring lockfile Resolving dependencies Resolved, downloaded and extracted [1] warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "eslint-plugin-react-hooks@5.2.0" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react@18.3.1" warn: incorrect peer dependency "react-dom@18.3.1" warn: incorrect peer dependency "@codemirror/language@6.13.1" error: Package "app" is not linked To install a linked package: bun link my-pkg-name-from-package-json Tip: the package name is from package.json, which can differ from the folder name. error: app@link:../app failed to resolve ```
Some checks failed
renovate/artifacts Artifact file update failure
ci/woodpecker/push/renovate-lint Pipeline was successful
ci/woodpecker/pr/pr-review Pipeline was successful
ci/woodpecker/pr/application-checks Pipeline failed
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'renovate/major-backstage-monorepo:renovate/major-backstage-monorepo'
git switch 'renovate/major-backstage-monorepo'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'main'
git merge --no-ff 'renovate/major-backstage-monorepo'
git switch 'renovate/major-backstage-monorepo'
git rebase 'main'
git switch 'main'
git merge --ff-only 'renovate/major-backstage-monorepo'
git switch 'renovate/major-backstage-monorepo'
git rebase 'main'
git switch 'main'
git merge --no-ff 'renovate/major-backstage-monorepo'
git switch 'main'
git merge --squash 'renovate/major-backstage-monorepo'
git switch 'main'
git merge --ff-only 'renovate/major-backstage-monorepo'
git switch 'main'
git merge 'renovate/major-backstage-monorepo'
git push origin 'main'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Personal/backstage!39
No description provided.