Skip to content

Bump @backstage/plugin-catalog-node from 1.19.0 to 2.2.0#20

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/backstage/plugin-catalog-node-2.2.0
Open

Bump @backstage/plugin-catalog-node from 1.19.0 to 2.2.0#20
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/backstage/plugin-catalog-node-2.2.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 22, 2026

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

Release notes

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

v1.51.0-next.2

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

v1.51.0-next.1

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

v1.51.0-next.0

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

v1.50.4

This release contains security fixes for @backstage/plugin-catalog-backend-module-unprocessed , @backstage/plugin-catalog-unprocessed-entities-common version and @backstage/plugin-catalog-unprocessed-entities.

v1.50.3

This patch release fixes the following issues:

  • Fix home page widgets not being draggable or resizable after the first save
  • Fix facets endpoint performance regression when filters or permissions are applied
  • Preserve external hrefs in BUI link components under non-root base path

v1.50.2

This patch release fixes the following issues:

  • Make TechDocs sidebar positioning configurable via CSS custom properties
  • Bump zod dependency to v4 for packages using configSchema and clarify that zod/v4 subpath from v3 is not supported
  • Clamp React Aria dependency ranges to patch-only updates to prevent unintended minor version upgrades
  • Fix active tab indicator disappearing on uncontrolled Tabs in @​backstage/ui

v1.50.1

This patch release fixes the following issues:

  • Replaced old config schema values from existing extensions and blueprints.
  • Fix config path resolution for embedded-postgres detection in repo start
  • Update React Aria to v1.17.0 and migrate to monopackage imports

v1.50.0

These are the release notes for the v1.50.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: Identity token ownership claim removed by default

The auth.omitIdentityTokenOwnershipClaim setting now defaults to true. Backstage user tokens issued by the auth backend will no longer contain the ent claim with the user's ownership entity refs. This means tokens in large organizations no longer risk hitting HTTP header size limits.

To get ownership info for the current user, code should use the userInfo core service. The setting can still be set back to false if needed, but it will be removed entirely in a future release.

BREAKING: Standard Schema for new frontend system extension config

The new frontend system now uses Standard Schema for extension configuration. A new configSchema option has been added to createExtension, createExtensionBlueprint, as well as the override and makeWithOverrides methods on extension definitions and blueprints. This option accepts direct schema values from any Standard Schema compatible library with JSON Schema support, replacing the old config.schema callback format which is now deprecated.

... (truncated)

Changelog

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

2.2.0

Minor Changes

  • e5fcfcb: Added provideStaticCatalogModel that helps provide a static catalog model at startup.

  • 056e18e: BREAKING ALPHA: Removed the deprecated CatalogPermissionRuleInput, CatalogPermissionExtensionPoint, and catalogPermissionExtensionPoint exports. Use coreServices.permissionsRegistry directly to register catalog entity permission rules and permissions.

  • c384fff: BREAKING PRODUCERS: Added updateLocation method to CatalogService for updating the type and target of an existing location. Any code that implements CatalogService must now provide this method.

  • 7a03196: BREAKING ALPHA: Removed the following deprecated exports from @backstage/plugin-catalog-node/alpha:

    • catalogServiceRef — use catalogServiceRef from @backstage/plugin-catalog-node instead
    • CatalogLocationsExtensionPoint / catalogLocationsExtensionPoint — use the non-alpha equivalents from @backstage/plugin-catalog-node instead
    • CatalogProcessingExtensionPoint / catalogProcessingExtensionPoint — use the non-alpha equivalents from @backstage/plugin-catalog-node instead
    • CatalogAnalysisExtensionPoint / catalogAnalysisExtensionPoint — use the non-alpha equivalents from @backstage/plugin-catalog-node instead

Patch Changes

  • Updated dependencies
    • @​backstage/backend-plugin-api@​1.9.0
    • @​backstage/backend-test-utils@​1.11.2
    • @​backstage/errors@​1.3.0
    • @​backstage/catalog-model@​1.8.0
    • @​backstage/catalog-client@​1.15.0
    • @​backstage/plugin-permission-node@​0.10.12
    • @​backstage/plugin-catalog-common@​1.1.9
    • @​backstage/plugin-permission-common@​0.9.8

2.2.0-next.2

Minor Changes

  • 056e18e: BREAKING ALPHA: Removed the deprecated CatalogPermissionRuleInput, CatalogPermissionExtensionPoint, and catalogPermissionExtensionPoint exports. Use coreServices.permissionsRegistry directly to register catalog entity permission rules and permissions.

  • 7a03196: BREAKING ALPHA: Removed the following deprecated exports from @backstage/plugin-catalog-node/alpha:

    • catalogServiceRef — use catalogServiceRef from @backstage/plugin-catalog-node instead
    • CatalogLocationsExtensionPoint / catalogLocationsExtensionPoint — use the non-alpha equivalents from @backstage/plugin-catalog-node instead
    • CatalogProcessingExtensionPoint / catalogProcessingExtensionPoint — use the non-alpha equivalents from @backstage/plugin-catalog-node instead
    • CatalogAnalysisExtensionPoint / catalogAnalysisExtensionPoint — use the non-alpha equivalents from @backstage/plugin-catalog-node instead

Patch Changes

  • Updated dependencies
    • @​backstage/errors@​1.3.0-next.0
    • @​backstage/backend-plugin-api@​1.9.0-next.2
    • @​backstage/backend-test-utils@​1.11.2-next.2
    • @​backstage/catalog-client@​1.14.1-next.0
    • @​backstage/catalog-model@​1.7.8-next.0
    • @​backstage/plugin-permission-common@​0.9.8-next.0
    • @​backstage/plugin-permission-node@​0.10.12-next.2
    • @​backstage/plugin-catalog-common@​1.1.9-next.0

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 22, 2026
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/backstage/plugin-catalog-node-2.2.0 branch from cbaeb60 to 12990a7 Compare April 29, 2026 09:26
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 1, 2026

Dependabot could not find a dependency.. Because of this, Dependabot cannot update this pull request.

Bumps [@backstage/plugin-catalog-node](https://github.com/backstage/backstage/tree/HEAD/plugins/catalog-node) from 1.19.0 to 2.2.0.
- [Release notes](https://github.com/backstage/backstage/releases)
- [Changelog](https://github.com/backstage/backstage/blob/master/plugins/catalog-node/CHANGELOG.md)
- [Commits](https://github.com/backstage/backstage/commits/HEAD/plugins/catalog-node)

---
updated-dependencies:
- dependency-name: "@backstage/plugin-catalog-node"
  dependency-version: 2.2.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/backstage/plugin-catalog-node-2.2.0 branch from 12990a7 to 2d413f8 Compare May 6, 2026 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants