Bump @backstage/plugin-catalog from 1.13.0 to 1.14.0 in /backstage

[dependabot]

Bumps @backstage/plugin-catalog from 1.13.0 to 1.14.0.

Release notes

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

v1.14.0

These are the release notes for the v1.14.0 release of Backstage.

A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for their hard work in getting this release developed and done.

Highlights

This release has an important security fix, along with a lot of squashed bugs and exciting additions! Enjoy.

BREAKING: Tweaks to the OpenAPI tooling

There’s been further work made on the OpenAPI tooling! One of the changes is that the commands for this feature are grouped under a schema openapi subcommand. This lets us structure things a bit better for the future. The generated file now also has a .generated.ts extension, to more easily be able to keep it apart in linting and similar.

BREAKING: Kubernetes plugin log viewer and tweaks

There’s been some awesome additions made to the Kubernetes plugin, including the ability to show pod logs! To support this, some breaking changes were made in some of its interfaces. Check out #17120 for some details of what changed.

DEPRECATION: React 16

We are preparing for React 18, and as part of doing that, we are now officially deprecating support for React 16. Nothing will break for you just yet, but if you are still on React 16 your backstage-cli commands will start to show helpful warning messages guiding you to bump to version 17 wehn you can.

See #17752 for some details about this, and links to the relevant issues.

New plugin: DevTools

This plugin is focused on integrators rather than end users. It allows you to see useful information about your Backstage installation, such as what operating system and NodeJS version it’s running on, what Backstage and individual package versions you have, and more! This may serve as a foundation for adding even more ops focused features in the future.

Contributed by @​awanlin in #17393

Migration to AWS-SDK version 3

There’s been work done under the hood to migrate AWS features over to using v3 of their client SDKs. While this should mostly go below the radar and ultimately work the same as it did before, do reach out to us if you encounter any problems that might be related to this migration.

There’s actually a minor interface breakage as part of this, where AwsIamKubernetesAuthTranslator has some methods removed, but that’s one which may not have a lot of use outside of the package.

Contributed by @​aochsner, see PRs linked at the bottom of issue #16470

Persistent session store for the auth backend

For auth providers that use session storage, those sessions are now persisted in the auth backend database, instead of in local memory. This should make session handling work better across scaled auth backend instances.

Markdown Output Support for Software Templates

You can now output Markdown from the Software Template runs which can provide more data to the end user after a job has completed in the outputs section of scaffolder/next

Contributed by @​voximity in #17641

Refactored Configuration Loading

The configuration loading system has been refactored to make it easier to extend the system with additional sources of configuration. See the initial PR and the @backstage/config-loader changelog for more details.

... (truncated)

Changelog

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

1.14.0

Minor Changes

• 28f1ab2e1a: The catalog plugin no longer implements the experimental reconfiguration API. The create button title can now instead be configured using the new experimental internationalization API, via the catalogTranslationRef exported at /alpha. For example:

  import { catalogTranslationRef } from '@backstage/plugin-catalog/alpha';
  const app = createApp({
  __experimentalTranslations: {
  resources: [
  createTranslationMessages({
  ref: catalogTranslationRef,
  catalog_page_create_button_title: 'Create Software',
  }),
  ],
  },
  });

• f3561a2935: include owner chip in catalog search result item

Patch Changes

• 7c4a8e4d5f: Create an experimental CatalogSearchResultItemExtension for declarative integration with Backstage; it can be accessed via the /alpha import.
• 0296f272b4: The `spec.lifecycle' field in entities will now always be rendered as a string.
• 0b55f773a7: Removed some unused dependencies
• 9a1fce352e: Updated dependency @testing-library/jest-dom to ^6.0.0.
• f95af4e540: Updated dependency @testing-library/dom to ^9.0.0.
• e5a2956dd2: Migrate catalog api to declarative integration system, it is exported from /alpha subpath.
• Updated dependencies
  • @​backstage/plugin-catalog-react@​1.8.5
  • @​backstage/frontend-plugin-api@​0.2.0
  • @​backstage/core-plugin-api@​1.7.0
  • @​backstage/core-components@​0.13.6
  • @​backstage/integration-react@​1.1.20
  • @​backstage/catalog-model@​1.4.3
  • @​backstage/errors@​1.2.3
  • @​backstage/plugin-search-react@​1.7.1
  • @​backstage/theme@​0.4.3
  • @​backstage/catalog-client@​1.4.5
  • @​backstage/types@​1.1.1
  • @​backstage/plugin-catalog-common@​1.0.17
  • @​backstage/plugin-scaffolder-common@​1.4.2
  • @​backstage/plugin-search-common@​1.2.7

1.14.0-next.2

Patch Changes

... (truncated)

Commits

• 73e7820 Version Packages
• 4f30767 Version Packages (next)
• 8b05da0 Version Packages (next)
• e04bb20 Version Packages (next)
• 6e726c7 Merge pull request #16348 from DavidAn830/daan/add-filter
• b9d824e Merge branch 'backstage:master' into daan/add-filter
• 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 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)