Bump @backstage/catalog-model from 1.2.1 to 1.4.1

[dependabot[bot]]

Bumps @backstage/catalog-model from 1.2.1 to 1.4.1.

Release notes

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

v1.4.0

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

Search is V1!

Backstage Search is now promoted to v1.0 with a stable Search API for plugin developers to add search to their plugins, and app integrators to expose that to their users.

No additional features are released as part of the major release as the maintainers of the search packages focused on the following for this release:

• Bug fixes and clean up of deprecations.
• Improved error handling for missing indices.
• Separation of AWS Elastic and Open Elastic support.
• Refactor the packages by moving reusable components from @backstage/plugin-search to @backstage/plugin-search-react.
• Improved documentation including tutorials for how to Integrate Search into a plugin.

With moving to v1.0 we also recommend using Elasticsearch for production usage. Moving forward, the search maintainers will prioritize the Elasticsearch engine while we’ll rely on the community to maintain the Postgres engine.

Experimental Backend System Evolution

This release adds the new @backstage/backend-app-api and @backstage/backend-plugin-api packages, both part of the evolution of the backend system. These packages are highly experimental and we do not recommend using them for any purpose, yet.

@backstage/cli Deprecation Removals

The @backstage/cli had a large number of deprecated commands removed, for example, app:build is now gone and should be replaced with package build. For a full list of commands that were removed, see the changelog.

@backstage/plugin-auth-backend Deprecation Removals

Many deprecated symbols have now been removed from @backstage/plugin-auth-backend, most notably the provider factories such as createGithubProvider have been removed, which should be replaced with providers.github.create. See the changelog for more details.

New module: @backstage/plugin-api-docs-module-protoc-gen-doc

This is a new module for @backstage/plugin-api-docs that exports a widget implementation for rendering gRPC docs generated by protoc-gen-doc. Contributed by @​kissmikijr #11923.

New module: @backstage/plugin-catalog-backend-module-openapi

This is a new module for @backstage/plugin-catalog-backend that exports a catalog processor which dereferences $ref fields in OpenAPI definitions. Contributed by @​mfrinnstrom #11645.

New plugin: @backstage/plugin-apollo-explorer

A plugin to embed the Apollo Explorer inside your Backstage instance to run queries against GraphQL endpoints. Contributed by @​unredundant #12600.

Security Fixes

@backstage/plugin-scaffolder-backend, please upgrade to the latest version if you are using this module.

Upgrade path

... (truncated)

Changelog

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

1.4.1

Patch Changes

• Updated dependencies
  • @​backstage/errors@​1.2.1
  • @​backstage/config@​1.0.8
  • @​backstage/types@​1.1.0

1.4.1-next.0

Patch Changes

• Updated dependencies
  • @​backstage/errors@​1.2.1-next.0
  • @​backstage/config@​1.0.8
  • @​backstage/types@​1.1.0

1.4.0

Minor Changes

• 33eae4b39a95: Deprecate target field and make targetRef required in common.schema.json

Patch Changes

• af748a148d52: Add OpenAPI Specification (OAS) v3.1.0 examples.
• 1df5fc954798: Remove requirement for 'target' property of EntityRelation
• Updated dependencies
  • @​backstage/types@​1.1.0
  • @​backstage/errors@​1.2.0
  • @​backstage/config@​1.0.8

1.4.0-next.1

Patch Changes

• af748a148d52: Add OpenAPI Specification (OAS) v3.1.0 examples.
• Updated dependencies
  • @​backstage/config@​1.0.7
  • @​backstage/errors@​1.2.0-next.0
  • @​backstage/types@​1.0.2

1.4.0-next.0

Minor Changes

• 33eae4b39a95: Deprecate target field and make targetRef required in common.schema.json

Patch Changes

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

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.