Bump @backstage/plugin-search-backend from 1.5.14 to 2.1.6 in /backstage

[dependabot]

Bumps @backstage/plugin-search-backend from 1.5.14 to 2.1.6.

Release notes

Sourced from @​backstage/plugin-search-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-search-backend's changelog.

@​backstage/plugin-search-backend

2.1.8-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-permission-node@​0.11.5-next.1
  • @​backstage/plugin-search-backend-node@​1.4.9-next.1

2.1.8-next.0

Patch Changes

• Updated dependencies
  • @​backstage/config@​1.3.10-next.0
  • @​backstage/errors@​1.3.2-next.0
  • @​backstage/backend-plugin-api@​1.10.2-next.0
  • @​backstage/plugin-permission-common@​0.9.12-next.0
  • @​backstage/plugin-permission-node@​0.11.5-next.0
  • @​backstage/plugin-search-backend-node@​1.4.9-next.0
  • @​backstage/backend-openapi-utils@​0.7.3-next.0
  • @​backstage/plugin-search-common@​1.2.26-next.0

2.1.7

Patch Changes

• b11c9b4: Fixed a bug where the search engine could receive an unfiltered query when no document types were permitted.
• Updated dependencies
  • @​backstage/backend-openapi-utils@​0.7.2
  • @​backstage/plugin-search-backend-node@​1.4.8
  • @​backstage/config@​1.3.9
  • @​backstage/plugin-permission-node@​0.11.4
  • @​backstage/backend-plugin-api@​1.10.1
  • @​backstage/plugin-permission-common@​0.9.11
  • @​backstage/plugin-search-common@​1.2.25

2.1.7-next.2

Patch Changes

• Updated dependencies
  • @​backstage/config@​1.3.9-next.0
  • @​backstage/backend-plugin-api@​1.10.1-next.1
  • @​backstage/plugin-permission-common@​0.9.11-next.0
  • @​backstage/plugin-permission-node@​0.11.4-next.1
  • @​backstage/plugin-search-backend-node@​1.4.8-next.1

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