@backstage/core
- Introduced initial version of an inverted app/plugin relationship, where plugins export components for apps to use, instead registering themselves directly into the app. This enables more fine-grained control of plugin features, and also composition of plugins such as catalog pages with additional cards and tabs. This breaks the use of
RouteRefs, and there will be more changes related to this in the future, but this change lays the initial foundation. Seepackages/appand followup PRs for how to update plugins for this change. #2076 - Switch to an automatic dependency injection mechanism for all Utility APIs, allowing plugins to ship default implementations of their APIs. See https://backstage.io/docs/api/utility-apis. #2285
@backstage/cli
- Change
backstage-cli backend:build-imageto forward all args todocker image build, instead of just tag. Also add--buildflag for building all dependent packages before packaging the workspace for the docker build. #2299
@backstage/create-app
- Change root
tscoutput dir todist-types, in order to allow for standalone plugin repos. #2278
@backstage/catalog-backend
- We have simplified the way that GitHub ingestion works. The
catalog.processors.githubApikey is deprecated, in favor ofcatalog.processors.github. At the same time, the location typegithub/apiis likewise deprecated, in favor ofgithub. This location type now serves both raw HTTP reads and APIv3 reads, depending on how you configure it. It also supports having several providers at once - for example, both public GitHub and an internal GitHub Enterprise, with different keys. If you still use thecatalog.processors.githubApiconfig key, things will work but you will get a deprecation warning at startup. In a later release, support for the old key will go away entirely. See the configuration section in the docs for more details.