dependabot(deps): bump @backstage/plugin-catalog from 1.24.0 to 1.30.0 in /backstage

[dependabot]

Bumps @backstage/plugin-catalog from 1.24.0 to 1.30.0.

Release notes

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

v1.30.0

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

New Frontend System - Plugin Adoption

This release marks another big milestone for the New Frontend System. We encourage all plugin owners to add support for the new frontend system to their plugins.

At the end of last year in the 1.21 release, we shipped the New Frontend System Alpha. It marked a more stable release of the new system, but we knew there was still much more work left to be done. Since then we have received valuable feedback and identified key areas of improvement. In particular around the creation of new extension kinds as well as overriding and testing of extensions.

Over the summer months we’ve been working hard towards addressing this feedback and getting the New Frontend System in shape for us to be confident in encouraging broader adoption by plugins. For a summary of the changes you can check out the 1.30 migration documentation, or can see the ongoing progress in the meta issue. With this release comes some new features, deprecations and breaking changes in the @backstage/frontend-app-api, @backstage/frontend-plugin-api, and @backstage/core-compat-api packages.

Breaking:

• All types of route references in the New Frontend System are now optional. This means that all usages of useRouteRef in the new system might return undefined, and your code must be able to act accordingly. Code that uses the old system (which will be the vast majority of code at this point) is not affected by this.

New:

• Blueprints and createExtensionBlueprint as a replacement for extension creators. You will find that old extension creators are marked as deprecated, and point to the corresponding blueprints which have a superior developer experience!
• Ability to override individual extensions using extension.override(...), as well as overriding extensions in a plugin using a combination of plugin.withOverrides([...]) and plugin.getExtension(id) to replace individual extensions or add new ones.
• createExtensionTester supports .get and .query to directly access extension data and streamline tests decoupled from React, as well as a .reactElement shorthand for accessing any output React elements.
• A new set of utilities that can patch support for the new frontend system for a plugin that otherwise only supports the old one. The new convertLegacyPlugin is used to convert a plugin instance, while convertLegacyPageExtension with friends can convert extensions from the old system.

Deprecations:

• createPlugin has been renamed to createFrontendPlugin
• createExtension with object keys for inputs and outputs has been deprecated in favor of the array form.
• configSchema in createExtension has been replaced with config.schema which is a better alternative to declaring config for extensions without having to use createSchemaFromZod.
• Existing dataRefs should now embed the ID using the .with method.
• The render method on createExtensionTester has been deprecated in favor of composing .reactElement with renderInTestApp.

BREAKING: Backend System deprecations and removals

• Almost all service factories in @backstage/backend-app-api were marked deprecated some time back - those are now removed. Please import them from their new homes in @backstage/backend-defaults/<service> instead.
• In our effort to migrate to the new backend system some backend-plugins createRouter exports have been marked as deprecated. Please make sure to update your backends accordingly as createRouter will eventually be removed from all plugin exports.
• Several deprecated methods and types have been removed from backend related packages. Most of these are either renamed and re-exported from other packages, see the CHANGELOG for the individual package for more information.

Most notably the long deprecated UrlReader exports have been renamed:

• ReadUrlOptions: Use UrlReaderServiceReadUrlOptions instead;
• ReadUrlResponse: Use UrlReaderServiceReadUrlResponse instead;
• ReadTreeOptions: Use UrlReaderServiceReadTreeOptions instead;
• ReadTreeResponse: Use UrlReaderServiceReadTreeResponse instead;
• ReadTreeResponseFile: Use UrlReaderServiceReadTreeResponseFile instead;
• ReadTreeResponseDirOptions: Use UrlReaderServiceReadTreeResponseDirOptions instead;
• SearchOptions: Use UrlReaderServiceSearchOptions instead;
• SearchResponse: Use UrlReaderServiceSearchResponse instead;

... (truncated)

Changelog

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

1.30.0

Minor Changes

• 970cb48: Show the pagination text for the offset-paginated catalog table, and remove the pagination bar from the top of the CatalogTable when pagination is enabled.

Patch Changes

• fb58f20: Internal update to use the new pluginId option of createFrontendPlugin.
• 2ddbc50: A new filter parameter has been added to EntityContextMenuItemBlueprint to make it easier to configure which entities a menu item should appear for. The filter parameter is a function which accepts an entity and returns a boolean.
• bf85d37: Fix for missing routeRef when using core-plugin-api in a dialog context
• Updated dependencies
  • @​backstage/frontend-plugin-api@​0.10.2
  • @​backstage/core-components@​0.17.2
  • @​backstage/catalog-model@​1.7.4
  • @​backstage/core-compat-api@​0.4.2
  • @​backstage/plugin-search-react@​1.9.0
  • @​backstage/plugin-catalog-react@​1.18.0
  • @​backstage/core-plugin-api@​1.10.7
  • @​backstage/catalog-client@​1.10.0
  • @​backstage/integration-react@​1.2.7
  • @​backstage/plugin-permission-react@​0.4.34
  • @​backstage/errors@​1.2.7
  • @​backstage/types@​1.2.1
  • @​backstage/version-bridge@​1.0.11
  • @​backstage/plugin-catalog-common@​1.1.4
  • @​backstage/plugin-scaffolder-common@​1.5.11
  • @​backstage/plugin-search-common@​1.2.18

1.30.0-next.3

Minor Changes

• 970cb48: Show the pagination text for the offset-paginated catalog table, and remove the pagination bar from the top of the CatalogTable when pagination is enabled.

Patch Changes

• Updated dependencies
  • @​backstage/plugin-search-react@​1.9.0-next.2
  • @​backstage/core-compat-api@​0.4.2-next.3
  • @​backstage/core-components@​0.17.2-next.1
  • @​backstage/core-plugin-api@​1.10.7-next.0
  • @​backstage/plugin-catalog-react@​1.18.0-next.3
  • @​backstage/catalog-client@​1.10.0-next.0
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/errors@​1.2.7
  • @​backstage/frontend-plugin-api@​0.10.2-next.1
  • @​backstage/integration-react@​1.2.7-next.3
  • @​backstage/types@​1.2.1
  • @​backstage/version-bridge@​1.0.11

... (truncated)

Commits

• 2a2c84b Version Packages
• ebe7c4d apply in more places
• d52ed1a frontend-plugin-api: store extension ID parts in an object type parameter
• af7be32 chore: api-reports
• 8cb9a85 chore: migrate rest of catalogt
• 45a469f chore: update apireports
• 896a84b chore: small fix
• 4c39af8 feat: small refactor for the search package
• 7999f61 chore: tidy up the last of the catalog tests
• 52a2e39 chore: fix package.json export
• Additional commits viewable 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 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)

[dependabot]

Labels

The following labels could not be found: kind/cleanup, ok-to-test, release-note-none. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[dependabot]

Superseded by #142.