paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 46 Packages Projects Releases Wiki Activity
Files
master
backstage/docs/releases/v1.42.0-next.2-changelog.md
T
github-actions[bot] 1e8a013c67 Version Packages (next)
2025-08-05 13:45:29 +00:00

27 KiB
Raw Permalink Blame History

Release v1.42.0-next.2

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

@backstage/cli@0.34.0-next.1

Minor Changes

  • 38b4243: Added plugin and module templates for the new frontend system. These templates are not included by default, but can be included by adding @backstage/cli/templates/new-frontend-plugin and @backstage/cli/templates/new-frontend-plugin-module as custom templates.

Patch Changes

  • Updated dependencies
    • @backstage/catalog-model@1.7.5
    • @backstage/cli-common@0.1.15
    • @backstage/cli-node@0.2.13
    • @backstage/config@1.3.3
    • @backstage/config-loader@1.10.2
    • @backstage/errors@1.2.7
    • @backstage/eslint-plugin@0.1.11
    • @backstage/integration@1.17.1
    • @backstage/release-manifests@0.0.13
    • @backstage/types@1.2.1

@backstage/core-compat-api@0.5.0-next.2

Minor Changes

  • e4ddf22: BREAKING: The defaultPath override of convertLegacyPageExtension has been renamed to path, in order to align with the same update that was made to the PageBlueprint.

Patch Changes

@backstage/frontend-app-api@0.12.0-next.2

Minor Changes

  • df7bd3b: BREAKING: Removed the deprecated FrontendFeature type, import it from @backstage/frontend-plugin-api instead.

Patch Changes

  • d9e00e3: Add support for a new aliasFor option for createRouteRef. This allows for the creation of a new route ref that acts as an alias for an existing route ref that is installed in the app. This is particularly useful when creating modules that override existing plugin pages, without referring to the existing plugin. For example:

    export default createFrontendModule({
  pluginId: 'catalog',
  extensions: [
    PageBlueprint.make({
      params: {
        defaultPath: '/catalog',
        routeRef: createRouteRef({ aliasFor: 'catalog.catalogIndex' }),
        loader: () =>
          import('./CustomCatalogIndexPage').then(m => (
            <m.CustomCatalogIndexPage />
          )),
      },
    }),
  ],
});

  • 3d2499f: Moved createSpecializedApp options to a new CreateSpecializedAppOptions type.

  • Updated dependencies

@backstage/frontend-defaults@0.3.0-next.2

Minor Changes

  • 76832a9: BREAKING: Removed the deprecated CreateAppFeatureLoader and support for it in other APIs. Switch existing usage to use the newer createFrontendFeatureLoader from @backstage/frontend-plugin-api instead.

Patch Changes

  • 22de964: Deprecated createPublicSignInApp, which has been replaced by the new appModulePublicSignIn from @backstage/plugin-app/alpha instead.
  • e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.
  • Updated dependencies

@backstage/frontend-plugin-api@0.11.0-next.1

Minor Changes

  • c5f88b5: BREAKING: Remove deprecated source property from the AppNodeSpec type, use AppNodeSpec.plugin instead.

  • e4ddf22: BREAKING: The defaultPath param of PageBlueprint has been renamed to path. This change does not affect the compatibility of extensions created with older versions of this blueprint.

  • 37f2989: BREAKING: Removed the routable property from ExtensionBoundary. This property was never needed in practice and is instead inferred from whether or not the extension outputs a route reference. It can be safely removed.

  • 3243fa6: BREAKING: Removed the ability to define a default extension name in blueprints. This option had no practical purpose as blueprints already use the kind to identity the source of the extension.

  • a082429: BREAKING: The separate RouteResolutionApiResolveOptions type has been removed.

  • 5d31d66: BREAKING: In an attempt to align some of the API's around providing components to Blueprints, we've renamed the parameters for both the RouterBlueprint and AppRootWrapperBlueprint from Component to component.

    // old
RouterBlueprint.make({
  params: {
    Component: ({ children }) => <div>{children}</div>,
  },
});

// new
RouterBlueprint.make({
  params: {
    component: ({ children }) => <div>{children}</div>,
  },
});

    // old
AppRootWrapperBlueprint.make({
  params: {
    Component: ({ children }) => <div>{children}</div>,
  },
});

// new
AppRootWrapperBlueprint.make({
  params: {
    component: ({ children }) => <div>{children}</div>,
  },
});

    As part of this change, the type for component has also changed from ComponentType<PropsWithChildren<{}>> to (props: { children: ReactNode }) => JSX.Element | null which is not breaking, just a little more reflective of the actual expected component.

  • 45ead4a: BREAKING: The AnyRoutes and AnyExternalRoutes types have been removed and their usage has been inlined instead.

    Existing usage can be replaced according to their previous definitions:

    type AnyRoutes = { [name in string]: RouteRef | SubRouteRef };
type AnyExternalRoutes = { [name in string]: ExternalRouteRef };

  • 121899a: BREAKING: The element param for AppRootElementBlueprint no longer accepts a component. If you are currently passing a component such as element: () => <MyComponent /> or element: MyComponent, simply switch to element: <MyComponent />.

  • a321f3b: BREAKING: The CommonAnalyticsContext has been removed, and inlined into AnalyticsContextValue instead.

Patch Changes

  • d9e00e3: Add support for a new aliasFor option for createRouteRef. This allows for the creation of a new route ref that acts as an alias for an existing route ref that is installed in the app. This is particularly useful when creating modules that override existing plugin pages, without referring to the existing plugin. For example:

    export default createFrontendModule({
  pluginId: 'catalog',
  extensions: [
    PageBlueprint.make({
      params: {
        defaultPath: '/catalog',
        routeRef: createRouteRef({ aliasFor: 'catalog.catalogIndex' }),
        loader: () =>
          import('./CustomCatalogIndexPage').then(m => (
            <m.CustomCatalogIndexPage />
          )),
      },
    }),
  ],
});

  • 93b5e38: Plugins should now use the new AnalyticsImplementationBlueprint to define and provide concrete analytics implementations. For example:

    import { AnalyticsImplementationBlueprint } from '@backstage/frontend-plugin-api';

const AcmeAnalytics = AnalyticsImplementationBlueprint.make({
  name: 'acme-analytics',
  params: define =>
    define({
      deps: { config: configApiRef },
      factory: ({ config }) => AcmeAnalyticsImpl.fromConfig(config),
    }),
});

  • 948de17: Tweaked the return types from createExtension and createExtensionBlueprint to avoid the forwarding of ConfigurableExtensionDataRef into exported types.

  • 147482b: Updated the recommended naming of the blueprint param callback from define to defineParams, making the syntax defineParams => defineParams(...).

  • 3c3c882: Added added defaults for all type parameters of ExtensionDataRef and deprecated AnyExtensionDataRef, as it is now redundant.

  • Updated dependencies

@backstage/plugin-app@0.2.0-next.1

Minor Changes

  • 121899a: BREAKING: The app-root-element extension now only accepts JSX.Element in its element param, meaning overrides need to be updated.

Patch Changes

  • a08f95f: Added a new module for implementing public sign-in apps, exported as appModulePublicSignIn via the /alpha sub-path export. This replaces the createPublicSignInApp export from @backstage/frontend-defaults, which is now deprecated.
  • 5d31d66: Updated the usage of the RouterBlueprint and AppRootWrapperBlueprint to use the lowercase component parameter
  • 93b5e38: The default implementation of the Analytics API now collects and instantiates analytics implementations exposed via AnalyticsImplementationBlueprint extensions. If no such extensions are discovered, the API continues to do nothing with analytics events fired within Backstage. If multiple such extensions are discovered, every discovered implementation automatically receives analytics events.
  • Updated dependencies

@backstage/plugin-catalog-react@1.20.0-next.2

Minor Changes

  • e4ddf22: BREAKING ALPHA: The defaultPath, defaultTitle, and defaultGroup params of PageBlueprint has been renamed to path, title, and group. The convertLegacyEntityContentExtension utility has also received the same change. This change does not affect the compatibility of extensions created with older versions of this blueprint.

Patch Changes

@backstage/core-components@0.17.5-next.1

Patch Changes

  • 5563605: Added FavoriteToggleProps.
  • Updated dependencies

@backstage/create-app@0.7.2-next.2

Patch Changes

  • Bumped create-app version.
  • Updated dependencies
    • @backstage/cli-common@0.1.15

@backstage/frontend-test-utils@0.3.5-next.2

Patch Changes

  • df7bd3b: Updated import of the FrontendFeature type.
  • 5d31d66: Updated the usage of the RouterBlueprint and AppRootWrapperBlueprint to use the lowercase component parameter
  • Updated dependencies

@backstage/ui@0.7.0-next.2

Patch Changes

  • d4e603e: Updated Menu component in Backstage UI to use useId() from React Aria instead of React to support React 17.

@backstage/plugin-api-docs@0.12.10-next.2

Patch Changes

@backstage/plugin-app-visualizer@0.1.22-next.1

Patch Changes

@backstage/plugin-catalog@1.31.2-next.2

Patch Changes

@backstage/plugin-catalog-graph@0.4.22-next.2

Patch Changes

@backstage/plugin-catalog-import@0.13.4-next.2

Patch Changes

@backstage/plugin-catalog-unprocessed-entities@0.2.20-next.2

Patch Changes

@backstage/plugin-devtools@0.1.30-next.2

Patch Changes

@backstage/plugin-home@0.8.11-next.2

Patch Changes

@backstage/plugin-kubernetes@0.12.10-next.2

Patch Changes

@backstage/plugin-notifications@0.5.8-next.2

Patch Changes

@backstage/plugin-org@0.6.42-next.2

Patch Changes

@backstage/plugin-scaffolder@1.34.0-next.2

Patch Changes

@backstage/plugin-search@1.4.29-next.2

Patch Changes

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

Patch Changes

  • d9bda0f: Allow filter to be an array in config schema
  • Updated dependencies
    • @backstage/backend-plugin-api@1.4.2-next.0
    • @backstage/catalog-client@1.11.0-next.0
    • @backstage/catalog-model@1.7.5
    • @backstage/config@1.3.3
    • @backstage/errors@1.2.7
    • @backstage/plugin-catalog-common@1.1.5
    • @backstage/plugin-catalog-node@1.18.0-next.0
    • @backstage/plugin-permission-common@0.9.1
    • @backstage/plugin-search-backend-node@1.3.14-next.0
    • @backstage/plugin-search-common@1.2.19

@backstage/plugin-search-react@1.9.3-next.1

Patch Changes

@backstage/plugin-signals@0.0.22-next.2

Patch Changes

@backstage/plugin-techdocs@1.14.0-next.2

Patch Changes

@backstage/plugin-techdocs-backend@2.0.5-next.1

Patch Changes

@backstage/plugin-user-settings@0.8.25-next.2

Patch Changes

example-app@0.2.112-next.2

Patch Changes

example-app-next@0.0.26-next.2

Patch Changes

techdocs-cli-embedded-app@0.2.111-next.2

Patch Changes

Reference in New Issue View Git Blame Copy Permalink