Bump @backstage/plugin-catalog-backend from 1.26.0 to 3.9.1 in /backstage

[dependabot]

Bumps @backstage/plugin-catalog-backend from 1.26.0 to 3.9.1.

Release notes

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

v1.56.0-next.3

See docs/releases/v1.56.0-next.3-changelog.md for more information.

v1.56.0-next.2

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

v1.56.0-next.1

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

v1.56.0-next.0

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

v1.55.3

This patch release fixes the following issues:

• Fixed TechDocs generation for documented MkDocs Markdown extension configurations.

v1.55.2

This patch release contains the following commits:

• fix: normalize TechDocs Markdown extension configuration

v1.55.1

This patch release fixes the following issues:

• Fix the Yarn patch verifier failing to load unless consumers separately install the Yarn CLI package. (#35749)
• Fix TechDocs addons not rendering on the new frontend system. (#35770)

v1.55.0

These are the release notes for the v1.55.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 catalog APIs and configuration

This release removes several deprecated features from @backstage/plugin-catalog-backend.

The catalog.enableRelationsCompatibility config option and its associated compatibility layer have been removed. 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.

The deprecated CodeOwnersProcessor and AnnotateScmSlugEntityProcessor have been removed. Replace their custom registrations with the corresponding community modules: @backstage-community/plugin-catalog-backend-module-codeowners and @backstage-community/plugin-catalog-backend-module-annotate-scm-slug.

Remove the deprecated catalog.stitchingStrategy.mode key from your configuration. Stitching continues to run asynchronously, with pollingInterval and stitchTimeout still supported.

BREAKING: Elasticsearch 8 upgrade

The @backstage/plugin-search-backend-module-elasticsearch package has upgraded its Elasticsearch client to version 8, requiring at least Elasticsearch 8.19 — the only 8.x release line still under support, following the end of life of Elasticsearch 7.x and earlier 8.x lines. Elasticsearch 7.x clusters are no longer supported.

If you use the elastic provider or connect to a plain Elasticsearch node, make sure your cluster is running Elasticsearch 8.19 or later before upgrading. The aws and opensearch providers keep using the OpenSearch client and are unaffected. Existing TLS settings continue to work without any configuration changes.

... (truncated)

Changelog

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

@​backstage/plugin-catalog-backend

4.0.1-next.3

Patch Changes

• aa6e7c6: Reduce repeated work for entities that fail stitching by gradually increasing retry delays with jitter. Failed entities remain eligible for recovery, and new stitching requests reset their failure count.
• d7cc6e5: Reject non-positive stitching polling intervals and lease durations at startup to prevent continuous polling and immediate lease expiry. Configuration errors identify the setting that needs correction.
• 7c376ff: Improved the performance and planner stability of orphan entity cleanup on large PostgreSQL catalogs. Orphan deletion and updates to related entities are now atomic, so a failed cleanup does not leave related entities waiting indefinitely for updated relations. Cleanup also preserves entities when a new reference is committed while it waits to delete them.
• Updated dependencies
  • @​backstage/catalog-client@​1.16.3-next.1
  • @​backstage/backend-plugin-api@​1.11.0-next.2

4.0.1-next.2

Patch Changes

• 589dcef: Fixed an issue where successfully processed entities could remain unavailable if stitch scheduling was interrupted.

• a69d971: Improved the reliability of deferred stitching. Pending stitching work is no longer lost when entities are deleted and re-added, and updated instances prevent timed-out stitching attempts from overwriting or removing work taken over by another updated instance. During rolling upgrades from older versions, instances may still perform redundant stitching. On MySQL, protection against overlapping writes remains best-effort.

• 476f042: Fixed entities disappearing from filtered and sorted catalog queries after a database error during stitching. The final entity and its search index rows are now written together, so a failure part way through is rolled back and retried in full. Previously the entity could be left with a search index that no longer matched it, and because the entity itself looked up to date, every later stitch attempt skipped it. Such an entity stayed readable by direct lookup while missing from list queries that filter or sort, until it was next edited.

  PostgreSQL and MySQL deadlocks trigger prompt, bounded retries of the entire write transaction, skipping the write if newer stitching work has superseded it. If retries are exhausted, queued work remains available for recovery after the stitching timeout.

• Updated dependencies

  • @​backstage/integration@​2.1.3-next.1
  • @​backstage/backend-openapi-utils@​0.7.3-next.2

4.0.1-next.1

Patch Changes

• Updated dependencies
  • @​backstage/backend-plugin-api@​1.11.0-next.1
  • @​backstage/backend-openapi-utils@​0.7.3-next.1
  • @​backstage/plugin-catalog-node@​2.2.6-next.1
  • @​backstage/plugin-events-node@​0.4.27-next.1
  • @​backstage/plugin-permission-node@​0.11.5-next.1

4.0.1-next.0

Patch Changes

• a08e746: Improved large entity provider mutations by yielding to the event loop while preparing database changes.

• 727d53f: Improve responsiveness to other requests while reading large sets of entities with field selection, without reducing page sizes.

  Like full-entity responses, projected list responses may now be streamed without a Content-Length or automatically generated ETag header.

• e783f4b: Fixed catalog processing error messages to report stable processor names in minified builds.

• Updated dependencies

  • @​backstage/integration@​2.1.3-next.0

... (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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.