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

[dependabot]

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

Release notes

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

v1.31.0

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

Backend System 1.0 🎉

The time has come for releasing the new Backend System as stable version 1.0! This means that the API is now stable and breaking changes should not occur until version 2.0, see our package versioning policy for more information about this.

There is documentation in place both for migrating backends and migrating plugins, and we encourage you to start doing so as soon as possible. Going forward, we will increasingly refer to this as "The backend system", and the previous one as "The old backend system". The main Backstage and community-plugins repositories have already been more or less fully migrated over.

The backend system brings a host of improvements to the way that backends and their features are constructed. Instead of the old convention-based structure that could lead to migration pains, features now fit together with dependency injection like a jigsaw puzzle while leveraging powerful core services and extending each other dynamically with additional behaviors. And this is just scratching the surface of it - do check out the docs!

We are very excited about this important milestone after a long period of development and refinement together with our passionate community, and hope that you will find it as refreshing and simple yet powerful as it was envisioned to be. This also lays the foundation for us being able to continue iterating at a high pace without incurring undue end user breakages during upgrades.

Keep the feedback coming! Either on the Community Discord, or through issues on GitHub. Also if you’re looking for a way to help, please take a look at these backstage and community plugins issues about deprecating old-backend capabilities of already migrated plugins.

Technical details

At a technical level, the following packages are now on major version 1, and their major version 0 will stop receiving feature updates:

• @backstage/backend-app-api
• @backstage/backend-plugin-api
• @backstage/backend-test-utils

The following packages are deprecated and frozen (have stopped receiving updates). Please use the above three packages and @backstage/backend-defaults to replace them. You may still use the compatibility adapters in @backstage/backend-common short term while performing a gradual migration.

• @backstage/backend-common
• @backstage/backend-tasks

The following core services have been entirely removed. Please migrate to the new auth system.

• coreServices.identity
• coreServices.tokenManager

The backwards compatibility with plugins using legacy auth through the token manager service has also been removed. This means that instead of falling back to using the old token manager, requests towards plugins that don't support the new auth system will simply fail. Please make sure that all plugins in your deployment are hosted within a backend instance from the new backend system; a mixture of new and old will lead to auth problems.

For a lot more detail about what changed and what migration steps might be needed, check the release notes for versions 1.27, 1.28, 1.29 and 1.30.

New Frontend System Updates

Some new things have landed in this version for the continued work on the New Frontend System. We’ve introduced the @backstage/plugin-app package, which is now responsible for housing the built in extensions and providing an entry point to override them using appPlugin.override().

There’s a new round of deprecations as we move forward with the New Frontend System. Namespace is no longer required to be provided to all extensions, or Blueprints and their respective .make or .makeWithOverrides methods. This will now default to the ID of the plugin that they are installed alongside.

We’ve deprecated createExtensionOverrides and introduced a new createFrontendModule method which replaces it and takes a required pluginId for which to associate the extensions that you’re providing to override or compliment the corresponding plugin.

We’ve also deprecated the createApp import from @backstage/frontend-app-api and you should now use the same import from @backstage/frontend-defaults instead which aligns nicely to the New Backend System patterns.

... (truncated)

Changelog

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

1.31.0

Minor Changes

• 406acb6: Add support to customize the about card icon links via EntityIconLinkBlueprint and provide a default catalog view catalog source, launch scaffolder template and read techdocs docs icon links extensions.

  BREAKING ALPHA

  The Scaffolder launch template and TechDocs read documentation icons have been extracted from the default Catalog about card links and are now provided respectively by the Scaffolder and TechDocs plugins in the new frontend system. It means that they will not be available unless you install the TechDocs and Scaffolder plugins. Also If you are using translation for these icon link titles other than the default, you should now translate them using the scaffolder translation reference or the TechDocs translation reference (the translation keys are still the same, aboutCard.viewTechdocs and aboutCard.launchTemplate).

• ec7b35d: Introduced backstage.io/techdocs-entity-path annotation which allows deep linking into another entities TechDocs in conjunction with backstage.io/techdocs-entity.

Patch Changes

• 18c64e9: Added the info.packageJson option to the plugin instance for the new frontend system.
• Updated dependencies
  • @​backstage/core-components@​0.17.3
  • @​backstage/catalog-client@​1.10.1
  • @​backstage/core-plugin-api@​1.10.8
  • @​backstage/frontend-plugin-api@​0.10.3
  • @​backstage/plugin-catalog-react@​1.19.0
  • @​backstage/plugin-techdocs-react@​1.3.0
  • @​backstage/plugin-techdocs-common@​0.1.1
  • @​backstage/plugin-search-react@​1.9.1
  • @​backstage/integration-react@​1.2.8
  • @​backstage/catalog-model@​1.7.4
  • @​backstage/core-compat-api@​0.4.3
  • @​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-permission-react@​0.4.35
  • @​backstage/plugin-scaffolder-common@​1.5.11
  • @​backstage/plugin-search-common@​1.2.18

1.31.0-next.2

Minor Changes

• 406acb6: Add support to customize the about card icon links via EntityIconLinkBlueprint and provide a default catalog view catalog source, launch scaffolder template and read techdocs docs icon links extensions.

  BREAKING ALPHA

  The Scaffolder launch template and TechDocs read documentation icons have been extracted from the default Catalog about card links and are now provided respectively by the Scaffolder and TechDocs plugins in the new frontend system. It means that they will not be available unless you install the TechDocs and Scaffolder plugins. Also If you are using translation for these icon link titles other than the default, you should now translate them using the scaffolder translation reference or the TechDocs translation reference (the translation keys are still the same, aboutCard.viewTechdocs and aboutCard.launchTemplate).

Patch Changes

• Updated dependencies
  • @​backstage/core-components@​0.17.3-next.0
  • @​backstage/plugin-catalog-react@​1.19.0-next.2

... (truncated)

Commits

• 698adeb Version Packages
• 3a196e0 Merge pull request #26609 from SzymonGr/master
• 0ff53c8 Enable loading state for paginated catalog tables by passing isLoading prop
• bc03a57 Fixed export and API Report
• 9adc552 Refactoring based on feedback
• 32fce06 Added missing items to overridableComponents
• 4735881 Version Packages (next)
• 836127c chore(deps): update dependency @​testing-library/react to v16
• 78475c3 feat: allow offset mode pagination in entity list
• c891b69 feat: add overrideable FavoriteToggle to core-components
• 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 #146.