build(deps): bump @backstage/plugin-catalog-backend from 0.10.2 to 1.7.2 in /backstage

[dependabot]

Bumps @backstage/plugin-catalog-backend from 0.10.2 to 1.7.2.

Release notes

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

v1.7.2

This release fixes an issue where @backstage/plugin-tech-insights was using the wrong content type in requests, causing them to fail.

v1.7.1

This release fixes an issue where @backstage/create-app unintentionally required Git to be set up for it to be able to create a new project.

v1.7.0

These are the release notes for the v1.7.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

GitHub Catalog Import now Powered by the Backend

The analysis performed during catalog imports (i.e. when supplying the URL of a repository rather than an individual YAML file in the Create flow) is now powered by the backend rather than frontend code. This means that the catalog backend needs to be supplied with a location analyzer for this use case to continue to function.

If you want to make use of this feature, check out the installation instructions in the changelog.

Contributed by @​kissmikijr in #13800

Permission Rule Changes

When defining permission rules, it's now necessary to provide a Zod Schema that specifies the parameters the rule expects. This has been added to help better describe the parameters in the response of the metadata endpoint and to validate the parameters before a rule is executed. The signatures of the rule methods (apply and toQuery) have changed slightly as well.

You can read more about this in the permissions documentation and the changelog.

Migration: jest v29

Both jest, jest-runtime, and jest-environment-jsdom as used by the Backstage CLI were bumped to version 29. This is up from version 27, so check out both the v28 and v29 (later

... (truncated)

Changelog

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

1.7.2

Patch Changes

• 071354eb7d: Add additional validation as security precations for output entities.
• b977c2e69f: Minor improvements to the descriptions provided with permission rules schemas
• 2380506364: The process of adding or modifying fields in the software-catalog search index has been simplified. For more details, see how to customize fields in the Software Catalog index.
• 9573651919: The previous migration that adds the search.original_value column may leave some of the entities not updated. Add a migration script to trigger a reprocessing of the entities.
• 9f71a2fd20: Location rule target patterns now also match hidden files, i.e. path components with a leading dot.
• e716946103: Updated usage of the lifecycle service.
• 1aec041c34: Fixed an issue where entities sometimes were not properly deleted during a full mutation.
• 0ff03319be: Updated usage of createBackendPlugin.
• fc73f6aae5: Switched the order of reprocessing statements retroactively in migrations. This only improves the experience for those who at a later time perform a large upgrade of an old Backstage installation.
• Updated dependencies
  • @​backstage/backend-plugin-api@​0.4.0
  • @​backstage/backend-common@​0.18.2
  • @​backstage/catalog-model@​1.2.0
  • @​backstage/plugin-catalog-node@​1.3.3
  • @​backstage/catalog-client@​1.3.1
  • @​backstage/config@​1.0.6
  • @​backstage/errors@​1.1.4
  • @​backstage/integration@​1.4.2
  • @​backstage/types@​1.0.2
  • @​backstage/plugin-catalog-common@​1.0.11
  • @​backstage/plugin-permission-common@​0.7.3
  • @​backstage/plugin-permission-node@​0.7.5
  • @​backstage/plugin-scaffolder-common@​1.2.5
  • @​backstage/plugin-search-common@​1.2.1

1.7.2-next.2

Patch Changes

• e716946103: Updated usage of the lifecycle service.
• 0ff03319be: Updated usage of createBackendPlugin.
• Updated dependencies
  • @​backstage/backend-plugin-api@​0.4.0-next.2
  • @​backstage/backend-common@​0.18.2-next.2
  • @​backstage/catalog-model@​1.2.0-next.1
  • @​backstage/plugin-catalog-node@​1.3.3-next.2
  • @​backstage/plugin-permission-node@​0.7.5-next.2
  • @​backstage/catalog-client@​1.3.1-next.1
  • @​backstage/config@​1.0.6
  • @​backstage/errors@​1.1.4
  • @​backstage/integration@​1.4.2
  • @​backstage/types@​1.0.2
  • @​backstage/plugin-catalog-common@​1.0.11-next.1
  • @​backstage/plugin-permission-common@​0.7.3
  • @​backstage/plugin-scaffolder-common@​1.2.5-next.1
  • @​backstage/plugin-search-common@​1.2.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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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.