Bump @backstage/plugin-catalog-react from 1.21.6 to 2.0.0 in /app

[dependabot]

Bumps @backstage/plugin-catalog-react from 1.21.6 to 2.0.0.

Release notes

Sourced from @​backstage/plugin-catalog-react's releases.

v1.48.1

This patch release fixes the following issues:

• Add missing sharing extensions sidebar item in frontend system architecture docs
• Fix type compatibility for older plugins in FrontendFeature type

v1.48.0

These are the release notes for the v1.48.0 release of Backstage.

A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done.

Highlights

BREAKING ALPHA: Catalog extension points graduated

If you are providing custom processors and entity providers into the catalog, you will now note that several (but not quite all!) of those extension points have graduated out of alpha and into the regular stable exports.

Thus, if you are importing for example catalogProcessingExtensionPoint from @backstage/plugin-catalog-node/alpha, you now want to remove that /alpha suffix.

BREAKING: API restrictions in New Frontend System

In the 1.47 release a new behavior was introduced to the New Frontend System that limits the ability for plugins and modules to provide APIs to plugins other than themselves. For example, the scaffolder plugin could no longer install a custom CatalogApi implementation. This also applies to modules, where you now need to use a module explicitly targeting the 'app' plugin to for example override the ErrorApi.

In 1.47 this new behavior simply triggered a warning, but in this release the API overrides are instead rejected with an error.

Experimental Client ID Metadata Documents

With the latest MCP specification published in November, it outlined a new authorization method that’s going to take over from Dynamic Client Registration called Client ID Metadata Documents.

This can be enabled in the auth-backend plugin by using the auth.experimentalClientIdMetadataDocuments.enabled flag in config.

Be sure to head over to the changelog for additional configuration and security considerations.

Experimental Refresh Token Support

Clients can now request the offline_access scope to receive refresh tokens when auth.experimentalRefreshToken.enabled is set, allowing new access tokens without re-authentication. This can be highly useful when using experimentalDynamicClientRegistration so that the tokens don’t expire every 1h by default, which then triggers another auth session approval request.

This also means that auth.experimentalDynamicClientRegistration.tokenExpiration has been removed in favor of using this method as a BREAKING EXPERIMENTAL change.

New Frontend System: Testing utilities

The testing utilities for the new frontend system have gotten an overhaul in this release, with all new features documented in the plugin testing section. Some highlights include that mountedRoutes and apis options are available for all harnesses where applicable. The selection of mockApis has been increased to support more of the core APIs and have both Jest and minimal implementation mocks. The mockApis now also produces values that can be passed directly to the various testing apis options, without the need to wrap [ref, impl] tuples.

Utilities for creating frontend and backend mocks

Both @backstage/frontend-test-utils and @backstage/backend-test-utils now export utilities for creating service and API mocks, createServiceMock and createApiMock. These utilities create the same kind of mock utilities as the ones provided by mockServices and mockApis, and are encouraged to be exported via the /testUtils sub-path export from packages, similar to how this pattern is used in @backstage/plugin-catalog-react.

New Frontend System: Plugin titles & icons

Plugins now have optional titles and icons in the new frontend system. This helps implement app-wide features and navigation patterns that enumerate plugins or in other ways traverse the extension tree in the app.

... (truncated)

Changelog

Sourced from @​backstage/plugin-catalog-react's changelog.

2.0.0

Minor Changes

• 0e9578d: Migrated UnregisterEntityDialog from Material UI to Backstage UI components.

• 491a06c: Add the ability to show icons for the tabs on the entity page (new frontend)

• b4e8249: Implemented support for the new queryLocations and streamLocations that allow paginated/streamed and filtered location queries

• 7feb83b: BREAKING ALPHA: All of the predicate types and functions have been moved to the @backstage/filter-predicates package.

  When moving into the more general package, they were renamed as follows:

  • EntityPredicate -> FilterPredicate
  • EntityPredicateExpression -> FilterPredicateExpression
  • EntityPredicatePrimitive -> FilterPredicatePrimitive
  • entityPredicateToFilterFunction -> filterPredicateToFilterFunction
  • EntityPredicateValue -> FilterPredicateValue

• e8258d0: BREAKING: Removed the 'summary' entity card type from EntityCardType. Users should migrate to using 'content' or 'info' card types instead.

  TypeScript will now show errors if you try to use type: 'summary' when creating entity cards.

• ac9bead: Added createTestEntityPage test utility for testing entity cards and content extensions in the new frontend system. This utility creates a test page extension that provides EntityProvider context and accepts entity extensions through input redirects:

  import { renderTestApp } from '@backstage/frontend-test-utils';
  import { createTestEntityPage } from '@backstage/plugin-catalog-react/testUtils';
  renderTestApp({
  extensions: [createTestEntityPage({ entity: myEntity }), myEntityCard],
  });

Patch Changes

• f523983: Fixes a bug where the EntityListProvider would not correctly hydrate query parameters if more than 20 were provided for the same key.
• 09a6aad: The catalogApiMock test utility now returns a MockWithApiFactory, allowing it to be passed directly to test utilities like renderTestApp and TestApiProvider without needing the [catalogApiRef, catalogApiMock()] tuple.
• 88dbd5e: fixed bug in UserListPicker by getting the kindParamater from the filters rather than from the queryParameters
• a7e0d50: Updated react-router-dom peer dependency to ^6.30.2 and explicitly disabled v7 future flags to suppress deprecation warnings.
• 69d880e: Bump to latest zod to ensure it has the latest features
• Updated dependencies
  • @​backstage/ui@​0.12.0
  • @​backstage/frontend-test-utils@​0.5.0
  • @​backstage/core-components@​0.18.7
  • @​backstage/core-compat-api@​0.5.8
  • @​backstage/frontend-plugin-api@​0.14.0
  • @​backstage/catalog-client@​1.13.0
  • @​backstage/core-plugin-api@​1.12.3
  • @​backstage/integration-react@​1.2.15
  • @​backstage/plugin-permission-react@​0.4.40
  • @​backstage/version-bridge@​1.0.12

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

I'm not approving this PR because it includes a major update of a dependency used in production