Bump @backstage/plugin-catalog-node from 1.19.0 to 2.2.3

[dependabot]

Bumps @backstage/plugin-catalog-node from 1.19.0 to 2.2.3.

Release notes

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

v1.54.0-next.2

See docs/releases/v1.54.0-next.2-changelog.md for more information.

v1.54.0-next.1

See docs/releases/v1.54.0-next.1-changelog.md for more information.

v1.54.0-next.0

See docs/releases/v1.54.0-next.0-changelog.md for more information.

v1.53.1

This patch release fixes the following issues:

• Errors in TypeScript configuration schema definitions no longer prevent apps from building or starting and are logged as warnings instead

v1.53.0

These are the release notes for the v1.53.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: Removed deprecated SSE transport from MCP actions

The deprecated Server-Sent Events (SSE) MCP transport has been removed from @backstage/plugin-mcp-actions-backend. MCP clients must use the Streamable HTTP endpoint at /api/mcp-actions/v1 or a configured named-server endpoint.

BREAKING: Configuration schemas now resolve imported types

Configuration schemas declared in TypeScript now resolve and validate imported types in @backstage/config-loader, instead of treating them as unconstrained values. Invalid imports now cause schema loading to fail. This may surface previously undetected schema issues in plugins that import types in their config.d.ts files.

BREAKING: Stricter OAuth redirect URI and CIMD allowlist matching

The OAuth redirect URI and client ID metadata document allowlists in @backstage/plugin-auth-backend now match patterns against each URL component separately instead of against the full URL string. Wildcards no longer match across the host and path boundary, patterns must include an explicit protocol and are otherwise rejected as invalid configuration instead of being silently ignored, and redirect URIs that contain embedded credentials are always rejected.

A wildcard port also no longer implicitly matches every path: a pattern such as http://localhost:* now only matches the root path. Use http://localhost:*/* to allow any port and any path. The built-in loopback defaults have been updated accordingly, so this only affects explicitly configured patterns.

BREAKING ALPHA: Catalog entity page migrated to BUI

The new frontend system Catalog entity page has been migrated to Backstage UI components with several breaking alpha changes in @backstage/plugin-catalog and @backstage/plugin-catalog-react:

• The entity page now uses a BUI page header with entity tags, title, metadata, favorite and context-menu actions, and Catalog-composed navigation. Existing alpha opaque entity header customizations continue to render through a temporary per-entity legacy fallback. Migrate those customizations to the new BUI-ready entity header layout extension point.
• The entity context menu has been migrated to BUI with Remix icons. The EntityContextMenuItemBlueprint now outputs menu item data instead of a rendered MUI element. The icon type is now IconElement — we recommend using Remix icons.
• A new alpha entity header layout extension point has been added, providing Catalog-composed tabs and the active tab ID for custom entity headers. The existing opaque entity header extension point is deprecated.

New translation keys have been added: entityLabels.systemLabel, entityLabels.domainLabel, entityLabels.partOfLabel, and entityContextMenu.moreButtonAriaLabel (default changed from more to More actions). Apps that provide Catalog translations should add entries for these new messages.

BREAKING: Removed legacy proxy agent bootstrap

The deprecated bootstrapEnvProxyAgents export has been removed from @backstage/cli-common, along with the global-agent and undici dependencies. The versions:bump command in @backstage/cli-module-migrate and newly created apps from @backstage/create-app no longer bootstrap legacy proxy agents either. Use Node.js built-in proxy support by setting NODE_USE_ENV_PROXY=1 alongside your HTTP_PROXY/HTTPS_PROXY/NO_PROXY environment variables instead. See the corporate proxy guide for details.

Contributed by @​jonkoops in #33444

... (truncated)

Changelog

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

2.2.3

Patch Changes

• Updated dependencies
  • @​backstage/backend-plugin-api@​1.9.3
  • @​backstage/catalog-client@​1.16.1
  • @​backstage/plugin-permission-node@​0.11.2

2.2.3-next.0

Patch Changes

• Updated dependencies
  • @​backstage/backend-test-utils@​1.11.5-next.0
  • @​backstage/plugin-permission-node@​0.11.2-next.0
  • @​backstage/backend-plugin-api@​1.9.3-next.0
  • @​backstage/catalog-client@​1.16.1-next.0

2.2.2

Patch Changes

• Updated dependencies
  • @​backstage/catalog-client@​1.16.0
  • @​backstage/backend-plugin-api@​1.9.2
  • @​backstage/plugin-permission-node@​0.11.1

2.2.2-next.0

Patch Changes

• Updated dependencies
  • @​backstage/catalog-client@​1.16.0-next.0
  • @​backstage/backend-test-utils@​1.11.4-next.0
  • @​backstage/plugin-permission-node@​0.11.1-next.0
  • @​backstage/backend-plugin-api@​1.9.2-next.0

2.2.1

Patch Changes

• ab1cdbb: Removed a handful of internal imports that referenced the package by its own name. Value imports were switched to relative paths, and type-only imports to import type. These self-referential imports could trigger circular initialization errors in bundled ESM and when the package was loaded via jest.requireActual — most visibly Cannot access '_AppRootElementBlueprintesm' before initialization from @backstage/frontend-plugin-api. There are no user-facing API changes.
• Updated dependencies
  • @​backstage/catalog-model@​1.9.0
  • @​backstage/errors@​1.3.1
  • @​backstage/backend-test-utils@​1.11.3
  • @​backstage/backend-plugin-api@​1.9.1
  • @​backstage/plugin-permission-node@​0.11.0
  • @​backstage/plugin-permission-common@​0.9.9

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