fix(deps): update dependency @backstage/plugin-catalog-backend to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@backstage/plugin-catalog-backend (source)	^3.8.1 → ^4.0.0

---

Release Notes

backstage/backstage (@​backstage/plugin-catalog-backend)

v4.0.0

Compare Source

Major Changes

• b0d8a53: BREAKING: Removed the deprecated CodeOwnersProcessor and AnnotateScmSlugEntityProcessor exports. To retain their behavior, install and register the corresponding community backend module:

  • CodeOwnersProcessor: @backstage-community/plugin-catalog-backend-module-codeowners
  • AnnotateScmSlugEntityProcessor: @backstage-community/plugin-catalog-backend-module-annotate-scm-slug

  Add the module to your backend with backend.add(import('<module-package>')) and remove the custom registration of the old processor. For explicit processor configuration, follow the replacement module's documentation.

• b0d8a53: BREAKING: Removed the deprecated catalog.stitchingStrategy.mode configuration setting and its startup warnings. Remove this key from your configuration, whether it is set to immediate or deferred. Stitching continues to run asynchronously via the worker queue. The catalog.stitchingStrategy.pollingInterval and catalog.stitchingStrategy.stitchTimeout settings remain supported and should be kept if you use them.

• d2cf99f: BREAKING: Removed the deprecated catalog.enableRelationsCompatibility config option and its associated compatibility layer. Entity relations are now always returned in the standard format with only targetRef. If you were relying on the target field in relations, update your code to use targetRef instead.

Patch Changes

• 736d84e: Use locale-insensitive Unicode casing for consistent string handling across environments.
• f5119cc: Improved PostgreSQL catalog query planning by correcting entity cardinality statistics for the search table.
• 72c16f5: Use stable PostgreSQL array parameters for $in filter predicates.
• 78656f8: Fixed catalog model relations to inherit the source entity namespace when no default namespace is configured, as documented. Explicit namespaces in entity references and explicitly configured default namespaces continue to take precedence.
• 7761a50: Improved path validation for catalog entity placeholders.
• 49b41f6: Fixed a bug where catalog entities could fail to process when catalog model sources are enabled and the catalog mixes backstage.io/v1alpha1 and backstage.io/v1beta1 for the same kind.
• 4b922b3: The catalog:query-catalog-entities action now accepts limit and offset when they are passed as strings, coercing them to numbers before validation. Previously the action failed with a validation error when a client sent these pagination arguments as strings, which is common for MCP/LLM clients.
• fda0ef1: Correct catalog property permission matching.
• ff327e0: Apply catalog location analysis permissions consistently when using a custom location analyzer.
• 05e2005: Fixed PostgreSQL catalog migrations sometimes failing during search index deduplication when using a database connection pool.
• 7629e5e: Use stable PostgreSQL array parameters for batched refresh state lookups and updates.
• c26a19b: Improved catalog database performance stability for large PostgreSQL installations with frequent entity updates.
• e363ae2: Allowed location type restrictions are now applied consistently during catalog processing.
• Updated dependencies
  • @​backstage/integration@2.1.2
  • @​backstage/plugin-catalog-common@1.2.0
  • @​backstage/backend-openapi-utils@0.7.2
  • @​backstage/catalog-client@1.16.2
  • @​backstage/catalog-model@1.10.1
  • @​backstage/filter-predicates@0.1.5
  • @​backstage/config@1.3.9
  • @​backstage/plugin-permission-node@0.11.4
  • @​backstage/backend-plugin-api@1.10.1
  • @​backstage/plugin-catalog-node@2.2.5
  • @​backstage/plugin-events-node@0.4.26
  • @​backstage/plugin-permission-common@0.9.11

v3.9.1

Compare Source

v3.9.0

Compare Source

Minor Changes

• c7c0ec3: Added a refresh-catalog-entity action so agents and MCP clients can re-queue a single entity for processing after creating or updating it — useful for reading back fresh data immediately after a scaffolder run without waiting for the next scheduled processing loop.

Patch Changes

• aa318d0: Migrated internal query filter handling from EntityFilter to FilterPredicate, simplifying the filter parsing and query application pipeline.
• 10f0713: Replaced the delete-all and reinsert pattern for the relations table with a diff-based sync that only touches rows that actually changed. In steady state (the common case), zero writes occur, eliminating write churn, dead tuples, and WAL traffic from the processing path. Stitching is now also skipped for relation neighbors that did not change.
• ee40136: Fixed a missing promise return in a database migration rollback function.
• eb6dff2: Fixed an issue where PostgreSQL deadlock errors during entity provider mutations were silently swallowed, causing entities to be dropped until the next full refresh. Transactions are now automatically retried on deadlock with exponential back-off.
• dd562f0: Fixed a potential MySQL deadlock during concurrent entity processing by retrying the updateProcessedEntity transaction on deadlock errors.
• b031a48: Fixed an issue where SCM location.moved events would generate new locations in the database for files that were not actively tracked.
• b7650ad: Simplified internal router setup by removing unnecessary conditional guards around route registrations.
• Updated dependencies
  • @​backstage/catalog-model@1.10.0
  • @​backstage/backend-plugin-api@1.10.0
  • @​backstage/integration@2.1.0
  • @​backstage/plugin-permission-common@0.9.10
  • @​backstage/plugin-permission-node@0.11.3
  • @​backstage/backend-openapi-utils@0.7.1
  • @​backstage/plugin-catalog-node@2.2.4
  • @​backstage/plugin-events-node@0.4.25

v3.8.2

Compare Source

Patch Changes

• ee40136: Fixed a missing promise return in a database migration rollback function.
• b7650ad: Simplified internal router setup by removing unnecessary conditional guards around route registrations.
• Updated dependencies
  • @​backstage/integration@2.1.0-next.0

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact 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: yarn.lock

➤ YN0000: · Yarn 4.18.0
➤ YN0000: ┌ Resolution step
➤ YN0016: │ @backstage/plugin-catalog-backend@npm:^4.0.0: All versions satisfying "^4.0.0" are quarantined
➤ YN0000: └ Completed in 0s 936ms
➤ YN0000: · Failed with errors in 0s 963ms