,
- ),
- ];
- },
-});
-```
diff --git a/.changeset/red-radios-promise.md b/.changeset/red-radios-promise.md
deleted file mode 100644
index ea876c3480..0000000000
--- a/.changeset/red-radios-promise.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-catalog-backend-module-gitlab': patch
----
-
-Adds new optional `excludeRepos` configuration option to the Gitlab catalog provider.
diff --git a/.changeset/renovate-147ac48.md b/.changeset/renovate-147ac48.md
deleted file mode 100644
index 257255dff1..0000000000
--- a/.changeset/renovate-147ac48.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-api-docs': patch
----
-
-Updated dependency `@graphiql/react` to `^0.23.0`.
diff --git a/.changeset/renovate-f04beb1.md b/.changeset/renovate-f04beb1.md
deleted file mode 100644
index 12d24ccc53..0000000000
--- a/.changeset/renovate-f04beb1.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-search-backend-module-explore': patch
----
-
-Updated dependency `@backstage-community/plugin-explore-common` to `^0.0.4`.
diff --git a/.changeset/rich-mugs-dress.md b/.changeset/rich-mugs-dress.md
deleted file mode 100644
index 5008e33a70..0000000000
--- a/.changeset/rich-mugs-dress.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@backstage/config-loader': patch
----
-
-Add boolean `allowMissingDefaultConfig` option to `ConfigSources.default` and
-`ConfigSources.defaultForTargets`, which results in omission of a ConfigSource
-for the default app-config.yaml configuration file if it's not present.
diff --git a/.changeset/selfish-bees-think.md b/.changeset/selfish-bees-think.md
deleted file mode 100644
index 15598ea551..0000000000
--- a/.changeset/selfish-bees-think.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/backend-defaults': patch
----
-
-Fixed the routing of the new health check service, the health endpoints should now properly be available at `/.backstage/health/v1/readiness` and `/.backstage/health/v1/liveness`.
diff --git a/.changeset/serious-cheetahs-help.md b/.changeset/serious-cheetahs-help.md
new file mode 100644
index 0000000000..88bad696c5
--- /dev/null
+++ b/.changeset/serious-cheetahs-help.md
@@ -0,0 +1,7 @@
+---
+'@backstage/plugin-catalog-react': patch
+'@backstage/plugin-search-react': patch
+'@backstage/plugin-catalog': patch
+---
+
+The `/alpha` export no longer export extension creators for the new frontend system, existing usage should be switched to use the equivalent extension blueprint instead. For more information see the [new frontend system 1.30 migration documentation](https://backstage.io/docs/frontend-system/architecture/migrations#130).
diff --git a/.changeset/seven-eggs-admire.md b/.changeset/seven-eggs-admire.md
deleted file mode 100644
index d68b38e2d7..0000000000
--- a/.changeset/seven-eggs-admire.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/create-app': patch
----
-
-Updated dockerfile and `app-config.production.yaml` to make it easier to get started with example data
diff --git a/.changeset/shaggy-dodos-applaud.md b/.changeset/shaggy-dodos-applaud.md
deleted file mode 100644
index b7f968aa39..0000000000
--- a/.changeset/shaggy-dodos-applaud.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/cli': patch
----
-
-Switched the target from `'ES2022'` to `'es2022'` for better compatibility with older versions of `swc`.
diff --git a/.changeset/sharp-mayflies-beg.md b/.changeset/sharp-mayflies-beg.md
new file mode 100644
index 0000000000..c78335c187
--- /dev/null
+++ b/.changeset/sharp-mayflies-beg.md
@@ -0,0 +1,5 @@
+---
+'@backstage/frontend-app-api': patch
+---
+
+Internal refactor following removal of v1 extension support. The app implementation itself still supports v1 extensions at runtime.
diff --git a/.changeset/shy-games-poke.md b/.changeset/shy-games-poke.md
deleted file mode 100644
index 1d2abff39c..0000000000
--- a/.changeset/shy-games-poke.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-notifications-backend-module-email': patch
----
-
-Add support for stream transport for debugging purposes
diff --git a/.changeset/shy-waves-share.md b/.changeset/shy-waves-share.md
deleted file mode 100644
index 861590fd01..0000000000
--- a/.changeset/shy-waves-share.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/backend-defaults': patch
----
-
-Update the `UrlReader` service to depends on multiple instances of `UrlReaderFactoryProvider` service.
diff --git a/.changeset/silly-candles-sin.md b/.changeset/silly-candles-sin.md
deleted file mode 100644
index b1d55113fd..0000000000
--- a/.changeset/silly-candles-sin.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-techdocs': patch
----
-
-TechDocs now supports the `mkdocs-redirects` plugin. Redirects defined using the `mkdocs-redirect` plugin will be handled automatically in TechDocs. Redirecting to external urls is not supported. In the case that an external redirect url is provided, TechDocs will redirect to the current documentation site home.
diff --git a/.changeset/silly-cycles-tan.md b/.changeset/silly-cycles-tan.md
deleted file mode 100644
index 517ce526ea..0000000000
--- a/.changeset/silly-cycles-tan.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-'@backstage/plugin-kubernetes-backend': patch
----
-
-Add `kubernetes.clusterLocatorMethods[].clusters[].customResources` to the configuration schema.
-This was already documented and supported by the plugin.
diff --git a/.changeset/silly-scissors-turn.md b/.changeset/silly-scissors-turn.md
deleted file mode 100644
index 985a6fb4fd..0000000000
--- a/.changeset/silly-scissors-turn.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/create-app': patch
----
-
-Included permission config and enabled it out of the box
diff --git a/.changeset/six-rats-kick.md b/.changeset/six-rats-kick.md
deleted file mode 100644
index 23958a2502..0000000000
--- a/.changeset/six-rats-kick.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder-backend-module-gitlab': patch
----
-
-Added test cases for gitlab:projectAccessToken:create example
diff --git a/.changeset/slow-ducks-rush.md b/.changeset/slow-ducks-rush.md
deleted file mode 100644
index c09f883e9c..0000000000
--- a/.changeset/slow-ducks-rush.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/core-compat-api': patch
----
-
-Both `compatWrapper` and `convertLegacyRouteRef` now support converting from the new system to the old.
diff --git a/.changeset/slow-ligers-drum.md b/.changeset/slow-ligers-drum.md
deleted file mode 100644
index 867cc07cee..0000000000
--- a/.changeset/slow-ligers-drum.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder-react': patch
----
-
-Fix null check in `isJsonObject` utility function for scaffolder review state component
diff --git a/.changeset/slow-toes-jog.md b/.changeset/slow-toes-jog.md
deleted file mode 100644
index 245feab544..0000000000
--- a/.changeset/slow-toes-jog.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-home': patch
----
-
-Fixed a bug on the WelcomeTitle component where the welcome message wasn't correct when the language was set to Spanish
diff --git a/.changeset/small-bottles-cough.md b/.changeset/small-bottles-cough.md
deleted file mode 100644
index 40098a84c7..0000000000
--- a/.changeset/small-bottles-cough.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-'@backstage/backend-plugin-api': minor
----
-
-The `createServiceRef` function now accepts a new boolean `multiple` option. The `multiple` option defaults to `false` and when set to `true`, it enables that multiple implementation are installed for the created service ref.
-
-We're looking for ways to make it possible to augment services without the need to replace the entire service.
-
-Typical example of that being the ability to install support for additional targets for the `UrlReader` service without replacing the service itself. This achieves that by allowing us to define services that can have multiple simultaneous implementation, allowing the `UrlReader` implementation to depend on such a service to collect all possible implementation of support for external targets:
-
-```diff
-// @backstage/backend-defaults
-
-+ export const urlReaderFactoriesServiceRef = createServiceRef({
-+ id: 'core.urlReader.factories',
-+ scope: 'plugin',
-+ multiton: true,
-+ });
-
-...
-
-export const urlReaderServiceFactory = createServiceFactory({
- service: coreServices.urlReader,
- deps: {
- config: coreServices.rootConfig,
- logger: coreServices.logger,
-+ factories: urlReaderFactoriesServiceRef,
- },
-- async factory({ config, logger }) {
-+ async factory({ config, logger, factories }) {
- return UrlReaders.default({
- config,
- logger,
-+ factories,
- });
- },
-});
-```
-
-With that, you can then add more custom `UrlReader` factories by installing more implementations of the `urlReaderFactoriesServiceRef` in your backend instance. Something like:
-
-```ts
-// packages/backend/index.ts
-import { createServiceFactory } from '@backstage/backend-plugin-api';
-import { urlReaderFactoriesServiceRef } from '@backstage/backend-defaults';
-...
-
-backend.add(createServiceFactory({
- service: urlReaderFactoriesServiceRef,
- deps: {},
- async factory() {
- return CustomUrlReader.factory;
- },
-}));
-
-...
-
-```
diff --git a/.changeset/small-ears-poke.md b/.changeset/small-ears-poke.md
deleted file mode 100644
index de906a8643..0000000000
--- a/.changeset/small-ears-poke.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-'@backstage/frontend-plugin-api': minor
----
-
-**BREAKING**: All types of route refs are always considered optional by `useRouteRef`, which means the caller must always handle a potential `undefined` return value. Related to this change, the `optional` option from `createExternalRouteRef` has been removed, since it is no longer necessary.
-
-This is released as an immediate breaking change as we expect the usage of the new route refs to be extremely low or zero, since plugins that support the new system will still use route refs and `useRouteRef` from `@backstage/core-plugin-api` in combination with `convertLegacyRouteRef` from `@backstage/core-compat-api`.
diff --git a/.changeset/small-spoons-shout.md b/.changeset/small-spoons-shout.md
deleted file mode 100644
index 76c209edc6..0000000000
--- a/.changeset/small-spoons-shout.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-'@backstage/cli': minor
----
-
-**BREAKING**: The lockfile (`yarn.lock`) dependency analysis and mutations have been removed from several commands.
-
-The `versions:bump` command will no longer attempt to bump and deduplicate dependencies by modifying the lockfile, it will only update `package.json` files.
-
-The `versions:check` command has been removed, since its only purpose was verification and mutation of the lockfile. We recommend using the `yarn dedupe` command instead, or the `yarn-deduplicate` package if you're using Yarn classic.
-
-The check that was built into the `package start` command has been removed, it will no longer warn about lockfile mismatches.
-
-The packages in the Backstage ecosystem handle package duplications much better now than when these CLI features were first introduced, so the need for these features has diminished. By removing them, we drastically reduce the integration between the Backstage CLI and Yarn, making it much easier to add support for other package managers in the future.
diff --git a/.changeset/smooth-countries-relate.md b/.changeset/smooth-countries-relate.md
deleted file mode 100644
index 5e86ee8ab5..0000000000
--- a/.changeset/smooth-countries-relate.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-catalog-graph': patch
----
-
-Use `entityPresentationApi` for the node title and the icon.
diff --git a/.changeset/soft-gorillas-refuse.md b/.changeset/soft-gorillas-refuse.md
deleted file mode 100644
index 323c4d20d2..0000000000
--- a/.changeset/soft-gorillas-refuse.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/backend-test-utils': patch
----
-
-The default services for `startTestBackend` and `ServiceFactoryTester` now includes the Root Health Service.
diff --git a/.changeset/spicy-lies-listen.md b/.changeset/spicy-lies-listen.md
deleted file mode 100644
index 6bc5e95846..0000000000
--- a/.changeset/spicy-lies-listen.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder': patch
----
-
-Fix helper text margin for scaffolder EntityNamePicker and EntityTagsPicker when using outlined text field
diff --git a/.changeset/spicy-planets-provide.md b/.changeset/spicy-planets-provide.md
deleted file mode 100644
index f2929df850..0000000000
--- a/.changeset/spicy-planets-provide.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-'@backstage/plugin-notifications-backend-module-email': minor
----
-
-**BREAKING** Following `NotificationTemplateRenderer` methods now return a Promise and **must** be awaited: `getSubject`, `getText` and `getHtml`.
-
-Required changes and example usage:
-
-```diff
-import { notificationsEmailTemplateExtensionPoint } from '@backstage/plugin-notifications-backend-module-email';
-import { Notification } from '@backstage/plugin-notifications-common';
-+import { getNotificationSubject, getNotificationTextContent, getNotificationHtmlContent } from 'my-notification-processing-library`
-export const notificationsModuleEmailDecorator = createBackendModule({
- pluginId: 'notifications',
- moduleId: 'email.templates',
- register(reg) {
- reg.registerInit({
- deps: {
- emailTemplates: notificationsEmailTemplateExtensionPoint,
- },
- async init({ emailTemplates }) {
- emailTemplates.setTemplateRenderer({
-- getSubject(notification) {
-+ async getSubject(notification) {
-- return `New notification from ${notification.source}`;
-+ const subject = await getNotificationSubject(notification);
-+ return `New notification from ${subject}`;
- },
-- getText(notification) {
-+ async getText(notification) {
-- return notification.content;
-+ const text = await getNotificationTextContent(notification);
-+ return text;
- },
-- getHtml(notification) {
-+ async getHtml(notification) {
-- return `
${notification.content}
`;
-+ const html = await getNotificationHtmlContent(notification);
-+ return html;
- },
- });
- },
- });
- },
-});
-```
diff --git a/.changeset/spotty-planets-accept.md b/.changeset/spotty-planets-accept.md
deleted file mode 100644
index 7342f89bd1..0000000000
--- a/.changeset/spotty-planets-accept.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder': patch
----
-
-Cleaned up codebase of RepoUrlPicker
diff --git a/.changeset/strange-papayas-beg.md b/.changeset/strange-papayas-beg.md
deleted file mode 100644
index 6ce33fb029..0000000000
--- a/.changeset/strange-papayas-beg.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder-backend-module-gitlab': patch
----
-
-Added test cases for gitlab:pipeline:trigger examples
diff --git a/.changeset/strong-otters-compete.md b/.changeset/strong-otters-compete.md
deleted file mode 100644
index fdcb982b88..0000000000
--- a/.changeset/strong-otters-compete.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/cli': patch
----
-
-Add support for dynamic plugins via the EXPERIMENTAL_MODULE_FEDERATION environment variable when running `yarn start`.
diff --git a/.changeset/stupid-dots-relate.md b/.changeset/stupid-dots-relate.md
deleted file mode 100644
index a83777bff9..0000000000
--- a/.changeset/stupid-dots-relate.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder-backend-module-cookiecutter': patch
----
-
-Add examples for `fetch:cookiecutter` scaffolder action & improve related tests
diff --git a/.changeset/sweet-oranges-buy.md b/.changeset/sweet-oranges-buy.md
deleted file mode 100644
index d9f3343e3d..0000000000
--- a/.changeset/sweet-oranges-buy.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/frontend-plugin-api': patch
----
-
-Added support to be able to define `zod` config schema in Blueprints, with built in schema merging from the Blueprint and the extension instances.
diff --git a/.changeset/swift-kings-sparkle.md b/.changeset/swift-kings-sparkle.md
deleted file mode 100644
index 84ceae962b..0000000000
--- a/.changeset/swift-kings-sparkle.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-catalog-backend-module-aws': patch
----
-
-`AwsOrganizationCloudAccountProcessor` configuration field `roleArn` is deprecated in favor of new field `accountId`
diff --git a/.changeset/tall-snakes-fix.md b/.changeset/tall-snakes-fix.md
deleted file mode 100644
index 351c781375..0000000000
--- a/.changeset/tall-snakes-fix.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/backend-plugin-api': patch
----
-
-fix typo in `getPluginRequestToken` comments
diff --git a/.changeset/tasty-ads-rescue.md b/.changeset/tasty-ads-rescue.md
deleted file mode 100644
index d522856bdd..0000000000
--- a/.changeset/tasty-ads-rescue.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/backend-defaults': patch
----
-
-Avoid excessive numbers of error listeners on cache clients
diff --git a/.changeset/thick-hotels-know.md b/.changeset/thick-hotels-know.md
deleted file mode 100644
index f0c7129256..0000000000
--- a/.changeset/thick-hotels-know.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder-backend': patch
----
-
-Fix scaffolder action `catalog:write` to write to directories that don't already exist
diff --git a/.changeset/thirty-adults-grab.md b/.changeset/thirty-adults-grab.md
deleted file mode 100644
index ed986a8289..0000000000
--- a/.changeset/thirty-adults-grab.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-'@backstage/plugin-search-backend-node': patch
-'@backstage/plugin-catalog-node': patch
----
-
-Explicit declare if the service ref accepts `single` or `multiple` implementations.
diff --git a/.changeset/thirty-paws-hope.md b/.changeset/thirty-paws-hope.md
deleted file mode 100644
index 0de607f331..0000000000
--- a/.changeset/thirty-paws-hope.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/core-app-api': patch
----
-
-The request to delete the session cookie when running the app in protected mode is now done with a plain `fetch` rather than `FetchApi`. This fixes a bug where the app would immediately try to sign-in again when removing the cookie during logout.
diff --git a/.changeset/tiny-oranges-pretend.md b/.changeset/tiny-oranges-pretend.md
deleted file mode 100644
index 87227fb962..0000000000
--- a/.changeset/tiny-oranges-pretend.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-'@backstage/frontend-plugin-api': patch
----
-
-Extension data references can now be defined in a way that encapsulates the ID string in the type, in addition to the data type itself. The old way of creating extension data references is deprecated and will be removed in a future release.
-
-For example, the following code:
-
-```ts
-export const myExtension = createExtensionDataRef('my-plugin.my-data');
-```
-
-Should be updated to the following:
-
-```ts
-export const myExtension = createExtensionDataRef().with({
- id: 'my-plugin.my-data',
-});
-```
diff --git a/.changeset/tough-goats-hang.md b/.changeset/tough-goats-hang.md
deleted file mode 100644
index 2608c03b2e..0000000000
--- a/.changeset/tough-goats-hang.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder': minor
----
-
-Added field extension `RepoBranchPicker` that supports autocompletion for Bitbucket
diff --git a/.changeset/tough-lies-repair.md b/.changeset/tough-lies-repair.md
deleted file mode 100644
index b2f848e292..0000000000
--- a/.changeset/tough-lies-repair.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder': patch
----
-
-Fix issue with `RepoUrlPicker` not refreshing the credentials for a different host
diff --git a/.changeset/tricky-ducks-juggle.md b/.changeset/tricky-ducks-juggle.md
deleted file mode 100644
index 48c0d215bd..0000000000
--- a/.changeset/tricky-ducks-juggle.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/backend-app-api': patch
----
-
-Added configuration for the `packages` options to config schema
diff --git a/.changeset/two-emus-work.md b/.changeset/two-emus-work.md
deleted file mode 100644
index 3c60086043..0000000000
--- a/.changeset/two-emus-work.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/cli': patch
----
-
-New command now supports setting package license
diff --git a/.changeset/violet-jokes-wave.md b/.changeset/violet-jokes-wave.md
deleted file mode 100644
index 623cff2583..0000000000
--- a/.changeset/violet-jokes-wave.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/cli': patch
----
-
-Fix for `repo build --all` not properly detecting the experimental public entry point.
diff --git a/.changeset/warm-monkeys-marry.md b/.changeset/warm-monkeys-marry.md
deleted file mode 100644
index 5ea8deae01..0000000000
--- a/.changeset/warm-monkeys-marry.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder-backend-module-sentry': patch
----
-
-Added test cases for sentry:project:create examples
diff --git a/.changeset/wicked-bobcats-teach.md b/.changeset/wicked-bobcats-teach.md
deleted file mode 100644
index 041e336f7d..0000000000
--- a/.changeset/wicked-bobcats-teach.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-auth-react': patch
----
-
-feat: Hide visibility of CookieAuthRedirect
diff --git a/.changeset/wild-eggs-exist.md b/.changeset/wild-eggs-exist.md
deleted file mode 100644
index 68c49e343b..0000000000
--- a/.changeset/wild-eggs-exist.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-'@backstage/plugin-scaffolder-backend-module-gitlab': patch
----
-
-Add custom action for merge request: **auto**
-
-The **Auto** action selects the committed action between _create_ and _update_.
-
-The **Auto** action fetches files using the **/projects/repository/tree endpoint**.
-After fetching, it checks if the file exists locally and in the repository. If it does, it chooses **update**; otherwise, it chooses **create**.
diff --git a/.changeset/wise-spiders-walk.md b/.changeset/wise-spiders-walk.md
deleted file mode 100644
index 65793041c5..0000000000
--- a/.changeset/wise-spiders-walk.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-techdocs': patch
----
-
-Fixed issue where header styles were incorrectly generated when themes used CSS variables to define font size.
diff --git a/.changeset/witty-bears-behave.md b/.changeset/witty-bears-behave.md
deleted file mode 100644
index 174467b9eb..0000000000
--- a/.changeset/witty-bears-behave.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/integration': patch
----
-
-Updated functions for `getHarnessEditContentsUrl`, `getHarnessFileContentsUrl`, `getHarnessArchiveUrl`, `getHarnessLatestCommitUrl` and `parseHarnessUrl` to handle account and org level urls
diff --git a/.changeset/witty-geese-battle.md b/.changeset/witty-geese-battle.md
deleted file mode 100644
index 082784cc8b..0000000000
--- a/.changeset/witty-geese-battle.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-catalog-react': patch
----
-
-Entity page extensions created for the new frontend system via the `/alpha` exports will now be enabled by default.
diff --git a/.changeset/witty-timers-marry.md b/.changeset/witty-timers-marry.md
deleted file mode 100644
index 4193acb6fc..0000000000
--- a/.changeset/witty-timers-marry.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/plugin-bitbucket-cloud-common': patch
----
-
-Added method `listBranchesByRepository` to `BitbucketCloudClient`
diff --git a/.changeset/young-games-visit.md b/.changeset/young-games-visit.md
deleted file mode 100644
index 467abcec86..0000000000
--- a/.changeset/young-games-visit.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-'@backstage/frontend-plugin-api': patch
-'@backstage/frontend-test-utils': patch
-'@backstage/frontend-app-api': patch
-'@backstage/core-compat-api': patch
-'@backstage/plugin-catalog-react': patch
-'@backstage/plugin-user-settings': patch
-'@backstage/plugin-search-react': patch
-'@backstage/plugin-techdocs': patch
-'@backstage/plugin-catalog': patch
-'@backstage/plugin-search': patch
----
-
-Added config input type to the extensions
diff --git a/.changeset/young-peaches-shake.md b/.changeset/young-peaches-shake.md
deleted file mode 100644
index 75c93f8f3b..0000000000
--- a/.changeset/young-peaches-shake.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@backstage/config-loader': minor
----
-
-Add configuration key to File and Remote `ConfigSource`s that enables configuration of parsing logic. Previously limited to yaml, these `ConfigSource`s now allow for a multitude of parsing options (e.g. JSON).
diff --git a/.github/vale/config/vocabularies/Backstage/accept.txt b/.github/vale/config/vocabularies/Backstage/accept.txt
index 42b0e4895c..320bb2e0ce 100644
--- a/.github/vale/config/vocabularies/Backstage/accept.txt
+++ b/.github/vale/config/vocabularies/Backstage/accept.txt
@@ -243,8 +243,10 @@ Mkdocs
monorepo
Monorepo
monorepos
+morgan
msgraph
msw
+multiton
mutex
mutexes
mysql
diff --git a/ADOPTERS.md b/ADOPTERS.md
index 3b534052f1..76114b6965 100644
--- a/ADOPTERS.md
+++ b/ADOPTERS.md
@@ -134,7 +134,6 @@ _You can do this by using the [Adopter form](https://info.backstage.spotify.com/
| [SafetyCulture](https://safetyculture.com/) | [@R-cen](https://github.com/R-cen), [@lachlancooper](https://github.com/lachlancooper), [@hkf57](https://github.com/hkf57) | Internal developer portal to provide a centralized place for engineers to see an overview of their team's services and information related to the service from other systems. Initially focused on the software catalog, techdocs and search. |
| [Sana Life Science](https://sanalifescience.com) | [Joe Hillyard](mailto:joe@sanalifescience.com) | API Catalog, Tools Management & Control Hub |
| [Ndustrial](https://ndustrial.io) | [Jonathan Skubic](mailto:jonathan@ndustrial.io) | Software Project Catalog |
-| [TUI Musement](https://www.musement.com/uk/) | [Simone Fumagalli](mailto:simone.fumagalli@musement.com) | We are importing our catalog into it to keep it under control. The next step is start using templates |
| [Kambi AB](https://www.kambi.com) | [Martin Norum](mailto:martin.norum@kambi.com) | We want to kick ass at speed, so we're currently building up a catalog of our existing software, and looking into how Backstage can support us in our journey towards autonomous product teams. Both to improve speed to market and operational awareness. |
| [ANZ](https://www.anz.com.au/personal/) | [Elliot Jackson](mailto:elliot.jackson@anz.com) | Catalog, tech docs and automation |
| [Genie Solutions](https://www.geniesolutionssoftware.com.au) | [Zainab Bagasrawala](mailto:zainabbagasrawala@geniesolutions.com.au) | Developer Portal to track our projects, documentation, observability tools and more |
diff --git a/README-zh_Hans.md b/README-zh_Hans.md
index 2813ee0793..129c7e7aa4 100644
--- a/README-zh_Hans.md
+++ b/README-zh_Hans.md
@@ -55,7 +55,7 @@ Backstage 的文档包括:
- [Discord 聊天室](https://discord.gg/backstage-687207715902193673) - 获得支持或讨论项目
- [参与贡献 Backstage](https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md) - 如果您想做出贡献,请从这里开始
- [RFCs](https://github.com/backstage/backstage/labels/rfc) - 帮助制定技术方向
-- [FAQ](https://backstage.io/docs/FAQ) - n.: 常问问题
+- [FAQ](https://backstage.io/docs/FAQ) - 常问问题
- [行为准则](CODE_OF_CONDUCT.md) - 这是我们的行事方式
- [采纳者](ADOPTERS.md) - 已经在使用 Backstage 的公司
- [博客](https://backstage.io/blog/) - 公告和更新
diff --git a/README.md b/README.md
index 6c27d01db2..4cba1082b0 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,5 @@
[](https://backstage.io/)
-> [!NOTE]
-> 🏖 From July 1st through 16th, due to maintainers being on summer vacations, expect the project to move a little slower than normal, and support to be limited. Normal service will resume after that! 🏝
-
# [Backstage](https://backstage.io)
English \| [한국어](README-ko_kr.md) \| [中文版](README-zh_Hans.md) \| [Français](README-fr_FR.md)
diff --git a/beps/00010-event-auditor/README.md b/beps/00010-event-auditor/README.md
new file mode 100644
index 0000000000..3bf7eb2e0d
--- /dev/null
+++ b/beps/00010-event-auditor/README.md
@@ -0,0 +1,183 @@
+---
+title: Event Auditor
+status: provisional
+authors:
+ - '@schultzp2020'
+owners:
+project-areas:
+ - core
+creation-date: 2024-06-04
+---
+
+# BEP: Event Auditor
+
+[**Discussion Issue**](https://github.com/backstage/backstage/issues/23950)
+
+- [BEP: Event Auditor](#bep-event-auditor)
+ - [Summary](#summary)
+ - [Motivation](#motivation)
+ - [Goals](#goals)
+ - [Non-Goals](#non-goals)
+ - [Proposal](#proposal)
+ - [Design Details](#design-details)
+ - [Data Model for Audit Events](#data-model-for-audit-events)
+ - [Actor Details Interface](#actor-details-interface)
+ - [Audit Request/Response Interfaces](#audit-requestresponse-interfaces)
+ - [Audit Event Status Interfaces](#audit-event-status-interfaces)
+ - [EventAuditor Interface](#eventauditor-interface)
+ - [Release Plan](#release-plan)
+ - [Dependencies](#dependencies)
+ - [Alternatives](#alternatives)
+
+## Summary
+
+This feature introduces a dedicated system for recording critical security-related actions and events within Backstage. By maintaining a distinct audit event stream, organizations benefit from enhanced security, improved regulatory compliance, efficient incident response, and ensured data integrity.
+
+## Motivation
+
+- Strengthen security by tracking user authentication, authorization, data access, and configuration changes.
+- Facilitate adherence to regulatory requirements through logging security-sensitive operations.
+- Enable efficient forensic analysis and investigation of security incidents.
+- Uphold the integrity of critical audit data by implementing robust access controls and tamper-proof measures.
+
+### Goals
+
+- Develop a backend service for the audit event stream to record security-critical events.
+- Ensure compliance with regulatory requirements through detailed audit event logging.
+ - Refer to [NIST: Audit and Accountability](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=AU)
+ - Refer to [NIST: Non-Repudiation](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=AU-10)
+- Establish a standardized data format for audit events.
+ - Refer to [NIST: Content of Audit Records](https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_1_1/home?element=AU-03)
+- Provide access to the transport layer for customizable output options.
+
+### Non-Goals
+
+- Implementing mechanisms for event storage, analysis, or visualization.
+- Addressing security aspects of event storage and access control beyond initial separation from regular events.
+
+Both of these non-goals can be implemented as separate plugins.
+
+## Proposal
+
+The proposal introduces a crucial change to implement a dedicated audit event stream in Backstage. We recommend creating a new backend service using Winston to establish a distinct channel specifically for audit events. This service would act as a wrapper around Winston, providing methods with strict interfaces to ensure uniformity across audit events throughout the Backstage application. By separating the configuration, we can clearly distinguish between regular application events and critical security events. The event format would include mandatory fields relevant to regulatory compliance and security investigations, such as actor, IP address, timestamp, and event details. This standardized format would streamline the analysis and investigation of security-related events.
+
+Overall, this approach offers several benefits. Separating the configuration allows for the clear distinction of security-critical events, enhancing monitoring and analysis. The standardized data format within the service ensures consistency and facilitates compliance with regulations. Finally, the service methods simplify the process of logging audit events.
+
+## Design Details
+
+### Data Model for Audit Events
+
+To ensure consistency and facilitate regulatory compliance, the proposal suggests creating a shared package that defines a data model for audit events. This model consists of several key components.
+
+#### Actor Details Interface
+
+This interface defines the information related to the actor who triggered the logged event. It includes fields like actor ID, IP address, hostname, and user agent.
+
+```ts
+export type ActorDetails = {
+ actorId?: string;
+ ip?: string;
+ hostname?: string;
+ userAgent?: string;
+};
+```
+
+#### Audit Request/Response Interfaces
+
+These interfaces define the structure of request and response data that might be included in the audit event. It's important to note that these interfaces exclude sensitive information like tokens from headers or other irrelevant details to avoid security risks.
+
+```ts
+export type AuditRequest = {
+ url: string;
+ method: string;
+};
+
+export type AuditResponse = {
+ status: number;
+};
+```
+
+#### Audit Event Status Interfaces
+
+These interfaces define the possible statuses for an audit event entry. There are three options:
+
+```ts
+/**
+ * Indicates the event was successful.
+ */
+export type AuditEventSuccessStatus = { status: 'succeeded' };
+
+/**
+ * Indicates the event failed and includes details about the encountered errors.
+ */
+export type AuditEventFailureStatus = {
+ status: 'failed';
+ errors: E[];
+};
+
+export type AuditEventStatus = AuditEventSuccessStatus | AuditEventFailureStatus | undefined;
+```
+
+#### EventAuditor Interface
+
+This interface defines the functionalities of an `EventAuditor` class. This class provides methods for:
+- Extracting the actor ID from an Express request (if available).
+- Creating detailed audit event information based on provided options.
+- Logging an audit event with a specific level (info, debug, warn, or error).
+
+```ts
+/**
+ * Common fields of an audit event.
+ *
+ * @public
+ */
+export type AuditEventOptions = AuditEventStatus & {
+ eventName: string;
+ message: string;
+ stage: string;
+ level?: 'info' | 'debug' | 'warn' | 'error';
+ metadata?: JsonValue;
+ response?: AuditResponse;
+ request?: Request;
+} & ({ actorId: string; } | { credentials: BackstageCredentials } | undefined);
+
+export type AuditEvent = {
+ actor: ActorDetails;
+ eventName: string;
+ stage: string;
+ isAuditLog: true;
+ request?: AuditRequest;
+ response?: AuditResponse;
+} & AuditLogStatus;
+
+export interface EventAuditor {
+ /**
+ * Processes an express request and obtains the actorId from it. Returns undefined if actorId is not obtainable.
+ *
+ * @public
+ */
+ getActorId(request?: Request): Promise;
+
+ /**
+ * Generates an Audit Event and logs it at the level passed by the user.
+ * Supports `info`, `debug`, `warn` or `error` level. Defaults to `info` if no level is passed.
+ *
+ * Secrets in the metadata field and request body, params and query field should be redacted by the user before passing in the request object
+ * @public
+ */
+ auditEvent(options: AuditEventOptions): Promise;
+}
+```
+
+## Release Plan
+
+The release plan involves initially creating a shared audit event package. Following this, the audit event will be implemented in core packages and other plugins. The first targets should be high-priority areas, such as the scaffolder and catalog systems. Since adding the audit event will not disrupt existing functionality, the release plan is simplified.
+
+## Dependencies
+
+- `@backstage/types`
+-
+
+## Alternatives
+
+N/A
diff --git a/beps/0010-scaffolder-templating-in-parameters/README.md b/beps/0010-scaffolder-templating-in-parameters/README.md
new file mode 100644
index 0000000000..354dc66ea9
--- /dev/null
+++ b/beps/0010-scaffolder-templating-in-parameters/README.md
@@ -0,0 +1,223 @@
+---
+title: Supporting templating syntax in `parameters` schema
+status: provisional
+authors:
+ - '@benjdlambert'
+owners:
+ - '@benjdlambert'
+ - '@backstage/scaffolder-maintainers'
+project-areas:
+ - scaffolder
+creation-date: 2024-03-26
+---
+
+
+
+# BEP: Supporting templating syntax in `parameters` schema
+
+
+
+[**Discussion Issue**](https://github.com/backstage/backstage/issues/16275)
+
+- [Summary](#summary)
+- [Motivation](#motivation)
+ - [Goals](#goals)
+ - [Non-Goals](#non-goals)
+- [Proposal](#proposal)
+- [Design Details](#design-details)
+- [Release Plan](#release-plan)
+- [Dependencies](#dependencies)
+- [Alternatives](#alternatives)
+
+## Summary
+
+
+
+This BEP proposes to add support for templating syntax in the `parameters` schema of a scaffolder template.
+This will allow users to define properties in the JSON Schema which are templated from current values that have been collected from the user already.
+This can be useful when you want to use a value that has already been collected as a default value in another field.
+
+For example:
+
+```yaml
+apiVersion: scaffolder.backstage.io/v1beta3
+kind: Template
+metadata:
+ name: my-template
+spec:
+ parameters:
+ - title: Some input
+ description: Get some info from the user
+ properties:
+ name:
+ type: string
+ default: Test
+ description:
+ type: string
+ default: ${{ parameters.name or "unknown" }}-description
+```
+
+## Motivation
+
+
+
+Inclusive of the initial RFC there's been a swarm of issues that are requesting this feature, and we want to align on the implementation and design of this feature.
+
+See the following:
+
+- https://github.com/backstage/backstage/issues/16275
+- https://github.com/backstage/backstage/pull/23283
+- https://github.com/backstage/backstage/issues/19597
+- https://github.com/backstage/backstage/issues/20533
+- https://github.com/backstage/backstage/pull/17746
+
+There's some ideas for introducing a templating syntax for both templating into the `parameters` schema, and also being able to pass through some templating strings to underlying field extensions that can use those templating strings.
+We want to align here so that we're not going to have those conflict or compete, and create a standard for how to achieve templating in both circumstances.
+
+### Goals
+
+
+
+- This BEP will settle the implementation for the templating of fields into the JSON Schema in the `parameters` section in the scaffolder templates.
+- This BEP will settle how to pass through templating strings to underlying field extensions in a non-conflicting way.
+
+### Non-Goals
+
+
+
+## Proposal
+
+The proposal is to be able to decorate the template schema server side with a context and use that to drive the form rendering client side.
+
+We can extend the `/parameter-schema` endpoint to accept a `formData` context query parameter which will be a JSON object of the current `formData` state. This in turn allows the scaffolder frontend to repeatedly call the endpoint to get the updated rendered parameter schema. We'll need to turn the endpoint into a `POST` endpoint to accept the form data, but will retain the `GET` version for backwards compatibility.
+
+## Design Details
+
+### Example implementation of the `/parameter-schema` endpoint
+
+```diff
+export interface ScaffolderApi {
+ getTemplateParameterSchema(
+ templateRef: string,
++ formData?: JsonObject,
+ ): Promise;
+}
+```
+
+```diff
+ router
+- .get(
++ .post(
+ '/v2/templates/:namespace/:kind/:name/parameter-schema',
+ async (req, res) => {
+ const credentials = await httpAuth.credentials(req);
+ const { token } = await auth.getPluginRequestToken({
+ onBehalfOf: credentials,
+ targetPluginId: 'catalog',
+ });
+ const template = await authorizeTemplate(
+ req.params,
+ token,
+ credentials,
+ );
+
+ const parameters = [template.spec.parameters ?? []].flat();
++ const secureTemplater = await SecureTemplater.loadRenderer({
++ templateFilters: {
++ ...createDefaultFilters({ integrations }),
++ ...additionalTemplateFilters,
++ },
++ templateGlobals: additionalTemplateGlobals,
++ });
++
++ const templatedParameters = parameters.map(parameter =>
++ renderTemplateString(
++ parameter,
++ {
++ parameters: req.body.formData,
++ },
++ secureTemplater,
++ logger,
++ ),
++ );
+```
+
+You can see a quick implementation of this in this [branch](https://github.com/backstage/backstage/compare/master...blam/templating-in-parameters)
+
+### Workaround for the `default` field
+
+There's a slight issue with the implementation of the `react-jsonschema-form`, which makes things like live updating on things like the `default` field slightly more difficult.
+Currently, on first render, the default value is populated and then stored in the `formData` object or the current state, and the default value is never re-evaluated again at a later stage.
+
+This means that if end users are wanting to set default values with `${{ parameters.myOtherProperty }}`, then they would need to ensure that they are on different steps in the form
+as the form would need to be re-rendered, and for performance reasons, we don't want to re-render the form on every `formData` update.
+
+We could fix this, by implementing custom logic for when the `parameter-schema` is updated, if the updated field is in a `default: *` field, then we replace the previous value with the new value in the `formData` automatically.
+This is a pretty ugly workaround, but maybe the only option we have. Also at this point, pretty unsure if this affects any other parts of the `JSONSchema`, and we would also have to implement it for those fields if they exist.
+
+### Templated error messages
+
+Templating for `errorMessages` has been solved by using the `ajv-errors` library https://github.com/backstage/backstage/pull/25624, you can see more about [`backrefs` and pointers here](https://ajv.js.org/packages/ajv-errors.html). Any other template strings that will be passed through the underlying components and to be left untemplated should be encapsulated with options instead of passing through raw strings. The below example illustrates an `entityAndName` format, which under the hood, might do something like `${{ parameters.entity }} - ${{ parameters.name }}`, but this implementation never leaks out to the templating language.
+
+```yaml
+parameters:
+ properties:
+ ...
+ description:
+ type: string
+ default: Test-description
+ ui:field: CustomDisplayField
+ ui:options:
+ format: entityAndName
+```
+
+## Release Plan
+
+
+
+This change is backwards compatible, and can be released in a minor release. There's no breaking changes to worry about here.
+
+## Dependencies
+
+
+
+## Alternatives
+
+
+
+### Templating client side
+
+- This could lead to confusion as `filters` such as `parseRepoUrl` and `pick` and any custom filters which you define in the backend would not be available in the client side.
+
+- Also with the limitations of the `default` value being updated only on first render and never re-evaluated, there's no performance benefit of doing things client side anymore.
+
+### Accept limitation of the `default` field
+
+Rather than using a workaround to support re-evaluating the `default` field, we could instead accept it as a limitation, and document it as such.
+
+This is not desirable, as it is likely a very common use-case to want to template the `default` field, leading to a poor template creation experience.
diff --git a/contrib/docker/minimal-hardened-image/Dockerfile b/contrib/docker/minimal-hardened-image/Dockerfile
index 8ee6a3d206..a247e0dff1 100644
--- a/contrib/docker/minimal-hardened-image/Dockerfile
+++ b/contrib/docker/minimal-hardened-image/Dockerfile
@@ -9,53 +9,79 @@
#
# Once the commands have been run, you can build the image using `yarn docker-build`
-FROM cgr.dev/chainguard/wolfi-base:latest
+# syntax = docker/dockerfile:1.4
-ENV NODE_VERSION 18=~18.19
-ENV PYTHON_VERSION 3.12=~3.12
+# Build Python environment in a separate builder stage
+FROM cgr.dev/chainguard/python:latest-dev as python-builder
-RUN apk add nodejs-$NODE_VERSION yarn
+ENV PATH=/venv/bin:$PATH
-# Install sqlite3 dependencies. You can skip this if you don't use sqlite3 in the image,
-# in which case you should also move better-sqlite3 to "devDependencies" in package.json.
-# Additionally, we install dependencies for `techdocs.generator.runIn: local`.
-# https://backstage.io/docs/features/techdocs/getting-started#disabling-docker-in-docker-situation-optional
-RUN --mount=type=cache,target=/var/cache/apk,sharing=locked \
- --mount=type=cache,target=/var/lib/apk,sharing=locked \
- apk update && \
- apk add sqlite-dev python-$PYTHON_VERSION py3-pip python-3-dev py3-setuptools build-base gcc libffi-dev glibc-dev openssl-dev brotli-dev c-ares-dev nghttp2-dev icu-dev zlib-dev gcc-12 libuv-dev && \
- yarn config set python /usr/bin/python3
+RUN --mount=type=cache,target=/home/nonroot/.cache/pip,uid=65532,gid=65532 \
+ python3 -m venv /home/nonroot/venv && \
+ /home/nonroot/venv/bin/pip install mkdocs-techdocs-core==1.3.3
-# Set up a virtual environment for mkdocs-techdocs-core.
-ENV VIRTUAL_ENV=/opt/venv
-RUN python3 -m venv $VIRTUAL_ENV
-ENV PATH="$VIRTUAL_ENV/bin:$PATH"
+# Build Node environment in a separate builder stage
+FROM cgr.dev/chainguard/wolfi-base:latest as node-builder
-RUN pip3 install mkdocs-techdocs-core==1.3.3
-
-# From here on we use the least-privileged `node` user to run the backend.
-WORKDIR /app
-RUN chown nonroot:nonroot /app
-USER nonroot
-
-# This switches many Node.js dependencies to production mode.
+ENV NODE_VERSION 20=~20.11
ENV NODE_ENV production
-# Copy over Yarn 3 configuration, release, and plugins
-COPY --chown=nonroot:nonroot .yarn ./.yarn
-COPY --chown=nonroot:nonroot .yarnrc.yml ./
+RUN --mount=type=cache,target=/var/cache/apk,sharing=locked,uid=65532,gid=65532 \
+ --mount=type=cache,target=/var/lib/apk,sharing=locked,uid=65532,gid=65532 \
+ apk update && \
+ apk add nodejs-$NODE_VERSION yarn \
+ # Install isolate-vm dependencies, these are needed by the @backstage/plugin-scaffolder-backend.
+ openssl-dev brotli-dev c-ares-dev nghttp2-dev icu-dev zlib-dev gcc-12 libuv-dev build-base
-# Copy repo skeleton first, to avoid unnecessary docker cache invalidation.
-# The skeleton contains the package.json of each package in the monorepo,
-# and along with yarn.lock and the root package.json, that's enough to run yarn install.
-COPY --chown=nonroot:nonroot yarn.lock package.json packages/backend/dist/skeleton.tar.gz ./
+WORKDIR /app
+RUN chown -R nonroot:nonroot /app
+
+RUN mkdir -p /home/nonroot/.yarn/berry && chown -R 65532:65532 /home/nonroot/.yarn/berry
+
+USER nonroot
+
+COPY --chown=65532:65532 .yarn ./.yarn
+COPY --chown=65532:65532 .yarnrc.yml ./
+
+COPY --chown=65532:65532 yarn.lock package.json packages/backend/dist/skeleton.tar.gz ./
RUN tar xzf skeleton.tar.gz && rm skeleton.tar.gz
-RUN --mount=type=cache,target=/home/node/.yarn/berry/cache,sharing=locked,uid=1000,gid=1000 \
- yarn workspaces focus --all --production
+RUN --mount=type=cache,target=/home/nonroot/.yarn/berry/cache,sharing=locked,uid=65532,gid=65532 \
+ yarn workspaces focus --all --production && yarn cache clean --all
-# Then copy the rest of the backend bundle, along with any other files we might want.
-COPY --chown=nonroot:nonroot packages/backend/dist/bundle.tar.gz app-config*.yaml ./
-RUN tar xzf bundle.tar.gz && rm bundle.tar.gz
+# Final stage to build the application image
+FROM cgr.dev/chainguard/wolfi-base:latest
+ENV PYTHON_VERSION 3.12=~3.12
+ENV NODE_VERSION 20=~20.14
+ENV NODE_ENV production
+
+RUN --mount=type=cache,target=/var/cache/apk,sharing=locked,uid=65532,gid=65532 \
+ --mount=type=cache,target=/var/lib/apk,sharing=locked,uid=65532,gid=65532 \
+ apk update && \
+ apk add \
+ # add node for backstage
+ nodejs-$NODE_VERSION \
+ # add python for backstage techdocs
+ python-$PYTHON_VERSION \
+ # add tini for init process
+ tini
+
+WORKDIR /app
+
+COPY package.json app-config.yaml ./
+ADD packages/backend/dist/skeleton.tar.gz packages/backend/dist/bundle.tar.gz ./
+
+RUN chown -R 65532:65532 /app
+RUN chown -R 65532:65532 /tmp
+USER 65532:65532
+
+COPY --from=node-builder --chown=65532:65532 /app/node_modules ./node_modules
+COPY --from=python-builder --chown=65532:65532 /home/nonroot/venv /home/nonroot/venv
+ENV PATH=/home/nonroot/venv/bin:$PATH
+
+ENV NODE_OPTIONS="--no-node-snapshot"
+ENV GIT_PYTHON_REFRESH="quiet"
+
+ENTRYPOINT ["tini", "--"]
CMD ["node", "packages/backend", "--config", "app-config.yaml"]
diff --git a/contrib/docker/minimal-hardened-image/README.md b/contrib/docker/minimal-hardened-image/README.md
index 62045a4ded..191c77986c 100644
--- a/contrib/docker/minimal-hardened-image/README.md
+++ b/contrib/docker/minimal-hardened-image/README.md
@@ -4,6 +4,19 @@ DockerHub images in general did not seem ideal for Backstage as the number of vu
The `Dockerfile` in this directory uses a [wolfi-base](https://github.com/wolfi-dev) image from Chainguard Images. This improves the security of the application and reduces false positives in scanners.
+## Steps taken
+
+When converting, I utilized the upstream Dockerfile as a starting point.
+
+- Multi-stage build - The Dockerfile has been split up into a multistage build which reduces the files, packages, executables, and directories in the final image.
+ - Size savings = ~900mb
+ - Reduced attack surface
+- Base Image - Swap to [wolfi-base](https://github.com/wolfi-dev) image from Chainguard Images
+ - Vulnerability Savings = ~239 at the time of updating this README
+- Entrypoint - Swap from `node` to `tini` as entrypoint to ensure that the default signal handlers work and zombie processes are handled properly
+- Use `ADD` instead of `COPY` in dockerfile to reduce copied compressed files
+ - When a `rm` is used to remove a compressed file it still makes its way into the final image. Using `ADD` is safe with local files.
+
## Pinning Digest
To reduce maintenance, the digest of the image has been removed from the `./Dockerfile` file. A complete example with the digest would be `cgr.dev/chainguard/wolfi-base:latest@sha256:3d6dece13cdb5546cd03b20e14f9af354bc1a56ab5a7b47dca3e6c1557211fcf` and it is suggested to update the `FROM` line in the `Dockerfile` to use a digest.
diff --git a/contrib/docs/tutorials/prometheus-metrics.md b/contrib/docs/tutorials/prometheus-metrics.md
index fb4366c7f7..0db97c649e 100644
--- a/contrib/docs/tutorials/prometheus-metrics.md
+++ b/contrib/docs/tutorials/prometheus-metrics.md
@@ -1,5 +1,8 @@
# Prometheus
+> [!NOTE]
+> The Prometheus metrics have been marked as deprecated and will be removed at a later point. The recommendation is to use the OpenTelemetry metrics by following the [Setup OpenTelemetry](https://backstage.io/docs/tutorials/setup-opentelemetry) documentation
+
## Overview
This is a small tutorial that goes over how to setup your Backstage instance to output metrics in a format that can be pulled in by Prometheus.
diff --git a/docs/auth/aws-alb/provider.md b/docs/auth/aws-alb/provider.md
index 8f21b7dbf0..a3974c895e 100644
--- a/docs/auth/aws-alb/provider.md
+++ b/docs/auth/aws-alb/provider.md
@@ -11,14 +11,18 @@ and get the user seamlessly authenticated.
## Configuration
The provider configuration can be added to your `app-config.yaml` under the root
-`auth` configuration:
+`auth` configuration, similar to the following example:
```yaml title="app-config.yaml"
auth:
providers:
awsalb:
- issuer: 'https://example.okta.com/oauth2/default' # optional
- region: 'us-west-2' # required, use your actual region here
+ # this is the URL of the IdP you configured
+ issuer: 'https://example.okta.com/oauth2/default'
+ # this is the ARN of your ALB instance
+ signer: 'arn:aws:elasticloadbalancing:us-east-2:123456789012:loadbalancer/app/my-load-balancer/1234567890123456'
+ # this is the region where your ALB instance resides
+ region: 'us-west-2'
signIn:
resolvers:
# typically you would pick one of these
@@ -26,6 +30,8 @@ auth:
- resolver: emailLocalPartMatchingUserEntityName
```
+Ensure that you have set the signer correctly. It is also recommended that you restrict your target groups' security policy to only accept connections from that ALB.
+
### Resolvers
This provider includes several resolvers out of the box that you can use:
diff --git a/docs/auth/cloudflare/provider.md b/docs/auth/cloudflare/provider.md
index 516ea9d647..a1946580a7 100644
--- a/docs/auth/cloudflare/provider.md
+++ b/docs/auth/cloudflare/provider.md
@@ -32,6 +32,12 @@ auth:
serviceTokens:
- token: '1uh2fh19efvfh129f1f919u21f2f19jf2.access'
subject: 'bot-user@your-company.com'
+ # You can customize the header name that contains the jwt token, by default
+ # cf-access-jwt-assertion is used
+ jwtHeaderName:
+ # You can customize the authorization cookie name, by default
+ # CF_Authorization is used
+ authorizationCookieName:
# This picks what sign in resolver(s) you want to use.
signIn:
resolvers:
diff --git a/docs/auth/google/gcp-iap-auth.md b/docs/auth/google/gcp-iap-auth.md
index 6479ac7268..298f212399 100644
--- a/docs/auth/google/gcp-iap-auth.md
+++ b/docs/auth/google/gcp-iap-auth.md
@@ -24,7 +24,7 @@ Let's start by adding the following `auth` configuration in your
```yaml
auth:
providers:
- gcp-iap:
+ gcpIap:
audience: '/projects//global/backendServices/'
jwtHeader: x-custom-header # Optional: Only if you are using a custom header for the IAP JWT
signIn:
@@ -77,6 +77,6 @@ backend.add(import('@backstage/plugin-auth-backend-module-gcp-iap-provider'));
## Adding the provider to the Backstage frontend
-See [Sign-In with Proxy Providers](../index.md#sign-in-with-proxy-providers) for pointers on how to set up the sign-in page, and to also make it work smoothly for local development. You'll use `gcp-iap` as the provider name.
+See [Sign-In with Proxy Providers](../index.md#sign-in-with-proxy-providers) for pointers on how to set up the sign-in page, and to also make it work smoothly for local development. You'll use `gcpIap` as the provider name.
If you [provide a custom sign in resolver](https://backstage.io/docs/auth/identity-resolver#building-custom-resolvers), you can skip the `signIn` block entirely.
diff --git a/docs/auth/index.md b/docs/auth/index.md
index 5188d7e2a4..de579d039a 100644
--- a/docs/auth/index.md
+++ b/docs/auth/index.md
@@ -112,9 +112,16 @@ const app = createApp({
});
```
-You can also use the `providers` prop to enable multiple sign-in methods, for example
+:::note Note
-- allowing guest access:
+You can configure sign-in to use a redirect flow with no pop-up by adding
+`enableExperimentalRedirectFlow: true` to the root of your `app-config.yaml`
+
+:::
+
+### Using Multiple Providers
+
+You can also use the `providers` prop to enable multiple sign-in methods, for example to allow guest access:
```tsx title="packages/app/src/App.tsx"
const app = createApp({
@@ -140,12 +147,53 @@ const app = createApp({
});
```
-:::note Note
+### Conditionally Render Sign In Provider
-You can configure sign-in to use a redirect flow with no pop-up by adding
-`enableExperimentalRedirectFlow: true` to the root of your `app-config.yaml`
+In the above example you have both Guest and GitHub sign-in options, this is helpful for non-production but in Production you will most likely not want to offer Guest access. You can easily use information from your config to help conditionally render the provider:
-:::
+```tsx title="packages/app/src/App.tsx"
+import {
+ configApiRef,
+ githubAuthApiRef,
+ useApi,
+} from '@backstage/core-plugin-api';
+
+const app = createApp({
+ components: {
+ SignInPage: props => {
+ const configApi = useApi(configApiRef);
+ if (configApi.getString('auth.environment') === 'development') {
+ return (
+
+ );
+ }
+ return (
+
+ );
+ },
+ },
+ // ..
+});
+```
## Sign-In with Proxy Providers
diff --git a/docs/backend-system/architecture/05-extension-points.md b/docs/backend-system/architecture/05-extension-points.md
index 4b7f893f0b..12c4ec75f5 100644
--- a/docs/backend-system/architecture/05-extension-points.md
+++ b/docs/backend-system/architecture/05-extension-points.md
@@ -78,7 +78,7 @@ Another pattern that can be used is a type of singleton pattern where the extens
```ts
interface ScaffolderTaskRunnerExtensionPoint {
- setTaskRunner(taskRunner: TaskRunner): void;
+ setTaskRunner(taskRunner: SchedulerServiceTaskRunner): void;
}
```
diff --git a/docs/backend-system/architecture/06-modules.md b/docs/backend-system/architecture/06-modules.md
index eb00e737e3..010f36109c 100644
--- a/docs/backend-system/architecture/06-modules.md
+++ b/docs/backend-system/architecture/06-modules.md
@@ -52,7 +52,7 @@ This allows you to install the module in your backend instance by just referenci
```ts
backend.add(
- import('backstage-plugin-catalog-backend-module-example-processor'),
+ import('@internal/backstage-plugin-catalog-backend-module-example-processor'),
);
```
diff --git a/docs/backend-system/core-services/root-http-router.md b/docs/backend-system/core-services/root-http-router.md
index b3522e1752..88a10455f5 100644
--- a/docs/backend-system/core-services/root-http-router.md
+++ b/docs/backend-system/core-services/root-http-router.md
@@ -52,19 +52,49 @@ You can configure the root HTTP Router service by passing the options to the `cr
```ts
import { rootHttpRouterServiceFactory } from '@backstage/backend-app-api';
+import { RequestHandler } from 'express';
+import morgan from 'morgan';
const backend = createBackend();
backend.add(
rootHttpRouterServiceFactory({
configure: ({ app, middleware, routes, config, logger, lifecycle }) => {
+ // Refer to https://expressjs.com/en/guide/writing-middleware.html on how to write express middleware
+ const customMiddleware = {
+ logging(): RequestHandler {
+ const middlewareLogger = logger.child({
+ type: 'incomingRequest',
+ });
+ return (req, res, next) => {
+ // Custom Logging Implementation
+ next();
+ };
+ },
+ // Default logging middleware uses the [morgan](https://github.com/expressjs/morgan) middleware which you can configure with custom formats.
+ morganLogging(): RequestHandler {
+ const middlewareLogger = logger.child({
+ type: 'incomingRequest',
+ });
+ const customMorganFormat =
+ '[:date[clf]] ":method :url HTTP/:http-version" :status ":user-agent"';
+ return morgan(customMorganFormat, {
+ stream: {
+ write(message: string) {
+ logger.info(message.trimEnd());
+ },
+ },
+ });
+ },
+ };
+
// the built in middleware is provided through an option in the configure function
app.use(middleware.helmet());
app.use(middleware.cors());
app.use(middleware.compression());
// you can add you your own middleware in here
- app.use(custom.logging());
+ app.use(customMiddleware.logging());
// here the routes that are registered by other plugins
app.use(routes);
diff --git a/docs/deployment/docker.md b/docs/deployment/docker.md
index d47cb248f8..897498d28f 100644
--- a/docs/deployment/docker.md
+++ b/docs/deployment/docker.md
@@ -246,6 +246,9 @@ WORKDIR /app
# Copy the install dependencies from the build stage and context
COPY --from=build --chown=node:node /app/yarn.lock /app/package.json /app/packages/backend/dist/skeleton/ ./
+# Note: The skeleton bundle only includes package.json files -- if your app has
+# plugins that define a `bin` export, the bin files need to be copied as well to
+# be linked in node_modules/.bin during yarn install.
RUN --mount=type=cache,target=/home/node/.cache/yarn,sharing=locked,uid=1000,gid=1000 \
yarn install --frozen-lockfile --production --network-timeout 600000
diff --git a/docs/features/search/collators.md b/docs/features/search/collators.md
new file mode 100644
index 0000000000..27860bfd64
--- /dev/null
+++ b/docs/features/search/collators.md
@@ -0,0 +1,107 @@
+---
+id: collators
+title: Collators
+description: Indexing you Backstage content with Collators
+---
+
+Backstage includes 2 [collators](./concepts.md#collators) out of the box for the [Catalog](#catalog) and [TechDocs](#techdocs). There's also some from the [Backstage Community](#community-collators) too!
+
+## Catalog
+
+The Catalog collator will index all the Entities in your Catalog. It is installed by default but if you need to add it manually here's how.
+
+First we add the plugin into your backend app:
+
+```bash title="From your Backstage root directory"
+yarn --cwd packages/backend add @backstage/plugin-search-backend-module-catalog
+```
+
+Then add the following line:
+
+```ts title="packages/backend/src/index.ts"
+const backend = createBackend();
+
+// Other plugins...
+
+// search plugin
+backend.add(import('@backstage/plugin-search-backend/alpha'));
+
+/* highlight-add-start */
+backend.add(import('@backstage/plugin-search-backend-module-catalog/alpha'));
+/* highlight-add-end */
+
+backend.start();
+```
+
+### Configuring the Catalog Collator
+
+The default schedule for the Catalog Collator is to run every 10 minutes, you can provide your own schedule by adding it to your config:
+
+```yaml title="app-config.yaml
+search:
+ collators:
+ catalog:
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
+ # supports cron, ISO duration, "human duration" as used in code
+ initialDelay: { seconds: 90 }
+ # supports cron, ISO duration, "human duration" as used in code
+ frequency: { hours: 6 }
+ # supports ISO duration, "human duration" as used in code
+ timeout: { minutes: 3 }
+```
+
+## TechDocs
+
+The TechDocs collator will index all the TechDocs in your Catalog. It is installed by default but if you need to add it manually here's how.
+
+First we add the plugin into your backend app:
+
+```bash title="From your Backstage root directory"
+yarn --cwd packages/backend add @backstage/plugin-search-backend-module-techdocs
+```
+
+Then add the following line:
+
+```ts title="packages/backend/src/index.ts"
+const backend = createBackend();
+
+// Other plugins...
+
+// search plugin
+backend.add(import('@backstage/plugin-search-backend/alpha'));
+
+/* highlight-add-start */
+backend.add(import('@backstage/plugin-search-backend-module-techdocs/alpha'));
+/* highlight-add-end */
+
+backend.start();
+```
+
+### Configuring the TechDocs Collator
+
+The default schedule for the TechDocs Collator is to run every 10 minutes, you can provide your own schedule by adding it to your config:
+
+```yaml title="app-config.yaml
+search:
+ collators:
+ techdocs:
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
+ # supports cron, ISO duration, "human duration" as used in code
+ initialDelay: { seconds: 90 }
+ # supports cron, ISO duration, "human duration" as used in code
+ frequency: { hours: 6 }
+ # supports ISO duration, "human duration" as used in code
+ timeout: { minutes: 3 }
+```
+
+## Community Collators
+
+Here are some of the known Search Collators available in from the Backstage Community:
+
+- [`@backstage/plugin-search-backend-module-explore`](https://github.com/backstage/backstage/tree/master/plugins/search-backend-module-explore): will index content from the [Explore plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/explore/plugins/explore).
+- [`@backstage/plugin-search-backend-module-stack-overflow-collator`](https://github.com/backstage/backstage/tree/master/plugins/search-backend-module-stack-overflow-collator): will index content from Stack Overflow.
+- [`@backstage-community/search-backend-module-adr`](https://github.com/backstage/community-plugins/tree/main/workspaces/adr/plugins/search-backend-module-adr): will index content from the [ADR plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/adr/plugins/adr).
+
+## Custom Collators
+
+To create your own collators/decorators modules, please use the [searchModuleCatalogCollator](https://github.com/backstage/backstage/blob/d7f955f300893f50c4882ea8f5c09aa42dfaacfd/plugins/search-backend-module-catalog/src/alpha.ts#L49) as an example, we recommend that modules are separated by plugin packages (e.g. `search-backend-module-`). You can also find the available search engines and collator/decorator modules documentation in the Alpha API reports.
diff --git a/docs/features/search/concepts.md b/docs/features/search/concepts.md
index 69a7223085..a777c2f53c 100644
--- a/docs/features/search/concepts.md
+++ b/docs/features/search/concepts.md
@@ -86,7 +86,7 @@ Search chooses to completely rebuild indices on a schedule. Different collators
can be configured to refresh at different intervals, depending on how often the
source information is updated. When search indexing is distributed among multiple
backend nodes, coordination to prevent clashes is typically handled by a
-distributed `TaskRunner`.
+distributed `SchedulerServiceTaskRunner`.
### The Search Page
diff --git a/docs/features/search/getting-started.md b/docs/features/search/getting-started.md
index b2a074974f..362b7fc46d 100644
--- a/docs/features/search/getting-started.md
+++ b/docs/features/search/getting-started.md
@@ -133,79 +133,34 @@ For more information about using `Root.tsx`, please see
Add the following plugins into your backend app:
```bash title="From your Backstage root directory"
-yarn --cwd packages/backend add @backstage/plugin-search-backend @backstage/plugin-search-backend-node
+yarn --cwd packages/backend add @backstage/plugin-search-backend @backstage/plugin-search-backend-module-pg @backstage/plugin-search-backend-module-catalog @backstage/plugin-search-backend-module-techdocs
```
-Create a `packages/backend/src/plugins/search.ts` file containing the following
-code:
+Then add the following lines:
-```typescript
-import { useHotCleanup } from '@backstage/backend-common';
-import { createRouter } from '@backstage/plugin-search-backend';
-import {
- IndexBuilder,
- LunrSearchEngine,
-} from '@backstage/plugin-search-backend-node';
-import { PluginEnvironment } from '../types';
-import { DefaultCatalogCollator } from '@backstage/plugin-catalog-backend';
-import { Router } from 'express';
+```ts title="packages/backend/src/index.ts"
+const backend = createBackend();
-export default async function createPlugin(
- env: PluginEnvironment,
-): Promise {
- const searchEngine = new LunrSearchEngine({
- logger: env.logger,
- });
- const indexBuilder = new IndexBuilder({
- logger: env.logger,
- searchEngine,
- });
+// Other plugins...
- const every10MinutesSchedule = env.scheduler.createScheduledTaskRunner({
- frequency: { minutes: 10 },
- timeout: { minutes: 15 },
- initialDelay: { seconds: 3 },
- });
+/* highlight-add-start */
+// search plugin
+backend.add(import('@backstage/plugin-search-backend/alpha'));
- indexBuilder.addCollator({
- schedule: every10MinutesSchedule,
- factory: DefaultCatalogCollatorFactory.fromConfig(env.config, {
- discovery: env.discovery,
- tokenManager: env.tokenManager,
- }),
- });
+// search engines
+backend.add(import('@backstage/plugin-search-backend-module-pg/alpha'));
- const { scheduler } = await indexBuilder.build();
+// search collators
+backend.add(import('@backstage/plugin-search-backend-module-catalog/alpha'));
+backend.add(import('@backstage/plugin-search-backend-module-techdocs/alpha'));
+/* highlight-add-end */
- scheduler.start();
- useHotCleanup(module, () => scheduler.stop());
-
- return await createRouter({
- engine: indexBuilder.getSearchEngine(),
- logger: env.logger,
- });
-}
+backend.start();
```
-Make the following modifications to your `packages/backend/src/index.ts` file:
+With the above setup Search will use the [Lunr](https://github.com/olivernn/lunr.js) in-memory Search Engine but if your have Postgres setup as your database then it will use Postgres as your Search Engine. Learn more in the [Search Engines](./search-engines.md) documentation.
-Import the `plugins/search` file you created above:
-
-```typescript
-import search from './plugins/search';
-```
-
-Set up an environment for search:
-
-```typescript
-const searchEnv = useHotMemoize(module, () => createEnv('search'));
-```
-
-Register the search service with the router:
-
-```typescript
-apiRouter.use('/search', await search(searchEnv));
-```
+The above also sets up two Collators for you - Catalog and TechDocs - which will index content from these two locations so that you can easily search them. Learn more in the [Collators documentation](./collators.md).
## Customizing Search
@@ -328,7 +283,7 @@ Backstage Search builds and maintains its index
[on a schedule](./concepts.md#the-scheduler). You can change how often the
indexes are rebuilt for a given type of document. You may want to do this if
your documents are updated more or less frequently. You can do so by configuring
-a scheduled `TaskRunner` to pass into the `schedule` value, like this:
+a scheduled `SchedulerServiceTaskRunner` to pass into the `schedule` value, like this:
```typescript {3}
const every10MinutesSchedule = env.scheduler.createScheduledTaskRunner({
@@ -347,16 +302,19 @@ indexBuilder.addCollator({
```
Note: if you are using the in-memory Lunr search engine, you probably want to
-implement a non-distributed `TaskRunner` like the following to ensure consistency
+implement a non-distributed `SchedulerServiceTaskRunner` like the following to ensure consistency
if you're running multiple search backend nodes (alternatively, you can configure
the search plugin to use a non-distributed database such as
[SQLite](../../tutorials/configuring-plugin-databases.md#postgresql-and-sqlite-3)):
```typescript
-import { TaskInvocationDefinition, TaskRunner } from '@backstage/backend-tasks';
+import {
+ SchedulerServiceTaskRunner,
+ SchedulerServiceTaskInvocationDefinition,
+} from '@backstage/backend-plugin-api';
-const schedule: TaskRunner = {
- run: async (task: TaskInvocationDefinition) => {
+const schedule: SchedulerServiceTaskRunner = {
+ run: async (task: SchedulerServiceTaskInvocationDefinition) => {
const startRefresh = async () => {
while (!task.signal?.aborted) {
try {
diff --git a/docs/features/search/how-to-guides.md b/docs/features/search/how-to-guides.md
index 9ce30da556..b0df9440f3 100644
--- a/docs/features/search/how-to-guides.md
+++ b/docs/features/search/how-to-guides.md
@@ -45,75 +45,6 @@ to do that in two steps.
});
```
-## How to index TechDocs documents
-
-The TechDocs plugin has supported integrations to Search, meaning that it
-provides a default collator factory ready to be used.
-
-The purpose of this guide is to walk you through how to register the
-[DefaultTechDocsCollatorFactory](https://github.com/backstage/backstage/blob/1adc2c7/plugins/search-backend-module-techdocs/src/collators/DefaultTechDocsCollatorFactory.ts)
-in your App, so that you can get TechDocs documents indexed.
-
-If you have been through the
-[Getting Started with Search guide](https://backstage.io/docs/features/search/getting-started),
-you should have the `packages/backend/src/plugins/search.ts` file available. If
-so, you can go ahead and follow this guide - if not, start by going through the
-getting started guide.
-
-1. Import the `DefaultTechDocsCollatorFactory` from
- `@backstage/plugin-search-backend-module-techdocs`.
-
- ```typescript
- import { DefaultTechDocsCollatorFactory } from '@backstage/plugin-search-backend-module-techdocs';
- ```
-
-2. If there isn't an existing schedule you'd like to run the collator on, be
- sure to create it first. Something like...
-
- ```typescript
- import { Duration } from 'luxon';
-
- const every10MinutesSchedule = env.scheduler.createScheduledTaskRunner({
- frequency: Duration.fromObject({ seconds: 600 }),
- timeout: Duration.fromObject({ seconds: 900 }),
- initialDelay: Duration.fromObject({ seconds: 3 }),
- });
- ```
-
-3. Register the `DefaultTechDocsCollatorFactory` with the IndexBuilder.
-
- ```typescript
- indexBuilder.addCollator({
- schedule: every10MinutesSchedule,
- factory: DefaultTechDocsCollatorFactory.fromConfig(env.config, {
- discovery: env.discovery,
- logger: env.logger,
- tokenManager: env.tokenManager,
- }),
- });
- ```
-
-You should now have your TechDocs documents indexed to your search engine of
-choice!
-
-If you want your users to be able to filter down to the techdocs type when
-searching, you can update your `SearchPage.tsx` file in
-`packages/app/src/components/search` by adding `techdocs` to the list of values
-of the `SearchType` component.
-
-```tsx title="packages/app/src/components/search/SearchPage.tsx"
-
-
- {/* ... */}
-
-```
-
-> Check out the documentation around [integrating search into plugins](../../plugins/integrating-search-into-plugins.md#create-a-collator) for how to create your own collator.
-
## How to customize fields in the Software Catalog or TechDocs index
Sometimes, you might want to have the ability to control which data passes into the search index
@@ -388,38 +319,3 @@ export const SearchModal = ({ toggleModal }: { toggleModal: () => void }) => (
```
There are other more specific search results layout components that also accept result item extensions, check their documentation: [SearchResultList](https://backstage.io/storybook/?path=/story/plugins-search-searchresultlist--with-result-item-extensions) and [SearchResultGroup](https://backstage.io/storybook/?path=/story/plugins-search-searchresultgroup--with-result-item-extensions).
-
-## How to migrate your backend installation to use Search together with the new backend system
-
-Recently, the Backstage maintainers [announced the new Backend System](https://backstage.io/blog/2023/02/15/backend-system-alpha). The search plugins are now migrated to support the new backend system. In this guide you will learn how to update your backend set up.
-
-In "packages/backend/index.ts", install the search plugin [1], the search engine [2], and the search collators/decorators modules [3]:
-
-```ts
-const backend = createBackend();
-// [1] adding the search plugin to the backend
-backend.add(import('@backstage/plugin-search-backend/alpha'));
-// [2] (optional) the default search engine is Lunr, if you want to extend the search backend with another search engine.
-backend.add(
- import('@backstage/plugin-search-backend-module-elasticsearch/alpha'),
-);
-// [3] extending search with collator modules to start index documents, take in optional schedule parameters.
-backend.add(import('@backstage/plugin-search-backend-module-catalog/alpha'));
-backend.add(import('@backstage/plugin-search-backend-module-techdocs/alpha'));
-backend.add(import('@backstage/plugin-search-backend-module-explore/alpha'));
-
-backend.start();
-```
-
-To create your own collators/decorators modules, please use the [searchModuleCatalogCollator](https://github.com/backstage/backstage/blob/d7f955f300893f50c4882ea8f5c09aa42dfaacfd/plugins/search-backend-module-catalog/src/alpha.ts#L49) as an example, we recommend that modules are separated by plugin packages (e.g. `search-backend-module-`). You can also find the available search engines and collator/decorator modules documentation in the Alpha API reports:
-
-**Search engine modules**
-
-- Postgres [module](https://github.com/backstage/backstage/blob/d7f955f300893f50c4882ea8f5c09aa42dfaacfd/plugins/search-backend-module-pg/alpha-api-report.md);
-- Elasticsearch [module](https://github.com/backstage/backstage/blob/d7f955f300893f50c4882ea8f5c09aa42dfaacfd/plugins/search-backend-module-elasticsearch/alpha-api-report.md).
-
-**Search collator/decorator modules**
-
-- Catalog [module](https://github.com/backstage/backstage/blob/d7f955f300893f50c4882ea8f5c09aa42dfaacfd/plugins/search-backend-module-catalog/alpha-api-report.md);
-- Explore [module](https://github.com/backstage/backstage/blob/d7f955f300893f50c4882ea8f5c09aa42dfaacfd/plugins/search-backend-module-explore/alpha-api-report.md);
-- TechDocs [module](https://github.com/backstage/backstage/blob/d7f955f300893f50c4882ea8f5c09aa42dfaacfd/plugins/search-backend-module-techdocs/alpha-api-report.md).
diff --git a/docs/features/search/search-engines.md b/docs/features/search/search-engines.md
index 86b6244fb6..f768a9bde8 100644
--- a/docs/features/search/search-engines.md
+++ b/docs/features/search/search-engines.md
@@ -4,34 +4,31 @@ title: Search Engines
description: Choosing and configuring your search engine for Backstage
---
-Backstage supports 3 search engines by default, an in-memory engine called Lunr,
-Elasticsearch and Postgres. You can configure your own search engines by
-implementing the provided interface as mentioned in the
-[search backend documentation.](./getting-started.md#Backend)
-
-Provided search engine implementations have their own way of constructing
-queries, which may be something you want to modify. Alterations to the querying
-logic of a search engine can be made by providing your own implementation of a
-QueryTranslator interface. This modification can be done without touching
-provided search engines by using the exposed setter to set the modified query
-translator into the instance.
-
-```typescript
-const searchEngine = new LunrSearchEngine({ logger: env.logger });
-searchEngine.setTranslator(new MyNewAndBetterQueryTranslator());
-```
+Backstage supports 3 search engines by default, an in-memory engine called [Lunr](#lunr), [Postgres](#postgres)
+and [Elasticsearch](#elasticsearch).
## Lunr
-Lunr search engine is enabled by default for your backstage instance if you have
-not done additional changes to the scaffolded app.
+Lunr search engine is enabled by default for your Backstage instance if you have not done additional changes to the scaffolded app.
-Lunr can be instantiated like this:
+As Lunr is built into the Search backend plugin it can be added like this:
-```typescript
-// app/backend/src/plugins/search.ts
-const searchEngine = new LunrSearchEngine({ logger: env.logger });
-const indexBuilder = new IndexBuilder({ logger: env.logger, searchEngine });
+```bash title="From your Backstage root directory"
+yarn --cwd packages/backend add @backstage/plugin-search-backend
+```
+
+Then add the following line:
+
+```ts title="packages/backend/src/index.ts"
+const backend = createBackend();
+
+// Other plugins...
+
+/* highlight-add-start */
+backend.add(import('@backstage/plugin-search-backend/alpha'));
+/* highlight-add-end */
+
+backend.start();
```
:::note Note
@@ -45,34 +42,39 @@ other search engines instead.
## Postgres
-The Postgres based search engine only requires that postgres being configured as
+The Postgres based search engine only requires that Postgres being configured as
the database engine for Backstage. Therefore it targets setups that want to
avoid maintaining another external service like Elasticsearch. The search
provides decent results and performs well with ten thousands of indexed
-documents. The connection to postgres is established via the database manager
+documents. The connection to Postgres is established via the database manager
also used by other plugins.
> **Important**: The search plugin requires at least Postgres 12!
-To use the `PgSearchEngine`, make sure that you have a Postgres database
-configured and make the following changes to your backend:
+First we need to add the plugin:
-1. Add a dependency on `@backstage/plugin-search-backend-module-pg` to your
- backend's `package.json`.
-2. Initialize the search engine. It is recommended to initialize it with a
- fallback to the lunr search engine if you are running Backstage for
- development locally with SQLite:
-
-```typescript
-// In packages/backend/src/plugins/search.ts
-
-// Initialize a connection to a search engine.
-const searchEngine = (await PgSearchEngine.supported(env.database))
- ? await PgSearchEngine.fromConfig(env.config, { database: env.database })
- : new LunrSearchEngine({ logger: env.logger });
+```bash title="From your Backstage root directory"
+yarn --cwd packages/backend add @backstage/plugin-search-backend-module-pg
```
-## Optional Configuration
+Then add the following line:
+
+```ts title="packages/backend/src/index.ts"
+const backend = createBackend();
+
+// Other plugins...
+
+// search plugin
+backend.add(import('@backstage/plugin-search-backend/alpha'));
+
+/* highlight-add-start */
+backend.add(import('@backstage/plugin-search-backend-module-pg/alpha'));
+/* highlight-add-end */
+
+backend.start();
+```
+
+### Optional Configuration
The following is an example of the optional configuration that can be applied when using Postgres as the search backend. Currently this is mostly for just the highlight feature:
@@ -106,19 +108,32 @@ Backstage supports Elasticsearch (and OpenSearch) search engine connections,
indexing and querying out of the box. Available configuration options enable
usage of either AWS or Elastic.co hosted solutions, or a custom self-hosted solution.
-Similarly to Lunr above, Elasticsearch can be set up like this:
+Similarly to Postgres above, Elasticsearch can be set up as follows.
-```typescript
-// app/backend/src/plugins/search.ts
-const searchEngine = await ElasticSearchSearchEngine.fromConfig({
- logger: env.logger,
- config: env.config,
-});
-const indexBuilder = new IndexBuilder({ logger: env.logger, searchEngine });
+First we need to add the plugin:
+
+```bash title="From your Backstage root directory"
+yarn --cwd packages/backend add @backstage/plugin-search-backend-module-elasticsearch
```
-For the engine to be available, your backend package needs a dependency on
-package `@backstage/plugin-search-backend-module-elasticsearch`.
+Then add the following line:
+
+```ts title="packages/backend/src/index.ts"
+const backend = createBackend();
+
+// Other plugins...
+
+// search plugin
+backend.add(import('@backstage/plugin-search-backend/alpha'));
+
+/* highlight-add-start */
+backend.add(
+ import('@backstage/plugin-search-backend-module-elasticsearch/alpha'),
+);
+/* highlight-add-end */
+
+backend.start();
+```
Elasticsearch needs some additional configuration before it is ready to use
within your instance. The configuration options are documented in the
@@ -126,67 +141,12 @@ within your instance. The configuration options are documented in the
The underlying functionality uses either the official Elasticsearch client
version 7.x (meaning that Elasticsearch version 7 is the only one confirmed to
-be supported), or the OpenSearch client, when the `aws` or `opensearch `provider
+be supported), or the OpenSearch client, when the `aws` or `opensearch` provider
is configured.
-Should you need to create your own bespoke search experiences that require more
-than just a query translator (such as faceted search or Relay pagination), you
-can access the configuration of the search engine in order to create new
-Elasticsearch clients. The version of the client need not be the same as one
-used internally by the Elasticsearch engine plugin. For example:
+### Example configurations
-```typescript
-import { isOpenSearchCompatible } from '@backstage/plugin-search-backend-module-elasticsearch';
-import { Client as ElasticClient } from '@elastic/elasticsearch';
-import { Client as OpenSearchClient } from '@opensearch-project/opensearch';
-
-// Return an Elasticsearch client
-const esClient = searchEngine.newClient(options => {
- if (!isOpenSearchCompatible(options)) {
- return new ElasticClient(options);
- }
-
- throw new Error('Incompatible options');
-});
-
-// Return an OpenSearch client
-const osClient = searchEngine.newClient(options => {
- if (isOpenSearchCompatible(options)) {
- return new OpenSearchClient(options);
- }
-
- throw new Error('Incompatible options');
-});
-```
-
-#### Set custom index template
-
-The Elasticsearch engine gives you the ability to set a custom index template if needed.
-
-> Index templates define settings, mappings, and aliases that can be applied automatically to new indices.
-
-```typescript
-// app/backend/src/plugins/search.ts
-const searchEngine = await ElasticSearchSearchEngine.initialize({
- logger: env.logger,
- config: env.config,
-});
-
-searchEngine.setIndexTemplate({
- name: '',
- body: {
- index_patterns: [''],
- template: {
- mappings: {},
- settings: {},
- },
- },
-});
-```
-
-## Example configurations
-
-### AWS
+#### AWS
Using AWS hosted Elasticsearch the only configuration option needed is the URL
to the Elasticsearch service. The implementation assumes that environment
@@ -201,7 +161,7 @@ search:
node: https://my-backstage-search-asdfqwerty.eu-west-1.es.amazonaws.com
```
-### Elastic.co
+#### Elastic.co
Elastic Cloud hosted Elasticsearch uses a Cloud ID to determine the instance of
hosted Elasticsearch to connect to. Additionally, username and password needs to
@@ -218,7 +178,7 @@ search:
password: changeme
```
-### OpenSearch
+#### OpenSearch
OpenSearch can be self hosted for example with the [official docker image](https://hub.docker.com/r/opensearchproject/opensearch). The configuration requires only the node and authentication.
@@ -232,7 +192,7 @@ search:
password: changeme
```
-### Others
+#### Others
Other Elasticsearch instances can be connected to by using standard
Elasticsearch authentication methods and exposed URL, provided that the cluster
@@ -242,8 +202,6 @@ username/password or an API key. For more information how to create an API key,
see
[Elastic documentation on API keys](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-create-api-key.html).
-#### Configuration examples
-
##### With username and password
```yaml
@@ -273,8 +231,6 @@ you may get an error caused by limited `thread_pool` configuration. ( `429 Too M
In this case you need to decrease the batch size to index the resources to prevent this kind of error. You can easily decrease
or increase the batch size in your `app-config.yaml` using the `batchSize` option provided for Elasticsearch configuration.
-#### Configuration example
-
**Set batch size to 100**
```yaml
diff --git a/docs/features/software-catalog/descriptor-format.md b/docs/features/software-catalog/descriptor-format.md
index 416eb27fbd..57c2283586 100644
--- a/docs/features/software-catalog/descriptor-format.md
+++ b/docs/features/software-catalog/descriptor-format.md
@@ -1243,6 +1243,18 @@ system belongs to, e.g. `artists`. This field is optional.
| --------------------------------------- | ------------------------------------------ | ----------------------------------------------------------------------------- |
| [`Domain`](#kind-domain) (default) | Same as this entity, typically `default` | [`partOf`, and reverse `hasPart`](well-known-relations.md#partof-and-haspart) |
+### `spec.type` [optional]
+
+The type of system. There is currently no enforced set of values for this field,
+so it is left up to the adopting organization to choose a nomenclature that
+matches their catalog hierarchy. This field is optional.
+
+Some common values for this field could be:
+
+- `product`
+- `service`
+- `feature-set`
+
## Kind: Domain
Describes the following entity kind:
@@ -1303,6 +1315,18 @@ which the domain is a part, e.g. `audio`. This field is optional.
| --------------------------------------- | ------------------------------------------ | ----------------------------------------------------------------------------- |
| [`Domain`](#kind-domain) (default) | Same as this entity, typically `default` | [`partOf`, and reverse `hasPart`](well-known-relations.md#partof-and-haspart) |
+### `spec.type` [optional]
+
+The type of domain. There is currently no enforced set of values for this field,
+so it is left up to the adopting organization to choose a nomenclature that
+matches their catalog hierarchy. This field is optional.
+
+Some common values for this field could be:
+
+- `product-area`
+- `product-group`
+- `bundle`
+
## Kind: Location
Describes the following entity kind:
diff --git a/docs/features/software-catalog/system-model.md b/docs/features/software-catalog/system-model.md
index ee7270a960..b93dde37d2 100644
--- a/docs/features/software-catalog/system-model.md
+++ b/docs/features/software-catalog/system-model.md
@@ -50,7 +50,7 @@ components need to be in a known machine-readable format so we can build further
tooling and analysis on top.
APIs have a visibility: they are either public (making them available for any
-other component to consume), restricted (only available to an allowlisted set of
+other component to consume), restricted (only available to an allowed set of
consumers), or private (only available within their system). As public APIs are
going to be the primary way interaction between components, Backstage supports
documenting, indexing and searching all APIs so we can browse them as
diff --git a/docs/features/techdocs/configuration.md b/docs/features/techdocs/configuration.md
index a861a50c87..05f184e90f 100644
--- a/docs/features/techdocs/configuration.md
+++ b/docs/features/techdocs/configuration.md
@@ -20,7 +20,7 @@ techdocs:
# spin up the techdocs-container docker image or to run mkdocs locally (assuming all the dependencies are taken care of).
# You want to change this to 'local' if you are running Backstage using your own custom Docker setup and want to avoid running
# into Docker in Docker situation. Read more here
- # https://backstage.io/docs/features/techdocs/getting-started#disable-docker-in-docker-situation-optional
+ # https://backstage.io/docs/features/techdocs/getting-started/#disabling-docker-in-docker-situation-optional
runIn: 'docker'
@@ -203,7 +203,7 @@ techdocs:
# (Optional) The time (in milliseconds) that the TechDocs backend will wait
# for a cache service to respond before continuing on as though the cached
- # object was not found (e.g. when the cache sercice is unavailable). The
+ # object was not found (e.g. when the cache service is unavailable). The
# default value is 1000
readTimeout: 500
```
diff --git a/docs/features/techdocs/how-to-guides.md b/docs/features/techdocs/how-to-guides.md
index 3a7cfd97bb..59198e919b 100644
--- a/docs/features/techdocs/how-to-guides.md
+++ b/docs/features/techdocs/how-to-guides.md
@@ -841,3 +841,8 @@ metadata:
annotations:
backstage.io/techdocs-entity: system:default/example
```
+
+## How to resolve broken links from moved or renamed pages in your documentation site
+
+TechDocs supports using the [mkdocs-redirects](https://github.com/mkdocs/mkdocs-redirects/tree/master) plugin to create a redirect map for any TechDocs site. This allows broken links from renamed or moved pages in your site to be redirected to their specified replacement.
+TechDocs will notify the user that the page they are trying to access is no longer maintained. Then, they will be redirected. External site redirects are not supported. If an external redirect is provided, the user will instead be redirected to the index page of the documentation site.
diff --git a/docs/frontend-system/architecture/01-index.md b/docs/frontend-system/architecture/00-index.md
similarity index 100%
rename from docs/frontend-system/architecture/01-index.md
rename to docs/frontend-system/architecture/00-index.md
diff --git a/docs/frontend-system/architecture/04-plugins.md b/docs/frontend-system/architecture/04-plugins.md
deleted file mode 100644
index 042d4fbc36..0000000000
--- a/docs/frontend-system/architecture/04-plugins.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-id: plugins
-title: Frontend Plugins
-sidebar_label: Plugins
-# prettier-ignore
-description: Frontend plugins
----
-
-> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
-
-## Introduction
-
-
-
-## Creating a Plugin
-
-
-
-```ts
-export const myPlugin = createPlugin({
- id: 'my-plugin',
-});
-```
-
-
-
-### Plugin ID
-
-
-
-### Plugin Extensions
-
-
-
-### Plugin Routes
-
-
-
-### Plugin External Routes
-
-
-
-### Plugin Feature Flags
-
-
-
-## Installing a Plugin in an App
-
-
diff --git a/docs/frontend-system/architecture/05-extension-overrides.md b/docs/frontend-system/architecture/05-extension-overrides.md
deleted file mode 100644
index 41702e6823..0000000000
--- a/docs/frontend-system/architecture/05-extension-overrides.md
+++ /dev/null
@@ -1,170 +0,0 @@
----
-id: extension-overrides
-title: Frontend Extension Overrides
-sidebar_label: Extension Overrides
-# prettier-ignore
-description: Frontend extension overrides
----
-
-> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
-
-## Introduction
-
-An extension override is a building block of the frontend system that allows you to programmatically override app or plugin extensions anywhere in your application. Since the entire application is built mostly out of extensions from the bottom up, this is a powerful feature. You can use it for example to provide your own app root layout, to replace the implementation of a Utility API with a custom one, to override how the catalog page renders itself, and much more.
-
-In general, most features should have a good level of customization built into them, so that users do not have to leverage extension overrides to achieve common goals. A well written feature often has [configuration](../../conf/) settings, or uses extension inputs for extensibility where applicable. An example of this is the search plugin, which allows you to provide result renderers as inputs rather than replacing the result page wholesale just to tweak how results are shown. Adopters should take advantage of those when possible, and only use extension overrides when it's necessary to entirely replace the extension. Check the respective extension documentation for guidance.
-
-## Override App Extensions
-
-In order to override an app extension, you must create a new extension and add it to the list of overridden features. The steps are: create your extension overrides and use them in Backstage.
-
-### Example
-
-In the example below, we create a file that exports custom extensions for the app's `light` and `dark` themes:
-
-```tsx title="packages/app/src/themes.tsx"
-import {
- createThemeExtension,
- createExtensionOverrides,
-} from '@backstage/frontend-plugin-api';
-import { apertureThemes } from './themes';
-import { ApertureLightIcon, ApertureDarkIcon } from './icons';
-
-// Creating a light theme extension
-const apertureLightTheme = createThemeExtension({
- // highlight-start
- namespace: 'app',
- name: 'light',
- // highlight-end
- title: 'Aperture Light Theme',
- variant: 'light',
- icon: ,
- Provider: ({ children }) => (
-
- ),
-});
-
-// Creating a dark theme extension
-const apertureDarkTheme = createThemeExtension({
- // highlight-start
- namespace: 'app',
- name: 'dark',
- // highlight-end
- title: 'Aperture Dark Theme',
- variant: 'dark',
- icon: ,
- Provider: ({ children }) => (
-
- ),
-});
-
-// Creating an extension overrides preset
-export default createExtensionOverrides({
- extensions: [apertureLightTheme, apertureDarkTheme],
-});
-```
-
-Note that we declare `namespace` as `'app'` while creating the themes, so the system knows we are overriding app extensions. Additionally, to specifically override the `light` and `dark` theme extensions, we set the `name` option to `light` and `dark`. Therefore, to override app theme extensions, we ensure that the extension `namespace` and `name` match those of the default app theme extension definitions.
-
-Now we are able to use the overrides in a Backstage app:
-
-```tsx title="packages/app/src/App.tsx"
-import { createApp } from '@backstage/frontend-app-api';
-import themeOverrides from './themes';
-
-const app = createApp({
- // highlight-next-line
- features: [themeOverrides],
-});
-
-export default app.createRoot().
-```
-
-If the plugin you want to change is internal to your company or you just want to replace one of the application's core extensions, you can decide to store the overrides code directly in the app package or extract them to a separate package.
-
-Note that it can still be a good idea to split your overrides out into separate packages in large projects. But it's up to you to decide how to group the extensions into extension overrides.
-
-## Override Plugin Extensions
-
-To override an extension that is provided by a plugin, you need to provide a new extension that has the same ID as the existing extension. That is, all kind, namespace, and name options must match the extension you want to replace. This means that you typically need to provide an explicit `namespace` when overriding extensions from a plugin.
-
-:::info
-We recommend that plugin developers share the extension IDs in their plugin documentation, but usually you can infer the ID by following the [naming patterns](./08-naming-patterns.md) documentation.
-:::
-
-### Example
-
-Imagine you have a plugin with the ID `'search'`, and the plugin provides a page extension that you want to fully override with your own custom component. To do so, you need to create your page extension with an explicit `namespace` option that matches that of the plugin that you want to override, in this case `'search'`. If the existing extension also has an explicit `name` you'd need to set the `name` of your override extension to the same value as well.
-
-```tsx title="packages/app/src/search.tsx"
-import {
- createPageExtension,
- createExtensionOverrides,
-} from '@backstage/frontend-plugin-api';
-
-// Creating a custom search page extension
-const customSearchPage = createPageExtension({
- // highlight-next-line
- namespace: 'search',
- // Omitting name since it is the index plugin page
- defaultPath: '/search',
- loader: () => import('./SearchPage').then(m => m.),
-});
-
-export default createExtensionOverrides({
- extensions: [customSearchPage]
-});
-```
-
-Don't forget to configure your overrides in the `createApp` function:
-
-```tsx title="packages/app/src/App.tsx"
-import { createApp } from '@backstage/frontend-app-api';
-import searchOverrides from './search';
-
-const app = createApp({
- // highlight-next-line
- features: [searchOverrides],
-});
-
-export default app.createRoot();
-```
-
-Now let's talk about the last override case, orphan extensions.
-
-## Create Standalone Extensions
-
-Sometimes you just need to quickly create a new extension and not overwrite an app extension or plugin. You can also use overrides to create extensions, but remember that if you want to make this extension available for installation by other users, we recommend providing it via a plugin in a separate package.
-
-### Example
-
-Imagine you want to create a page that is currently only used by your application, like an Institutional page, for example. You can use overrides to extend the Backstage app to render it. To do so, simply create a page extension and pass it to the app as an override:
-
-```tsx title="packages/app/src/App.tsx"
-import { createApp } from '@backstage/frontend-app-api';
-import {
- createPageExtension,
- createExtensionOverrides,
-} from '@backstage/frontend-plugin-api';
-
-const app = createApp({
- features: [
- createExtensionOverrides({
- extensions: [
- // highlight-start
- createPageExtension({
- name: 'institutional',
- defaultPath: '/institutional',
- loader: () =>
- import('./institutional').then(m => ),
- }),
- // highlight-end
- ],
- }),
- ],
-});
-
-export default app.createRoot();
-```
-
-Note that we are omitting `namespace` when creating the page extension. When we omit `namespace`, we are telling the system the new extension is standalone and not an application or plugin extension!
diff --git a/docs/frontend-system/architecture/02-app.md b/docs/frontend-system/architecture/10-app.md
similarity index 95%
rename from docs/frontend-system/architecture/02-app.md
rename to docs/frontend-system/architecture/10-app.md
index 3b839d4232..532971d124 100644
--- a/docs/frontend-system/architecture/02-app.md
+++ b/docs/frontend-system/architecture/10-app.md
@@ -33,13 +33,13 @@ const rootEl = document.getElementById('root')!;
ReactDOM.createRoot(rootEl).render(app);
```
-We call `createApp` to create a new app instance, which is responsible for wiring together all of the features that we provide to the app. It also provides a set of built-in [Extensions](./03-extensions.md) that help build out the foundations of the app, as well as defaults for many other systems such as [Utility API](./06-utility-apis.md) implementations, components, icons, themes, and how to load configuration. No real work is done at the point of creating the app though, it's all deferred to the rendering of the element returned from `app.createRoot()`.
+We call `createApp` to create a new app instance, which is responsible for wiring together all of the features that we provide to the app. It also provides a set of built-in [Extensions](./20-extensions.md) that help build out the foundations of the app, as well as defaults for many other systems such as [Utility API](./33-utility-apis.md) implementations, components, icons, themes, and how to load configuration. No real work is done at the point of creating the app though, it's all deferred to the rendering of the element returned from `app.createRoot()`.
-It is possible to explicitly install features when creating the app, although typically these will instead be discovered automatically which we'll explore later on. Nevertheless these features are what build out the actual functionality of the app by providing [Extensions](./03-extensions.md). These extensions are wired together by the app into a tree structure known as the app extension tree. Each node in this tree receives data from its child nodes, and passes along data to its parent. The following diagram illustrates the shape of a small app extension tree.
+It is possible to explicitly install features when creating the app, although typically these will instead be discovered automatically which we'll explore later on. Nevertheless these features are what build out the actual functionality of the app by providing [Extensions](./20-extensions.md). These extensions are wired together by the app into a tree structure known as the app extension tree. Each node in this tree receives data from its child nodes, and passes along data to its parent. The following diagram illustrates the shape of a small app extension tree.

-Each node in this tree is an extension with a parent node and children. The colored shapes represent extension data inputs and output, where each color is one unique type of data. You can see that there are both extensions that output data that is ignored by the parent, as well as extensions that accept inputs but do not have any children. There are a couple of different tools at your disposal when creating and extension that lets you define different requirements for your inputs and output, which we will cover in greater details in the [Extensions](./03-extensions.md) section.
+Each node in this tree is an extension with a parent node and children. The colored shapes represent extension data inputs and output, where each color is one unique type of data. You can see that there are both extensions that output data that is ignored by the parent, as well as extensions that accept inputs but do not have any children. There are a couple of different tools at your disposal when creating and extension that lets you define different requirements for your inputs and output, which we will cover in greater details in the [Extensions](./20-extensions.md) section.
A common type of data that is shared between extensions is React elements and components. These can in turn be rendered by each other in their own React components, which ends up forming a parallel tree of React components that is similar in shape to that of the app extension tree. At the top of the app extension tree is a built-in root extension that among other things outputs a React element. This element also ends up being the root of the parallel React tree, and is rendered by the React element returned by `app.createRoot()`.
diff --git a/docs/frontend-system/architecture/15-plugins.md b/docs/frontend-system/architecture/15-plugins.md
new file mode 100644
index 0000000000..a54573427d
--- /dev/null
+++ b/docs/frontend-system/architecture/15-plugins.md
@@ -0,0 +1,91 @@
+---
+id: plugins
+title: Frontend Plugins
+sidebar_label: Plugins
+# prettier-ignore
+description: Frontend plugins
+---
+
+> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
+
+## Introduction
+
+Frontend plugins are a foundational building block in Backstage and the frontend system. They are used to encapsulate and provide functionality for a Backstage app, such as new pages, navigational elements, and APIs; as well as extensions and features for other plugins, such as entity page cards and content for the Software Catalog, or result list items for the search plugin.
+
+Each plugin is typically shipped in a separate NPM package, whether that's a published package, or just in the local workspace. The plugin instance should always the `default` export of the package, either via the main entry-point or the `/alpha` sub-path export. Each plugin package is limited to exporting a single plugin instance. In a local workspace you could use a different structure if preferred, but this is considered a non-standard layout and should be avoided in published packages.
+
+## Creating a Plugin
+
+Frontend plugin instances are created with the `createFrontendPlugin` function, which is provided by the `@backstage/frontend-plugin-api` package. It takes a single options object that provides all of the necessary configuration for the plugin. In particular you will want to provide [extensions](./20-extensions.md) for your plugin, as that is the way that you can provide new functionality to the app.
+
+```tsx
+// This creates a new extension, see "Extension Blueprints" documentation for more details
+const myPage = PageBlueprint.make({
+ params: {
+ defaultPath: '/my-page',
+ loader: () => import('./MyPage').then(m => ),
+ },
+});
+
+export default createFrontendPlugin({
+ id: 'my-plugin',
+ extensions: [myPage],
+});
+```
+
+### `pluginId` option
+
+Each plugin needs an ID, which is used to uniquely identify the plugin within an entire Backstage system. The ID does not have to be globally unique across all of the NPM ecosystem, although you generally want to strive for that. It is not possible to install multiple plugins with the same ID in a single Backstage app.
+
+The plugin ID should generally be part of the of the package name and use kebab-case. See both the [frontend naming patterns section](./50-naming-patterns.md), as well as the [package metadata section](../../tooling/package-metadata.md#name) for more information.
+
+### `extensions` option
+
+These are the [extensions](./20-extensions.md) that the plugin provides to the app. Note that you should not export any of these extensions separately from the plugin package, as they can already by accessed via the `getExtension` method of the plugin instance using the extension ID.
+
+The extensions that you provide to a plugin will have their `namespace` set to the plugin ID by default. For example, if you create an extension using the `PageBlueprint` without any particular naming options and install that via a plugin with the ID `my-plugin`, the final extension ID will be `page:my-plugin`. You can read more about how this works in the [extension structure documentation](./20-extensions.md#extension-structure).
+
+### `routes` and `externalRoutes` options
+
+These are the routes that the plugin exposes to the app. The `routes` option declares all of the target routes that your plugin provides, i.e. routes that other plugins link to. The `externalRoutes` option instead declares all the outgoing routes, i.e. routes that your plugins links to, which you can bind to the `routes` of other plugins. See the [routes documentation](./36-routes.md) for more information how to set up cross-plugin navigation.
+
+### `featureFlags` option
+
+This is a list of feature flag declarations that your plugin provides to the app. This makes sure that the feature flags are correctly registered and can be toggled in the app. To read a feature flag you can use the feature flags [Utility API](../architecture/33-utility-apis.md), accessible via `featureFlagsApiRef`.
+
+## Installing a Plugin in an App
+
+A plugin instance is considered a frontend feature and can be installed directly in any Backstage frontend app. See the [app documentation](./10-app.md) for more information about the different ways in which you can install new features in an app.
+
+## Overriding a Plugin
+
+A plugin might not always behave exactly the way you want. It could be that you want to remove particular extensions, decorate them a bit, replace them with your own, or simply add new ones. Regardless of your exact use-case, you can use the `plugin.withOverrides` method to create a new copy of the plugin with the desired changes. When doing so you can also access the original extensions provided by the plugin, and use the [extension override](./25-extension-overrides.md) API to make changes to individual extensions:
+
+```tsx
+import plugin from '@backstage/plugin-catalog';
+
+export default plugin.withOverrides({
+ // These overrides are merged with the original extensions
+ extensions: [
+ // Override the catalog nav item to use a custom icon
+ plugin.getExtension('nav-item:catalog').override({
+ factory: origFactory => [
+ NavItemBlueprint.dataRefs.target({
+ ...origFactory().get(NavItemBlueprint.dataRefs.target),
+ icon: CustomCatalogIcon,
+ }),
+ ],
+ }),
+ // Override the catalog index page with a completely custom implementation
+ PageBlueprint.make({
+ params: {
+ defaultPath: '/catalog',
+ routeRef: plugin.routes.catalogIndex,
+ loader: () => import('./CustomCatalogIndexPage').then(m => ),
+ },
+ }),
+ ],
+});
+```
+
+You can keep the plugin override in your app package, but it can often be a good idea to separate it out into its own package, especially if the overrides are complex or you want distinct ownership of the override. For example, if you are overriding the `@backstage/plugin-catalog` plugin, you might create a new package called `@internal/plugin-catalog` at `plugins/catalog` in your workspace, which exports the overridden plugin instance.
diff --git a/docs/frontend-system/architecture/03-extensions.md b/docs/frontend-system/architecture/20-extensions.md
similarity index 66%
rename from docs/frontend-system/architecture/03-extensions.md
rename to docs/frontend-system/architecture/20-extensions.md
index 2f3daba6f8..02f4ba9d05 100644
--- a/docs/frontend-system/architecture/03-extensions.md
+++ b/docs/frontend-system/architecture/20-extensions.md
@@ -8,7 +8,7 @@ description: Frontend extensions
> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
-As mentioned in the [previous section](./02-app.md), Backstage apps are built up from a tree of extensions. This section will go into more detail about what extensions are, how to create and use them, and how to create your own extensibility patterns.
+As mentioned in the [previous section](./10-app.md), Backstage apps are built up from a tree of extensions. This section will go into more detail about what extensions are, how to create and use them, and how to create your own extensibility patterns.
## Extension Structure
@@ -18,12 +18,12 @@ Each extensions has a number of different properties that define how it behaves
### ID
-
-
The ID of an extension is used to uniquely identity it, and it should ideally be unique across the entire Backstage ecosystem. For each frontend app instance there can only be a single extension for any given ID. Installing multiple extensions with the same ID will either result in an error or one of the extensions will override the others. The ID is also used to reference the extensions from other extensions, in configuration, and in other places such as developer tools and analytics.
+When creating an extension you do not provide the ID directly. Instead, you indirectly or directly provide the kind, namespace, and name parts that make up the ID. The kind is always provided by the [extension blueprint](./23-extension-blueprints.md), the only exception is if you use [`createExtension`](#creating-an-extensions) directly. Any extension that is provided by a plugin will by default have its namespace set to the plugin ID, so you generally only need to provide an explicit namespace if you want to override an existing extension. The name is also optional, and primarily used to distinguish between multiple extensions of the same kind and namespace. If a plugin doesn't need to distinguish between different extensions of the same kind, the name can be omitted.
+
+The extension ID will be constructed using the pattern `[:][][/][]`, where the separating `/` is only present if both a namespace and name are defined.
+
### Output
The output of an extension is the data that it provides to its parent extension, and ultimately its contribution to the app. The output itself comes in the form of a collection of arbitrary values, anything that can be represented as a TypeScript type. However, each individual output value must be associated with a shared reference known as an extension data reference. You must also use these same references to be able to access individual output values of an extension.
@@ -32,7 +32,7 @@ The output of an extension is the data that it provides to its parent extension,
The inputs of an extension define the data that it received from its children. Each extension can have multiple different inputs identified by an input name. These inputs each have their own set of data that they expect, which is defined as a collection of extension data references. An extension will only have access to the data that it has explicitly requested from each input.
-### Attachment Point
+### Attachment point
The attachment point of an extension decides where in the app extension tree it will be located. It is defined by the ID of the parent extension, as well as the name of the input to attach to. Through the attachment point the extension will share its own output as inputs to the parent extension. An extension can only be attached to an input that matches its own output, it is an error to try to attach an extension to an input the requires data that the extension does not provide in its output.
@@ -44,7 +44,7 @@ Each extension in the app can be disabled, meaning it will not be instantiated a
The ordering of extensions is sometimes very important, as it may for example affect in which order they show up in the UI. When an extension is toggled from disabled to enabled through configuration it resets the ordering of the extension, pushing it to the end of the list. It is generally recommended to leave extensions as disabled by default if their order is important, allowing for the order in which their are enabled in the configuration to determine their order in the app.
-### Configuration & Configuration Schema
+### Configuration & configuration schema
Each extension can define a configuration schema that describes the configuration that it accepts. This schema is used to validate the configuration provided by integrators, but also to fill in default configuration values. The configuration itself is provided by integrators in order to customize the extension. It is not possible to provide a default configuration of an extension, this must instead be done through defaults in the configuration schema. This allows for a simpler configuration logic where multiple configurations of the same extension completely replace each other rather than being merged.
@@ -54,7 +54,7 @@ The extension factory is the implementation of the extension itself. It is a fun
Extension factories should be lean and not do any heavy lifting or async work, as they are called during the initialization of the app. For example, if you need to do an expensive computation to generate your output, then prefer outputting a callback that does the computation instead. This allows the parent extension to defer the computation for later so that you avoid blocking the app startup.
-## Creating an Extensions
+## Creating an extension
Extensions are created using the `createExtension` function from `@backstage/frontend-plugin-api`. At minimum you need to provide an ID, attachment point, output definition, and a factory function. The following example shows the creation of a minimal extension:
@@ -64,28 +64,22 @@ const extension = createExtension({
// This is the attachment point, `id` is the ID of the parent extension,
// while `input` is the name of the input to attach to.
attachTo: { id: 'my-parent', input: 'content' },
- // The output map defines the outputs of the extension. The object keys
- // are only used internally to map the outputs of the factory and do
- // not need to match the keys of the input.
- output: {
- element: coreExtensionData.reactElement,
- },
+ // The output option defines the allowed and required outputs of the extension factory.
+ output: [coreExtensionData.reactElement],
// This factory is called to instantiate the extensions and produce its output.
factory() {
- return {
- element:
Hello World
,
- };
+ return [coreExtensionData.reactElement(
Hello World
)];
},
});
```
-Note that while the `createExtension` is public API and used in many places, it is not typically what you use when building plugins and features. Instead there are many extension creator functions exported by both the core APIs and plugins that make it easier to create extensions for more specific usages.
+Note that while the `createExtension` function is public API and used in many places, it is not typically what you use when building plugins and features. Instead there are many [extension blueprints](./23-extension-blueprints.md) exported by both the core APIs and plugins that make it easier to create extensions for more specific usages.
-## Extension Data
+## Extension data
Communication between extensions happens in one direction, from one child extension through the attachment point to its parent. The child extension outputs data which is then passed as inputs to the parent extension. This data is called Extension Data, where the shape of each individual piece of data is described by an Extension Data Reference. These references are created separately from the extensions themselves, and can be shared across multiple different kinds of extensions. Each reference consists of an ID and a TypeScript type that the data needs to conform to, and represents one type of data that can be shared between extensions.
-### Extension Data References
+### Extension data references
To create a new extension data reference to represent a type of shared extension data you use the `createExtensionDataRef` function. When defining a new reference you need to provide an ID and a TypeScript type, for example:
@@ -101,59 +95,53 @@ The `ExtensionDataRef` can then be used to describe an output property of the ex
```tsx
const extension = createExtension({
// ...
- output: {
- element: reactElementExtensionDataRef,
- },
+ output: [reactElementExtensionDataRef],
factory() {
- return {
- element:
Hello World
,
- };
+ return [reactElementExtensionDataRef(
Hello World
)];
},
});
```
-### Extension Data Uniqueness
+### Extension data uniqueness
-Note that the key used in the output map, in this case `element`, is only used internally within the definition of the extension itself. That actual identifier for the data when consumed by other extensions is the ID of the reference, in this case [`core.reactElement`](https://github.com/backstage/backstage/blob/916da47e8abdb880877daa18881eb8fdbb33e70a/packages/frontend-plugin-api/src/wiring/coreExtensionData.ts#L23). This means that you can not output multiple different values for the same extension data reference, as they would conflict with each other. That in turn makes overly generic extension data references a bad idea, for example a generic "string" type. Instead create separate references for each type of data that you want to share.
+Note that you are **not** allowed to repeat the same data reference in the outputs, or return multiple values for the same reference. Multiple outputs for the same reference will conflict with each other and cause an error. If you want to output multiple values of the same TypeScript type you should create separate references for each value. That in turn means that overly generic extension data references are a bad idea, for example a generic "string" type. Instead create separate references for each type of data that you want to share.
```tsx
const extension = createExtension({
// ...
- output: {
- // ❌ Bad example - outputting values of same type
- element1: reactElementExtensionDataRef,
- element2: reactElementExtensionDataRef,
- },
+ output: [
+ // ❌ Bad example - duplicate output declaration
+ reactElementExtensionDataRef,
+ reactElementExtensionDataRef,
+ ],
factory() {
- return {
- element1:
Hello World
,
- element2:
Hello World
,
- };
+ return [
+ // ❌ Bad example - duplicate output values
+ reactElementExtensionDataRef(
Hello
),
+ reactElementExtensionDataRef(
World
),
+ ];
},
});
```
-### Core Extension Data
+### Core extension data
We provide default `coreExtensionData`, which provides commonly used `ExtensionDataRef`s - e.g. for `React.JSX.Element` and `RouteRef`. They can be used when creating your own extension. For example, the React Element extension data that we defined above is already provided as `coreExtensionData.reactElement`.
For a full list and explanations of all types of core extension data, see the [core extension data reference](../building-plugins/04-built-in-data-refs.md).
-### Optional Extension Data
+### Optional extension data
By default all extension data is required, meaning that the extension factory must provide a value for each output. However, it is possible to make extension data optional by calling the `.optional()` method. This makes it optional for the factory function to return a value as part of its output. When calling the `.optional()` method you create a new copy of the extension data reference, it does not mutate the existing reference.
```tsx
const extension = createExtension({
// ...
- output: {
- element: coreExtensionData.reactElement.optional(),
- },
+ output: [coreExtensionData.reactElement.optional()],
factory() {
- return {
- element:
- Math.random() < 0.5 ? : undefined,
- };
+ return Math.random() > 0.5
+ ? [coreExtensionData.reactElement(
Hello World
)]
+ : [];
},
});
```
@@ -167,17 +155,19 @@ const navigationExtension = createExtension({
// ...
inputs: {
// [1]: Input
- logo: createExtensionInput(
- {
- element: coreExtensionData.reactElement,
- },
- { singleton: true, optional: true },
- ),
+ logo: createExtensionInput([coreExtensionData.reactElement], {
+ singleton: true,
+ optional: true,
+ }),
},
factory({ inputs }) {
return {
element: (
-
+
),
};
},
@@ -193,10 +183,9 @@ So how can we now attach the output to the parent extension's input? If we think
const navigationItemExtension = createExtension({
// ...
attachTo: { id: 'app/nav', input: 'items' },
+ output: [coreExtensionData.reactElement],
factory() {
- return {
- element: Home,
- };
+ return [coreExtensionData.reactElement(Home)];
},
});
@@ -205,26 +194,22 @@ const navigationExtension = createExtension({
// [2]: Extension `id` will be `app/nav` following the extension naming pattern
namespace: 'app',
name: 'nav',
- output: {
- element: coreExtensionData.reactElement,
- },
+ output: [coreExtensionData.reactElement],
inputs: {
- items: createExtensionInput({
- element: coreExtensionData.reactElement,
- }),
+ items: createExtensionInput([coreExtensionData.reactElement]),
},
factory({ inputs }) {
- return {
- element: (
+ return [
+ coreExtensionData.reactElement(
+ ,
),
- };
+ ];
},
// ...
});
@@ -232,27 +217,27 @@ const navigationExtension = createExtension({
In this case the extension input `items` is an array, where each individual item is an extension that attached itself to the extension inputs of this `id`.
-With the `inputs` not only the `output` of an extensions item is passed to the extension, but also the `node`. However, it is discouraged to consume the `node` here unless needed. If we are looking at the `factory` function from the example above we could access the `node` like the following:
+In addition to being able to access data passed through the input, you also have access to the underlying app `node`. This can be useful if you for example want to get the ID of the attached extension. However, avoid using the `node` unless needed, it is generally better to stick to only consuming the provided data. If we are looking at the `factory` function from the example above we could access the `node` like the following:
```tsx
// ...
factory({ inputs }) {
- return {
- element: (
+ return [
+ coreExtensionData.reactElement(
),
- };
+ ];
},
```
-## Extension Configuration
+## Extension configuration
With the `app-config.yaml` there is already the option to pass configuration to plugins or the app to e.g. define the `baseURL` of your app. For extensions this concept would be limiting as an extension can be independent of the plugin & initiated several times. Therefore we created a possibility to configure each extension individually through config. The extension config schema is created using the [`zod`](https://zod.dev/) library, which in addition to TypeScript type checking also provides runtime validation and coercion. If we continue with the example of the `navigationExtension` and now want it to contain a configurable title, we could make it available like the following:
@@ -262,20 +247,20 @@ const navigationExtension = createExtension({
namespace: 'app',
name: 'nav',
// [3]: Extension `id` will be `app/nav` following the extension naming pattern
- configSchema: createSchemaFromZod(z =>
- z.object({
- title: z.string().default('Sidebar Title'),
- }),
- ),
+ config: {
+ schema: {
+ title: z => z.string().default('Sidebar Title'),
+ },
+ },
factory({ config }) {
- return {
- element: (
+ return [
+ coreExtensionData.reactElement(
+ ,
),
- };
+ ];
},
// ...
});
@@ -293,47 +278,40 @@ app:
title: 'Backstage'
```
-## Extension Creators
+## Extension factory as a generator function
-With creating an extension by using `createExtension(...)` you have the advantage that the extension can be anything in your Backstage application. We realised that this comes with the trade-off of having to repeat boilerplate code for similar building blocks. Here extension creators come into play for covering common building blocks in Backstage like pages using `createPageExtension`, themes using the `createThemeExtension` or items for the navigation using `createNavItemExtension`.
+In all examples so far we have defined the extension factory as a regular function that returns its output in an array. However, the only requirement is that the factory function returns any iterable of extension data values. This means that you can also define the factory function as a generator function, which allows you to yield values one by one. This is particularly useful if you want to conditionally output values.
-If we follow the example from above all items of the navigation have similarities, like they all want to be attached to the same extension with the same input as well as rendering the same navigation item component. Therefore `createExtension` can be abstracted for this use case to `createNavItemExtension` and if we add the extension to the app it will end up in the right place & looks like we expect a navigation item to look.
+For example, this is how we could define an extension where its output depends on the configuration:
```tsx
-export const HomeNavIcon = createNavItemExtension({
- routeRef: routeRefForTheHomePage,
- title: 'Home',
- icon: HomeIcon,
+const exampleExtension = createExtension({
+ // ...
+ config: {
+ schema: {
+ disableIcon: z.boolean().default(false),
+ },
+ },
+ output: [coreExtensionData.reactElement, iconDataRef.optional()],
+ *factory({ config }) {
+ yield coreExtensionData.reactElement(
Hello World
);
+
+ if (!config.disableIcon) {
+ yield iconDataRef();
+ }
+ },
});
```
-### Extension Kind
-
-With the example `HomeNavIcon` will end up on the extension input `items` of the extensions with the id `app/nav`. It raises the question what the `id` of the `HomeNavIcon` itself is. The extension creator for the navigation item has a defined `kind`, which by convention matches the own name. So in this example `createNavItemExtension` sets the kind to `nav-item`.
-
-The `id` of the extension is then build out of `namespace`, `name` & `kind` like the following - where `namespace` & `name` are optional properties that can be passed to the extension creator:
-
-```
-id: kind:namespace/name
-```
-
-For more information on naming of extension refer to the [naming patterns documentation](./08-naming-patterns.md).
-
-### Extension Creators in libraries
-
-Extension creators should be exported from frontend library packages (e.g. `*-react`) rather than plugin packages.
-
-If an extension is only for in-house tweaks, it's okay to put it in the plugin package. But if you want other open source plugins to use it, or you already have a `-react` package, always put extension creators in the `-react` package.
-
-## Extension Boundary
+## Extension boundary
The `ExtensionBoundary` wraps extensions with several React contexts for different purposes
### Suspense
-All React elements rendered by extension creators should be wrapped in the extension boundary. With `Suspense` the extension can than load resources asynchronously with having a loading fallback. It also allows to lazy load the whole extension similar to how plugins are currently lazy loaded in Backstage.
+Most React elements rendered by extensions should be wrapped in the extension boundary. With `Suspense` the extension can than load resources asynchronously with having a loading fallback. It also allows to lazy load the whole extension similar to how plugins are currently lazy loaded in Backstage.
-### Error Boundary
+### Error boundary
Similar to plugins the `ErrorBoundary` for extension allows to pass in a fallback component in case there is an uncaught error inside of the component. With this the error can be isolated & it would prevent the rest of the plugin to crash.
@@ -341,32 +319,21 @@ Similar to plugins the `ErrorBoundary` for extension allows to pass in a fallbac
Analytics information are provided through the `AnalyticsContext`, which will give `extensionId` & `pluginId` as context to analytics event fired inside of the extension. Additionally `RouteTracker` will capture an analytics event for routable extension to inform which extension metadata gets associated with a navigation event when the route navigated to is a gathered `mountPoint`. Whether an extension is routable is inferred from its outputs, but you can also explicitly control this behavior by passing the `routable` prop to `ExtensionBoundary`.
-The `ExtensionBoundary` can be used like the following in an extension creator:
+The `ExtensionBoundary` can be used like the following in an extension:
```tsx
-export function createSomeExtension<
- TConfig extends {},
- TInputs extends AnyExtensionInputMap,
->(options): ExtensionDefinition {
- return createExtension({
- // ...
- factory({ config, inputs, node }) {
- const ExtensionComponent = lazy(() =>
- options
- .loader({ config, inputs })
- .then(element => ({ default: () => element })),
- );
-
- return {
- path: config.path,
- routeRef: options.routeRef,
- element: (
-
-
-
- ),
- };
- },
- });
-}
+const routableExtension = createExtension({
+ // ...
+ factory({ config, inputs, node }) {
+ return [
+ coreExtensionData.path(config.path),
+ coreExtensionData.routeRef(myRouteRef),
+ coreExtensionData.reactElement(
+
+
+ ,
+ ),
+ ];
+ },
+});
```
diff --git a/docs/frontend-system/architecture/23-extension-blueprints.md b/docs/frontend-system/architecture/23-extension-blueprints.md
new file mode 100644
index 0000000000..ee09e7fec6
--- /dev/null
+++ b/docs/frontend-system/architecture/23-extension-blueprints.md
@@ -0,0 +1,142 @@
+---
+id: extension-blueprints
+title: Frontend Extension Blueprints
+sidebar_label: Extensions Blueprints
+# prettier-ignore
+description: Frontend extensions
+---
+
+> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
+
+The `createExtension` function and related APIs is considered a low-level building and fairly advanced building block, and is not typically what you would use when building plugins and features. Instead, the core APIs and plugins provide extension blueprints that makes it easier to create extensions for specific usages. These blueprints accept a number of parameters that is up to each blueprint to define, and then creates a new extension using the provided parameters. New blueprints are created using the `createExtensionBlueprint` function, and are by convention exported with the symbol `Blueprint`. If you are curious about what blueprints are available from a plugin or package, look for `*Blueprint` exports in the package's API, for plugins these are typically found in the `*-react` package.
+
+## Creating an extension from a blueprint
+
+Every extension blueprint provides a `make` method that can be used to create new extensions. It is a simple way to create a new extension where the base blueprint provides all the necessary functionality. All you need to do is to provide the necessary blueprint parameters, but you also have the ability to provide additional options, for example a `name` for the extension.
+
+The following is a simple example of how one might use the blueprint `make` method to create a new extension:
+
+```tsx
+const myPageExtension = PageBlueprint.make({
+ params: {
+ defaultPath: '/my-page',
+ loader: () => import('./components/MyPage').them(m => ),
+ },
+});
+```
+
+The returned `myPageExtension` is an extension which is ready to be used in a plugin. It is the same type of object as is returned by the lower level `createExtension` function.
+
+## Creating an extension from a blueprint with overrides
+
+Every extension blueprint also provides a `makeWithOverrides` method. It is useful in cases where you want to provide additional integration points for an extension created with a blueprint. You might for example want to define additional inputs or configuration schema, or use the existing configuration to dynamically compute the parameters passed to the blueprint.
+
+The following is an example of how one might use the blueprint `makeWithOverrides` method to create a new extension:
+
+```tsx
+const myPageExtension = PageBlueprint.makeWithOverrides({
+ config: {
+ schema: {
+ layout: z => z.enum(['grid', 'rows']).default('grid'),
+ },
+ },
+ // The original blueprint factory is provided as the first argument
+ factory(originalFactory, { config }) {
+ // Call and forward the result from the original factory, providing
+ // the blueprint parameters as the first argument.
+ return originalFactory({
+ defaultPath: '/my-page',
+ loader: () =>
+ import('./components/MyPage').them(m => (
+ // We can now access values from the factory context when providing
+ // the blueprint parameters, such as config values.
+
+ )),
+ });
+ },
+});
+```
+
+When using `makeWithOverrides`, we no longer pass the blueprint parameters directly. Instead, we provide a `factory` function that receives the original blueprint factory as the first argument, and the extension factory context as the second. We can then call the original blueprint factory with the blueprint parameters and forward the result as the return value of out factory. Notice that when passing the blueprint parameters using this pattern we have access to a lot more information than when using the `make` method, at the cost of being more complex.
+
+Apart from the addition of the blueprint parameters of the first argument to the original factory function, the `makeWithOverrides` method works the same way as [extension overrides](./25-extension-overrides.md). All the same options and rules apply, including the ability to define additional inputs, override outputs, and so on. We therefore defer to the [extension overrides](./25-extension-overrides.md) documentation for more information on how to use the `makeWithOverrides` method.
+
+## Creating an extension blueprint
+
+To create a new extension blueprint, you use the `createExtensionBlueprint` function. At the surface it is very similar to `createExtension`, but with a few key differences. Firstly you must provide a `kind` option, which will be the kind of all extensions created with the blueprint. See the [naming patterns section](./50-naming-patterns.md) for more information about how to select a good extension kind. Secondly, the `factory` function has a new signature where the first parameter is the blueprint parameters, and the second is the factory context. And finally, rather than returning an extension, `createExtensionBlueprint` returns a blueprint object with the `make` method and friends, which is used as is described above.
+
+The following is an example of how one might create a new extension blueprint:
+
+```tsx
+export interface MyWidgetBlueprintParams {
+ defaultTitle: string;
+ element: JSX.Element;
+}
+
+export const MyWidgetBlueprint = createExtensionBlueprint({
+ kind: 'my-widget',
+ attachTo: { id: 'page:my-plugin', input: 'widgets' },
+ config: {
+ schema: {
+ title: z.string().optional(),
+ },
+ },
+ output: [coreExtensionData.reactElement],
+ factory(params: MyWidgetBlueprintParams, { config }) {
+ return [
+ // Note that while this is a valid pattern, you might often want to
+ // return separate pieces of data instead, more on that below.
+ coreExtensionData.reactElement(
+
+ {params.element}
+ ,
+ ),
+ ];
+ },
+});
+```
+
+This is of course a quite bare-bones example blueprint, but still a very real example. Blueprints can be very simple, there's already a lot of value in encapsulating the extension kind, attachment point, and output in a blueprint.
+
+Most of the options provided to `createExtensionBlueprint` can be overridden when using `makeWithOverrides` to create an extension from the blueprint. These overrides work the same way as [extension overrides](./25-extension-overrides.md), and we defer to that documentation for more information on how overrides work.
+
+### Blueprint-specific extension data references
+
+In some cases you may want to define and provide [extension data reference](./20-extensions.md#extension-data-references) that are specific to your blueprint. In the above example we might want to forward the `title` as data for example, rather than encapsulating it into the `MyWidgetContainer` component. This gives the parent extension more flexibility in the rendering for our example widget extensions.
+
+To do that, we create a new extension data reference for our widget title. This references is provided via the `dataRefs` options when we create the blueprint, which makes it available for use via `MyWidgetBlueprint.dataRefs.widgetTitle`.
+
+```tsx
+export interface MyWidgetBlueprintParams {
+ defaultTitle: string;
+ element: JSX.Element;
+}
+
+const widgetTitleRef = createExtensionDataRef().with({
+ id: 'my-plugin.widget.title',
+});
+
+export const MyWidgetBlueprint = createExtensionBlueprint({
+ kind: 'my-widget',
+ attachTo: { id: 'page:my-plugin', input: 'widgets' },
+ config: {
+ schema: {
+ title: z.string().optional(),
+ },
+ },
+ output: [widgetTitleRef, coreExtensionData.reactElement],
+ factory(params: MyWidgetBlueprintParams, { config }) {
+ return [
+ widgetTitleRef(config.title ?? params.defaultTitle),
+ coreExtensionData.reactElement(params.element),
+ ];
+ },
+ dataRefs: {
+ widgetTitle: widgetTitleRef,
+ },
+});
+```
+
+### Extension Blueprints in libraries
+
+If you are publishing a plugin, the extension creators should always be exported from frontend library packages (e.g. `*-react`) rather than plugin packages.
diff --git a/docs/frontend-system/architecture/25-extension-overrides.md b/docs/frontend-system/architecture/25-extension-overrides.md
new file mode 100644
index 0000000000..d47e2697a9
--- /dev/null
+++ b/docs/frontend-system/architecture/25-extension-overrides.md
@@ -0,0 +1,307 @@
+---
+id: extension-overrides
+title: Frontend Extension Overrides
+sidebar_label: Extension Overrides
+# prettier-ignore
+description: Frontend extension overrides
+---
+
+> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
+
+## Introduction
+
+An important customization point in the frontend system is the ability to override existing extensions. It can be used for anything from slight tweaks to the extension logic, to completely replacing an extension with a custom implementation. While extensions are encouraged to make themselves configurable, there are many situations where you need to override an extension to achieve the desired behavior. The ability to override extensions should be kept in mind when building plugins, and can be a powerful tool to allow for deeper customizations without the need to re-implement large parts of the plugin.
+
+In general, most features should have a good level of customization built into them, so that users do not have to leverage extension overrides to achieve common goals. A well written feature often has [configuration](../../conf/) settings, or uses extension inputs for extensibility where applicable. An example of this is the search plugin, which allows you to provide result renderers as inputs rather than replacing the result page wholesale just to tweak how results are shown. Adopters should take advantage of those when possible in order to reduce the need and size of extension overrides.
+
+## Overriding an extension
+
+Every extension created with `createExtension` comes with an `override` method, including those created from an [extension blueprint](./23-extension-blueprints.md). The `override` method **creates a new extension**, it does not mutate the existing extension. This new extension in created in such a way that if it is installed adjacent to the existing extension, it will take precedence and override the existing extension. While the `override` method does create new extension instances, it is not intended to be used as a way to create multiple new extensions from a base template, for that use-case you will want to use an [extension blueprint](./23-extension-blueprints.md) instead.
+
+The following is an example of calling the `.override(...)` method on an extension:
+
+```tsx
+const myOverrideExtension = myExtension.override({
+ factory(originalFactory) {
+ return originalFactory();
+ },
+});
+```
+
+This override is a no-op, it does not change the behavior of the extension, but simply forwards the outputs from the original extension factory. If you are familiar with [extension blueprints](./23-extension-blueprints.md), you will recognize this factory override pattern where we get access to the original factory function. In fact the only difference is that we do not need to pass any parameters to the original factory. The first parameter is now instead the optional factory context overrides, more on that as we dive into each override pattern in the following sections.
+
+## Overriding original factory outputs
+
+When overriding an extension you can choose to forward the existing outputs, or replace them with your own. The override factory has an exception to the rule that extension factories can only return a single value for each declared output. It will instead always use the **last** value provided for each extension data reference. This makes it possible to forward the outputs from the original factory, but also provide your own, for example:
+
+```tsx
+const myOverrideExtension = myExtension.override({
+ factory(originalFactory) {
+ return [
+ ...originalFactory(),
+ coreExtensionData.reactElement(
Hello Override
),
+ ];
+ },
+});
+```
+
+You can also access individual data values from the original factory, in order to decorate the output:
+
+```tsx
+const myOverrideExtension = myExtension.override({
+ factory(originalFactory) {
+ const originalOutput = originalFactory();
+ const originalElement = originalOutput.get(coreExtensionData.reactElement);
+
+ return [
+ ...originalOutput,
+ coreExtensionData.reactElement(
+
+ Show original element
+ {originalElement}
+ ,
+ ),
+ ];
+ },
+});
+```
+
+Just as [extension factories can be declared as a generator function](./20-extensions.md#extension-factory-as-a-generator-function), so can the override factory. Using a generator function, the first example above can be written as follows:
+
+```tsx
+const myOverrideExtension = myExtension.override({
+ *factory(originalFactory) {
+ yield* originalFactory();
+ yield coreExtensionData.reactElement(
Hello Override
);
+ },
+});
+```
+
+Note the `yield*` expression, which forwards all values from the provided iterable to the generator, in this case the original factory output.
+
+## Overriding declared outputs
+
+When overriding an extension you can provide a new output declaration. This **replaces** any existing output declaration, which means that if you want to forward any of the original output you will need to declare it again. The following example shows how to override an extension and replace the output declaration:
+
+```tsx
+// Original extension
+const exampleExtension = createExtension({
+ name: 'example',
+ output: [coreExtensionData.reactElement],
+ factory: () => [coreExtensionData.reactElement(
Example
)],
+});
+
+// Override extension, with additional outputs
+const overrideExtension = exampleExtension.override({
+ output: [coreExtensionData.reactElement, coreExtensionData.routePath],
+ factory(originalFactory) {
+ return [...originalFactory(), coreExtensionData.routePath('/example')];
+ },
+});
+```
+
+When overriding the output declaration you don't need to include the original outputs. Just remember that you will no longer be able to directly forward the output from the original factory, and will still need to adhere to the contract of the input that the extension is attached to.
+
+## Overriding declared inputs
+
+When overriding an extension you can also provide new input declarations. You can define any number of new inputs, but you are **not** able to override the existing inputs declared by the original extension. The new inputs will be merged with the existing ones, giving the override factory access to both. The following example shows how to override an extension and add a new input declaration:
+
+```tsx
+const myOverrideExtension = myExtension.override({
+ inputs: {
+ myOverrideInput: createExtensionInput([coreExtensionData.reactElement]),
+ },
+ factory(originalFactory, { inputs }) {
+ const originalOutput = originalFactory();
+ const originalElement = originalOutput.get(coreExtensionData.reactElement);
+
+ return [
+ ...originalOutput,
+ coreExtensionData.reactElement(
+
+
Original element
+ {originalElement}
+
Additional inputs
+
+ {inputs.myOverrideInput.map(i => (
+
+ {i.get(coreExtensionData.reactElement)}
+
+ ))}
+
+
,
+ ),
+ ];
+ },
+});
+```
+
+## Overriding configuration schema
+
+Overriding the configuration schema works very similarly to overriding the declared inputs. You can define new configuration fields that will be merged with the existing ones, but you can not re-declare existing fields. The following example shows how to override an extension and add a new configuration field:
+
+```tsx
+const exampleExtension = createExtension({
+ config: {
+ schema: {
+ foo: z => z.string(),
+ },
+ },
+ // ...
+});
+
+const overrideExtension = exampleExtension.override({
+ config: {
+ schema: {
+ bar: z => z.string(),
+ },
+ },
+ factory(originalFactory, { config }) {
+ //
+ console.log(`foo=${config.foo} bar=${config.bar}`);
+ return originalFactory();
+ },
+});
+```
+
+## Overriding original factory config context
+
+In all examples so far we have called the `originalFactory` callback without any arguments. It is however possible to override parts of the factory context for the original factory using the first parameter of the original factory. This can be useful if you want to override the provided configuration or change the inputs in some way. Note that if you are implementing a `factory` for a blueprint, the override factory context will instead be the second parameter of the original factory function. The following is an example of how to override the configuration for the original factory:
+
+```tsx
+const exampleExtension = createExtension({
+ name: 'example',
+ config: {
+ schema: {
+ layout: z => z.enum(['grid', 'list']).optional(),
+ },
+ },
+ output: [coreExtensionData.reactElement],
+ factory: ({ config }) => [
+ coreExtensionData.reactElement(
+ ,
+ ),
+ ],
+});
+
+const overrideExtension = exampleExtension.override({
+ factory(originalFactory, { config }) {
+ return originalFactory({
+ config: {
+ // Switch default layout from 'list' to 'grid'
+ layout: config.layout ?? 'grid',
+ },
+ });
+ },
+});
+```
+
+As can be seen in the above example we can provide a new configuration object in the `originalFactory` call using the `config` property. When providing the `config` property we will completely override the original configuration object that would otherwise have been provided to the original factory. Note that this object must adhere to the output type of the configuration schema, which might not be intuitive. It's due to the configuration having already been processed and validated by Zod at this point, which means that things like defaults in the schema will not be applied again.
+
+## Overriding original factory inputs context
+
+In addition to the configuration, you are also able to override the inputs provided to the original factory. Just like when overriding configuration you will completely replace the original inputs with the new ones, but you are able to forward the inputs that you are receiving to the override factory.
+
+You can override each input in one of two ways, which can not be combined. You can forward (or not forward) the original input, optionally filtering out individual items or reordering them. Or you can provide new values for the input, which will replace the original input. When providing new values you must forward all existing inputs and the inputs can not be reordered, and when forwarding the existing inputs you can not provide new values.
+
+The following example shows how to override the values provided for each input item:
+
+```tsx
+const exampleExtension = createExtension({
+ inputs: {
+ items: createExtensionInput([coreExtensionData.reactElement]),
+ },
+ // ...
+});
+
+const overrideExtension = exampleExtension.override({
+ factory(originalFactory, { inputs }) {
+ return originalFactory({
+ inputs: {
+ items: inputs.items.map(i => [
+ coreExtensionData.reactElement(
+ {i.get(coreExtensionData.reactElement)},
+ ),
+ ]),
+ },
+ });
+ },
+});
+```
+
+In contrast, the following example shows how to forward the original inputs, but in a different order:
+
+```tsx
+const exampleExtension = createExtension({
+ inputs: {
+ content: createExtensionInput([coreExtensionData.reactElement], {
+ singleton: true,
+ optional: true,
+ }),
+ items: createExtensionInput([coreExtensionData.reactElement]),
+ },
+ // ...
+});
+
+const overrideExtension = exampleExtension.override({
+ factory(originalFactory, { inputs }) {
+ return originalFactory({
+ inputs: {
+ // We can also skip forwarding the original input, if we want to remove it
+ content: inputs.content,
+ // Sort items input by their extension ID
+ items: inputs.items.toSorted((a, b) =>
+ a.node.spec.id.localeCompare(b.node.spec.id),
+ ),
+ },
+ });
+ },
+});
+```
+
+## Installing override extension in an app
+
+To install extension overrides in a Backstage app you should use `plugin.withOverrides` whenever you are overriding or adding extensions for a plugin. See the section on [overriding a plugin](./15-plugins.md#overriding-a-plugin) for more information.
+
+There is also a `createExtensionOverrides` function that can be used to install a collection of standalone extensions in an app. This method will be replaced with a different mechanism in the future, but for now remains the only way to override the built-in extensions in the app or to package extensions for a plugin package separate from the plugin itself.
+
+Note that while using either of these options you don't necessarily need to use the extension `.override(...)` method to create the overrides. You can also create new extensions with `createExtension` or a blueprint that are either completely net-new extensions, or override an existing extension by using the same `kind`, `namespace` and `name` to produce the same extension ID.
+
+### Creating a standalone extension bundle
+
+The following example shows how to create a standalone extension bundle that overrides the search page from the search plugin:
+
+```tsx
+import {
+ createPageExtension,
+ createExtensionOverrides,
+} from '@backstage/frontend-plugin-api';
+
+const customSearchPage = PageBlueprint.make({
+ // Since this is a standalone extension we need to provide the namespace to match the search plugin
+ namespace: 'search',
+ params: {
+ defaultPath: '/search',
+ loader: () =>
+ import('./CustomSearchPage').then(m => ),
+ },
+});
+
+export default createExtensionOverrides({
+ extensions: [customSearchPage],
+});
+```
+
+Assuming the above code resides in the `@internal/search-page` package, you can install it in your app like this:
+
+```tsx title="packages/app/src/App.tsx"
+import { createApp } from '@backstage/frontend-app-api';
+import searchPageOverride from '@internal/search-page';
+
+const app = createApp({
+ // highlight-next-line
+ features: [searchPageOverride],
+});
+
+export default app.createRoot();
+```
diff --git a/docs/frontend-system/architecture/08-references.md b/docs/frontend-system/architecture/30-references.md
similarity index 100%
rename from docs/frontend-system/architecture/08-references.md
rename to docs/frontend-system/architecture/30-references.md
diff --git a/docs/frontend-system/architecture/06-utility-apis.md b/docs/frontend-system/architecture/33-utility-apis.md
similarity index 97%
rename from docs/frontend-system/architecture/06-utility-apis.md
rename to docs/frontend-system/architecture/33-utility-apis.md
index 49e5854b65..c20936f819 100644
--- a/docs/frontend-system/architecture/06-utility-apis.md
+++ b/docs/frontend-system/architecture/33-utility-apis.md
@@ -10,7 +10,7 @@ description: Utility APIs
## Overview
-Utility APIs are pieces of standalone functionality, interfaces that can be requested by plugins to use. They are defined by a TypeScript interface as well as a reference (an "API ref") used to access its implementation. They can be provided both by plugins and the core framework, and are themselves [extensions](../architecture/03-extensions.md) that can have inputs, be replaced, and be declaratively configured in your app-config.
+Utility APIs are pieces of standalone functionality, interfaces that can be requested by plugins to use. They are defined by a TypeScript interface as well as a reference (an "API ref") used to access its implementation. They can be provided both by plugins and the core framework, and are themselves [extensions](../architecture/20-extensions.md) that can have inputs, be replaced, and be declaratively configured in your app-config.
A common example of a utility API is a client interface to interact with the backend part of a plugin, such as the catalog client. Any frontend plugin can then request an implementation of that interface to make requests through.
diff --git a/docs/frontend-system/architecture/07-routes.md b/docs/frontend-system/architecture/36-routes.md
similarity index 99%
rename from docs/frontend-system/architecture/07-routes.md
rename to docs/frontend-system/architecture/36-routes.md
index 9db4d007b6..e684932414 100644
--- a/docs/frontend-system/architecture/07-routes.md
+++ b/docs/frontend-system/architecture/36-routes.md
@@ -42,7 +42,7 @@ The code snippet in the previous section does not indicate which plugin the rout
```tsx title="plugins/catalog/src/plugin.tsx"
import React from 'react';
import {
- createPlugin,
+ createFrontendPlugin,
createPageExtension,
} from '@backstage/frontend-plugin-api';
import { indexRouteRef } from './routes';
@@ -55,7 +55,7 @@ const catalogIndexPage = createPageExtension({
loader: () => import('./components').then(m => ),
});
-export default createPlugin({
+export default createFrontendPlugin({
id: 'catalog',
// highlight-start
routes: {
@@ -196,7 +196,7 @@ Now the only thing left is to provide the page and external route via a plugin:
```tsx title="plugins/catalog/src/plugin.tsx"
import React from 'react';
import {
- createPlugin,
+ createFrontendPlugin,
createPageExtension,
useRouteRef,
} from '@backstage/frontend-plugin-api';
@@ -208,7 +208,7 @@ const catalogIndexPage = createPageExtension({
loader: () => import('./components').then(m => ),
});
-export default createPlugin({
+export default createFrontendPlugin({
id: 'catalog',
routes: {
index: indexRouteRef,
@@ -404,7 +404,7 @@ Finally, see how a plugin can provide subroutes:
```tsx title="plugins/catalog/src/plugin.tsx"
import React from 'react';
import {
- createPlugin,
+ createFrontendPlugin,
createPageExtension,
} from '@backstage/frontend-plugin-api';
import { indexRouteRef, detailsSubRouteRef } from './routes';
@@ -415,7 +415,7 @@ const catalogIndexPage = createPageExtension({
loader: () => import('./components').then(m => ),
});
-export default createPlugin({
+export default createFrontendPlugin({
id: 'catalog',
routes: {
index: indexRouteRef,
diff --git a/docs/frontend-system/architecture/08-naming-patterns.md b/docs/frontend-system/architecture/50-naming-patterns.md
similarity index 91%
rename from docs/frontend-system/architecture/08-naming-patterns.md
rename to docs/frontend-system/architecture/50-naming-patterns.md
index f031b80d84..11e0b8e733 100644
--- a/docs/frontend-system/architecture/08-naming-patterns.md
+++ b/docs/frontend-system/architecture/50-naming-patterns.md
@@ -23,7 +23,7 @@ Example:
```ts
// This declaration is only for internal usage in tests. This could also be a direct default export.
-export const userSettingsPlugin = createPlugin({
+export const userSettingsPlugin = createFrontendPlugin({
id: 'user-settings',
...
})
@@ -42,7 +42,7 @@ Note that while we use this naming pattern for the plugin instance this is only
| ID | `[:][/]` | `'core.nav'`, `'page:user-settings'`, `'entity-card:catalog/about'` |
| Symbol | `[][]` | `coreNav`, `userSettingsPage`, `catalogAboutEntityCard` |
-When you create a new extension you never provide the ID directly. Instead, you indirectly or directly provide the kind, namespace, and name parts that make up the ID. The kind is always provided by the blueprint creator, the only exception is if you use `createExtension` directly. Any extension that is provided by a plugin will by default have its namespace set to the plugin ID, so you generally only need to provide an explicit namespace if you want to override an existing extension. The name is also optional, and primarily used to distinguish between multiple extensions of the same kind and namespace. If a plugin doesn't need to distinguish between different extensions of the same kind, the name can be omitted.
+When you create a new extension you never provide the ID directly. Instead, you indirectly or directly provide the kind, namespace, and name parts that make up the ID. The kind is always provided by the extension blueprint, the only exception is if you use `createExtension` directly. Any extension that is provided by a plugin will by default have its namespace set to the plugin ID, so you generally only need to provide an explicit namespace if you want to override an existing extension. The name is also optional, and primarily used to distinguish between multiple extensions of the same kind and namespace. If a plugin doesn't need to distinguish between different extensions of the same kind, the name can be omitted.
Example:
@@ -67,7 +67,7 @@ const catalogSearchResultListItem = SearchResultListItemBlueprint.make({
});
// Note that the extensions themselves are not exported, only the plugin instance
-export const catalogPlugin = createPlugin({
+export const catalogPlugin = createFrontendPlugin({
id: 'catalog',
extensions: [catalogEntityPage, catalogSearchResultListItem /* ... */],
});
diff --git a/docs/frontend-system/architecture/60-migrations.md b/docs/frontend-system/architecture/60-migrations.md
new file mode 100644
index 0000000000..a1ab0197f7
--- /dev/null
+++ b/docs/frontend-system/architecture/60-migrations.md
@@ -0,0 +1,104 @@
+---
+id: migrations
+title: Frontend System Migrations
+sidebar_label: Migrations
+# prettier-ignore
+description: Migration documentation for different versions of the frontend system core APIs.
+---
+
+> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
+
+## Introduction
+
+This section provides migration guides for different versions of the frontend system core APIs. Each guide will provide a summary of the changes that have been made for a particular Backstage release, and how to update your usage of the core APIs.
+
+This guide is intended for app and plugin authors who have already migrated their code to the new frontend system, and are looking to keep it up to date with the latest changes. These guides do not cover trivial migrations that can be explained in a deprecation message, such as a renamed export.
+
+## 1.30
+
+### Reworked extension inputs and outputs
+
+In previous versions of the frontend system you would define extension inputs and outputs as an "data map" where each named property corresponded to a piece of data that could be accessed via the same name in the extension factory. In order to better support extension overrides and blueprints, as well as reduce the risk of confusion, these data maps have been replaced by an array of data references.
+
+For example, an extension previously declared like this:
+
+```tsx
+createExtension({
+ name: 'example',
+ attachTo: { id: 'some-extension', input: 'content' },
+ inputs: {
+ header: createExtensionInput(
+ { element: coreExtensionData.reactElement },
+ {
+ optional: true,
+ singleton: true,
+ },
+ ),
+ },
+ output: { element: coreExtensionData.reactElement },
+ factory({ inputs }) {
+ return {
+ element: ,
+ };
+ },
+});
+```
+
+Would now look like this:
+
+```tsx
+createExtension({
+ name: 'example',
+ attachTo: { id: 'some-extension', input: 'content' },
+ inputs: {
+ header: createExtensionInput([coreExtensionData.reactElement], {
+ optional: true,
+ singleton: true,
+ }),
+ },
+ output: [coreExtensionData.reactElement],
+ factory({ inputs }) {
+ return [
+ coreExtensionData.reactElement(
+ ,
+ ),
+ ];
+ },
+});
+```
+
+Note the changes to the `inputs` and `output` declarations, as well as how these are used in the factory. Both the `inputs` and `output` now declare their expected data using an array, without names tied to each piece of data. The `get` method on the input object is used to access the input data, and accept a data reference matching the data that was declared for that input.
+
+The biggest change in practice is how the extension factories output their data. Instead of returning an object with the data values, you instead use each extension data reference to encapsulate a value and return a collection of these encapsulated values from the factory.
+
+### Blueprints instead of extension creators
+
+The "extension creator" pattern where `createExtension` was wrapped up in a function for creating specific kind of extensions has been replaced by [extension blueprints](./23-extension-blueprints.md). Extension creators were hard to implement and to maintain, with blueprints providing a much more consistent and powerful API surface for both plugin builders and integrators. For example, `createPageExtension` was the extension creator equivalent of `PageBlueprint`.
+
+Replace all existing usages of extension creators in your plugin or app with the corresponding blueprint. For a given extension creator `createExtension`, the blueprint equivalent is `Blueprint`. There might be slight differences in the API between the two, but most often you just need to move the kind-specific options of the extension creator to be passed as parameters to the blueprint. Note that if your extension declared any additional inputs or config you'll need to use the [`.makeWithOverrides`](./23-extension-blueprints.md#creating-an-extension-from-a-blueprint-with-overrides) method of the blueprint.
+
+If your plugin exports and extension creators, these should be migrated to blueprints instead.
+
+### Extension tester rework
+
+The `createExtensionTester` from the `@backstage/frontend-test-utils` package has been reworked to better support testing of extensions. The new API allows access to extension output directly using the new `.get(ref)` method, and also provides access to all tested extensions through the new `.query(id/extension)` method.
+
+The `.render()` method that used to render the test subject in a test app has been deprecated. The extension tester no longer constructs a full app tree, but instead only instantiates the tree for the extensions under test. If you want to test the rendering of an extension that outputs in an app, you can instead use the `renderInTestApp` utility in combination with the new `.reactElement()` method of the extension tester: `renderInTestApp(tester.reactElement())`.
+
+### Extension data references update
+
+The way that extension data references are declared has been changed to allow for type inference of the ID. This requires the declaration to be split into two separate function calls, one to supply the type and the other to infer any options. For example, a reference that was previously declared like this:
+
+```ts
+export const myExtension = createExtensionDataRef('my-plugin.my-data');
+```
+
+Should be updated to the following:
+
+```ts
+export const myExtension = createExtensionDataRef().with({
+ id: 'my-plugin.my-data',
+});
+```
diff --git a/docs/frontend-system/building-apps/01-index.md b/docs/frontend-system/building-apps/01-index.md
index ea7fe20948..16aacc1185 100644
--- a/docs/frontend-system/building-apps/01-index.md
+++ b/docs/frontend-system/building-apps/01-index.md
@@ -66,7 +66,7 @@ Linking routes from different plugins requires this configuration. You can do th
### Enable feature discovery
-Use this setting to enable experimental feature discovery when building your app with `@backstage/cli`. With this configuration your application tries to discover and install package extensions automatically, check [here](../architecture/02-app.md#feature-discovery) for more details.
+Use this setting to enable experimental feature discovery when building your app with `@backstage/cli`. With this configuration your application tries to discover and install package extensions automatically, check [here](../architecture/10-app.md#feature-discovery) for more details.
:::warning
Remember that package extensions that are not auto-discovered must be manually added to the application when creating an app. See [features](#install-features-manually) for more details.
@@ -78,7 +78,7 @@ It is possible to enable, disable and configure extensions individually in the `
### Customize or override built-in extensions
-Previously you would customize the application route, components, apis, sidebar, etc. through the code in `App.tsx`. Now we want you to write less code and install more extensions to customize your Backstage instance. See [here](../building-plugins/03-extension-types.md) which types of extensions are available for you to customize your application.
+Previously you would customize the application routes, components, apis, sidebar, etc. through the code in `App.tsx`. Now we want to allow the same thing to be achieved while writing less code and instead installing more extensions to customize your Backstage instance. See the [extension blueprints](../building-plugins/03-common-extension-blueprints.md) section for a list of common extension kinds that are available for you to customize and extend your application.
## Use code to customize the app at a more granular level
@@ -99,7 +99,7 @@ export default app.createRoot();
```
:::info
-You can also pass overrides to the features array, for more details, please read the [extension overrides](../architecture/05-extension-overrides.md) documentation.
+You can also pass overrides to the features array, for more details, please read the [extension overrides](../architecture/25-extension-overrides.md) documentation.
:::
### Using an async features loader
diff --git a/docs/frontend-system/building-apps/03-built-in-extensions.md b/docs/frontend-system/building-apps/03-built-in-extensions.md
index a5e6476eb0..5f74100df0 100644
--- a/docs/frontend-system/building-apps/03-built-in-extensions.md
+++ b/docs/frontend-system/building-apps/03-built-in-extensions.md
@@ -24,7 +24,7 @@ Be careful when disabling built-in extensions, as there may be other extensions
## Override built-in extensions
-You can override any built-in extension whenever their customizations, whether through configuration or input, do not meet a use case for your Backstage instance. Check out [this](../architecture/05-extension-overrides.md) documentation on how to override application extensions.
+You can override any built-in extension whenever their customizations, whether through configuration or input, do not meet a use case for your Backstage instance. Check out [this](../architecture/25-extension-overrides.md) documentation on how to override application extensions.
:::warning
Be aware there could be some implementation requirements to properly override an built-in extension, such as using same apis and do not remove inputs or configurations otherwise you can cause a side effect in other parts of the system that expects same minimal behavior.
diff --git a/docs/frontend-system/building-apps/08-migrating.md b/docs/frontend-system/building-apps/08-migrating.md
index 716e0da772..ceb3f34c35 100644
--- a/docs/frontend-system/building-apps/08-migrating.md
+++ b/docs/frontend-system/building-apps/08-migrating.md
@@ -23,7 +23,7 @@ import { createApp } from '@backstage/frontend-app-api';
This immediate switch will lead to a lot of breakages that we need to fix.
-Let's start by addressing the change to `app.createRoot(...)`, which no longer accepts any arguments. This represents a fundamental change that the new frontend system introduces. In the old system the app element tree that you passed to `app.createRoot(...)` was the primary way that you installed and configured plugins and features in your app. In the new system this is instead replaced by extensions that are wired together into an extension tree. Much more responsibility has now been shifted to plugins, for example you no longer have to manually provide the route path for each plugin page, but instead only configure it if you want to override the default. For more information on how the new system works, see the [architecture](../architecture/01-index.md) section.
+Let's start by addressing the change to `app.createRoot(...)`, which no longer accepts any arguments. This represents a fundamental change that the new frontend system introduces. In the old system the app element tree that you passed to `app.createRoot(...)` was the primary way that you installed and configured plugins and features in your app. In the new system this is instead replaced by extensions that are wired together into an extension tree. Much more responsibility has now been shifted to plugins, for example you no longer have to manually provide the route path for each plugin page, but instead only configure it if you want to override the default. For more information on how the new system works, see the [architecture](../architecture/00-index.md) section.
Given that the app element tree is most of what builds up the app, it's likely also going to be the majority of the migration effort. In order to make the migration as smooth as possible we have provided a helper that lets you convert an existing app element tree into plugins that you can install in a new app. This in turn allows for a gradual migration of individual plugins, rather than needing to migrate the entire app structure at once.
@@ -95,7 +95,7 @@ At this point the contents of your app should be past the initial migration stag
## Migrating `createApp` Options
-Many of the `createApp` options have been migrated to use extensions instead. Each will have their own [extension creator](../architecture/03-extensions.md#extension-creators) that you use to create a custom extension. To add these standalone extensions to the app they need to be passed to `createExtensionOverrides`, which bundles them into a _feature_ that you can install in the app. See the [standalone extensions](../architecture/05-extension-overrides.md#create-standalone-extensions) section for more information.
+Many of the `createApp` options have been migrated to use extensions instead. Each will have their own [extension blueprint](../architecture/23-extension-blueprints.md) that you use to create a custom extension. To add these standalone extensions to the app they need to be passed to `createExtensionOverrides`, which bundles them into a _feature_ that you can install in the app. See the [standalone extensions](../architecture/25-extension-overrides.md#creating-a-standalone-extension-bundle) section for more information.
For example, assuming you have a `lightTheme` extension that you want to add to your app, you can use the following:
@@ -115,7 +115,7 @@ You can then also add any additional extensions that you may need to create as p
### `apis`
-[Utility API](../utility-apis/01-index.md) factories are now installed as extensions instead. Pass the existing factory to `createApiExtension` and install it in the app. For more information, see the section on [configuring Utility APIs](../utility-apis/04-configuring.md).
+[Utility API](../utility-apis/01-index.md) factories are now installed as extensions instead. Pass the existing factory to `ApiBlueprint` and install it in the app. For more information, see the section on [configuring Utility APIs](../utility-apis/04-configuring.md).
For example, the following `apis` configuration:
@@ -134,12 +134,15 @@ const app = createApp({
Can be converted to the following extension:
```ts
-const scmIntegrationsApi = createApiExtension({
- factory: createApiFactory({
- api: scmIntegrationsApiRef,
- deps: { configApi: configApiRef },
- factory: ({ configApi }) => ScmIntegrationsApi.fromConfig(configApi),
- }),
+const scmIntegrationsApi = ApiBlueprint.make({
+ name: 'scm-integrations',
+ params: {
+ factory: createApiFactory({
+ api: scmIntegrationsApiRef,
+ deps: { configApi: configApiRef },
+ factory: ({ configApi }) => ScmIntegrationsApi.fromConfig(configApi),
+ }),
+ },
});
```
@@ -176,7 +179,7 @@ createApp({
});
```
-Plugins don't even have to be imported manually after installing their package if [features discovery](../architecture/02-app.md#feature-discovery) is enabled.
+Plugins don't even have to be imported manually after installing their package if [features discovery](../architecture/10-app.md#feature-discovery) is enabled.
```yaml title="in app-config.yaml"
app:
@@ -207,7 +210,7 @@ createApp({
Can be converted to the following plugin configuration:
```tsx
-createPlugin({
+createFrontendPlugin({
id: 'tech-radar',
// ...
featureFlags: [{ name: 'tech-radar' }],
@@ -219,9 +222,9 @@ createPlugin({
Many app components are now installed as extensions instead using `createComponentExtension`. See the section on [configuring app components](./01-index.md#configure-your-app) for more information.
-The `Router` component is now a built-in extension that you can [override](../architecture/05-extension-overrides.md) using `createRouterExtension`.
+The `Router` component is now a built-in extension that you can [override](../architecture/25-extension-overrides.md) using `createRouterExtension`.
-The Sign-in page is now installed as an extension using the `createSignInPageExtension` instead.
+The Sign-in page is now installed as an extension, created using the `SignInPageBlueprint` instead.
For example, the following sign-in page configuration:
@@ -246,25 +249,27 @@ const app = createApp({
Can be converted to the following extension:
```tsx
-const signInPage = createSignInPageExtension({
- loader: async () => props =>
- (
-
- ),
+const signInPage = SignInPageBlueprint.make({
+ params: {
+ loader: async () => props =>
+ (
+
+ ),
+ },
});
```
### `themes`
-Themes are now installed as extensions, using `createThemeExtension`.
+Themes are now installed as extensions, created using `ThemeBlueprint`.
For example, the following theme configuration:
@@ -287,14 +292,19 @@ const app = createApp({
Can be converted to the following extension:
```tsx
-const lightTheme = createThemeExtension({
- id: 'light',
- title: 'Light Theme',
- variant: 'light',
- icon: ,
- Provider: ({ children }) => (
-
- ),
+const lightTheme = ThemeBlueprint.make({
+ name: 'light',
+ params: {
+ theme: {
+ id: 'light',
+ title: 'Light Theme',
+ variant: 'light',
+ icon: ,
+ Provider: ({ children }) => (
+
+ ),
+ },
+ },
});
```
@@ -341,7 +351,7 @@ const app = createApp({
### `bindRoutes`
-Route bindings can still be done using this option, but you now also have the ability to bind routes using static configuration instead. See the section on [binding routes](../architecture/07-routes.md#binding-external-route-references) for more information.
+Route bindings can still be done using this option, but you now also have the ability to bind routes using static configuration instead. See the section on [binding routes](../architecture/36-routes.md#binding-external-route-references) for more information.
Note that if you are binding routes from a legacy plugin that was converted using `convertLegacyApp`, you will need to use the `convertLegacyRouteRefs` and/or `convertLegacyRouteRef` to convert the routes to be compatible with the new system.
@@ -360,7 +370,7 @@ const app = createApp({
### `__experimentalTranslations`
-Translations are now installed as extensions, using `createTranslationExtension`.
+Translations are now installed as extensions, created using `TranslationBlueprint`.
For example, the following translations configuration:
@@ -383,11 +393,14 @@ createApp({
Can be converted to the following extension:
```tsx
-createTranslationExtension({
- resource: createTranslationMessages({
- ref: catalogTranslationRef,
- catalog_page_create_button_title: 'Create Software',
- }),
+TranslationBlueprint.make({
+ name: 'catalog-overrides',
+ params: {
+ resource: createTranslationMessages({
+ ref: catalogTranslationRef,
+ catalog_page_create_button_title: 'Create Software',
+ }),
+ },
});
```
@@ -470,7 +483,7 @@ const routes = (
);
```
-If you are using [app feature discovery](../architecture/02-app.md#feature-discovery) the installation step is simple, it's already done! The new version of the scaffolder plugin was already discovered and present in the app, it was simply disabled because the plugin created from the legacy route had higher priority. If you do not use feature discovery, you will instead need to manually install the new scaffolder plugin in your app through the `features` option of `createApp`.
+If you are using [app feature discovery](../architecture/10-app.md#feature-discovery) the installation step is simple, it's already done! The new version of the scaffolder plugin was already discovered and present in the app, it was simply disabled because the plugin created from the legacy route had higher priority. If you do not use feature discovery, you will instead need to manually install the new scaffolder plugin in your app through the `features` option of `createApp`.
Continue this process for each of your legacy routes until you have migrated all of them. For any plugin with additional extensions installed as children of the `Route`, refer to the plugin READMEs for more detailed instructions. For the entity pages, refer to the [separate section](#entity-pages).
@@ -482,24 +495,22 @@ The entity pages are typically defined in `packages/app/src/components/catalog`
New apps feature a built-in sidebar extension (`app/nav`) that will render all nav item extensions provided by plugins. This is a placeholder implementation and not intended as a long-term solution. In the future we will aim to provide a more flexible sidebar extension that allows for more customization out of the box.
-Because the built-in sidebar is quite limited you may want to override the sidebar with your own custom implementation. To do so, use `createExtension` directly and refer to the [original sidebar implementation](https://github.com/backstage/backstage/blob/master/packages/frontend-app-api/src/extensions/AppNav.tsx). The following is an example of how to take your existing sidebar from the `Root` component that you typically find in `packages/app/src/components/Root.tsx`, and use it in an [extension override](../architecture/05-extension-overrides.md):
+Because the built-in sidebar is quite limited you may want to override the sidebar with your own custom implementation. To do so, use `createExtension` directly and refer to the [original sidebar implementation](https://github.com/backstage/backstage/blob/master/packages/frontend-app-api/src/extensions/AppNav.tsx). The following is an example of how to take your existing sidebar from the `Root` component that you typically find in `packages/app/src/components/Root.tsx`, and use it in an [extension override](../architecture/25-extension-overrides.md):
```tsx
const nav = createExtension({
namespace: 'app',
name: 'nav',
attachTo: { id: 'app/layout', input: 'nav' },
- output: {
- element: coreExtensionData.reactElement,
- },
+ output: [coreExtensionData.reactElement],
factory({ inputs }) {
- return {
- element: (
+ return [
+ coreExtensionData.reactElement(
{/* Sidebar contents from packages/app/src/components/Root.tsx go here */}
-
+ ,
),
- };
+ ];
},
});
```
@@ -548,7 +559,7 @@ export default app.createRoot(
);
```
-Any app root wrapper needs to be migrated to be an extension, using `createAppRootWrapperExtension`. Note that if you have multiple wrappers they must be completely independent of each other, i.e. the order in which they the appear in the React tree should not matter. If that is not the case then you should group them into a single wrapper.
+Any app root wrapper needs to be migrated to be an extension, created using `AppRootWrapperBlueprint`. Note that if you have multiple wrappers they must be completely independent of each other, i.e. the order in which they the appear in the React tree should not matter. If that is not the case then you should group them into a single wrapper.
Here is an example converting the `CustomAppBarrier` into extension:
@@ -558,11 +569,13 @@ createApp({
features: [
createExtensionOverrides({
extensions: [
- createAppRootWrapperExtension({
- name: 'CustomAppBarrier',
- // Whenever your component uses legacy core packages, wrap it with "compatWrapper"
- // e.g. props => compatWrapper()
- Component: CustomAppBarrier,
+ AppRootWrapperBlueprint.make({
+ name: 'custom-app-barrier',
+ params: {
+ // Whenever your component uses legacy core packages, wrap it with "compatWrapper"
+ // e.g. props => compatWrapper()
+ Component: CustomAppBarrier,
+ },
}),
],
}),
diff --git a/docs/frontend-system/building-plugins/01-index.md b/docs/frontend-system/building-plugins/01-index.md
index f8d80f9382..57a783d406 100644
--- a/docs/frontend-system/building-plugins/01-index.md
+++ b/docs/frontend-system/building-plugins/01-index.md
@@ -8,9 +8,9 @@ description: Building frontend plugins using the new frontend system
> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
-This section covers how to build your own frontend [plugins](../architecture/04-plugins.md) and
-[overrides](../architecture/05-extension-overrides.md). They are sometimes collectively referred to as
-frontend _features_, and what you install to build up a Backstage frontend [app](../architecture/02-app.md).
+This section covers how to build your own frontend [plugins](../architecture/15-plugins.md) and
+[overrides](../architecture/25-extension-overrides.md). They are sometimes collectively referred to as
+frontend _features_, and what you install to build up a Backstage frontend [app](../architecture/10-app.md).
## Creating a new plugin
@@ -24,14 +24,14 @@ The created plugin will currently be templated for use in the legacy frontend sy
## The plugin instance
-The starting point of a frontend plugin is the `createPlugin` function, which accepts a single options object as its only parameter. It is imported from `@backstage/frontend-plugin-api`, which is where you will find most of the common APIs for building plugins.
+The starting point of a frontend plugin is the `createFrontendPlugin` function, which accepts a single options object as its only parameter. It is imported from `@backstage/frontend-plugin-api`, which is where you will find most of the common APIs for building plugins.
This is how to create a minimal plugin:
```tsx title="in src/plugin.ts"
-import { createPlugin } from '@backstage/frontend-plugin-api';
+import { createFrontendPlugin } from '@backstage/frontend-plugin-api';
-export const examplePlugin = createPlugin({
+export const examplePlugin = createFrontendPlugin({
id: 'example',
extensions: [],
});
@@ -43,13 +43,13 @@ export { examplePlugin as default } from './plugin';
Note that we export the plugin as the default export of our package from `src/index.ts`. This is important, as it is how users of our plugin are able to seamlessly install the plugin package in a Backstage app without having to reference the plugin instance through code.
-The plugin ID should be a lowercase dash-separated string, while the plugin instance variable should be the camel case version of the ID with a `Plugin` suffix. For more details on naming patterns within the frontend system, see [the article on naming patterns](../architecture/08-naming-patterns.md). By sticking to these naming patterns you ensure that users of your plugin more easily recognize the exports and features provided by your plugin.
+The plugin ID should be a lowercase dash-separated string, while the plugin instance variable should be the camel case version of the ID with a `Plugin` suffix. For more details on naming patterns within the frontend system, see [the article on naming patterns](../architecture/50-naming-patterns.md). By sticking to these naming patterns you ensure that users of your plugin more easily recognize the exports and features provided by your plugin.
## Adding extensions
-The plugin that we created above is empty, and doesn't provide any actual functionality. To add functionality to a plugin you need to create and provide it with one or more [extensions](../architecture/03-extensions.md). Let's continue by adding a standalone page to our plugin, as well as a navigation item that allows users to navigate to the page.
+The plugin that we created above is empty, and doesn't provide any actual functionality. To add functionality to a plugin you need to create and provide it with one or more [extensions](../architecture/20-extensions.md). Let's continue by adding a standalone page to our plugin, as well as a navigation item that allows users to navigate to the page.
-To create a new extension you typically use pre-defined [extension creators](../architecture/03-extensions.md#extension-creators), provided either by the framework itself or by other plugins. In this case we'll need to use `createPageExtension` and `createNavItemExtension`, both from `@backstage/frontend-plugin-api`. We will also need to [create a route reference](../architecture/07-routes.md#creating-a-route-reference) to use as a reference for out page, allowing us to dynamically create URLs that link to our page.
+To create a new extension you typically use pre-defined [extension blueprints](../architecture/23-extension-blueprints.md), provided either by the framework itself or by other plugins. In this case we'll use `PageBlueprint` and `NavItemBlueprint`, both from `@backstage/frontend-plugin-api`. We will also need to [create a route reference](../architecture/36-routes.md#creating-a-route-reference) to use as a reference for our page, allowing us to dynamically create URLs that link to our page.
```tsx title="in src/routes.ts"
import { createRouteRef } from '@backstage/frontend-plugin-api';
@@ -63,7 +63,7 @@ export const rootRouteRef = createRouteRef();
```tsx title="in src/plugin.ts"
import {
- createPlugin,
+ createFrontendPlugin,
createPageExtension,
createNavItemExtension,
} from '@backstage/frontend-plugin-api';
@@ -71,28 +71,33 @@ import { rootRouteRef } from './routes';
// Note that these extensions aren't exported, only the plugin itself is.
// You can export it locally for testing purposes, but don't export it from the plugin package.
-const examplePage = createPageExtension({
- routeRef: rootRouteRef,
+const examplePage = PageBlueprint.make({
+ params: {
+ routeRef: rootRouteRef,
- // This is the default path of this page, but integrators are free to override it
- defaultPath: '/example',
+ // This is the default path of this page, but integrators are free to override it
+ defaultPath: '/example',
- // Page extensions are always dynamically loaded using React.lazy().
- // All of the functionality of this page is implemented in the
- // ExamplePage component, which is a regular React component.
- // highlight-next-line
- loader: () => import('./components/ExamplePage').then(m => ),
+ // Page extensions are always dynamically loaded using React.lazy().
+ // All of the functionality of this page is implemented in the
+ // ExamplePage component, which is a regular React component.
+ // highlight-next-line
+ loader: () =>
+ import('./components/ExamplePage').then(m => ),
+ },
});
// This nav item is provided to the app.nav extension, and will by default be rendered as a sidebar item
-const exampleNavItem = createNavItemExtension({
- routeRef: rootRouteRef,
- title: 'Example',
- icon: ExampleIcon, // Custom SvgIcon, or one from the Material UI icon library
+const exampleNavItem = NavItemBlueprint.make({
+ params: {
+ routeRef: rootRouteRef,
+ title: 'Example',
+ icon: ExampleIcon, // Custom SvgIcon, or one from the Material UI icon library
+ },
});
// The same plugin as above, now with the extensions added
-export const examplePlugin = createPlugin({
+export const examplePlugin = createFrontendPlugin({
id: 'example',
extensions: [examplePage, exampleNavItem],
// We can also make routes available to other plugins.
@@ -106,7 +111,7 @@ export const examplePlugin = createPlugin({
What we've built here is a very common type of plugin. It's a top-level tool that provides a single page, along with a method for navigating to that page. The implementation of the page component, in this case the highlighted `ExamplePage`, can be arbitrarily complex. It can be anything from a single simple information page, to a full-blown application with multiple sub-pages.
-We have also provided external access to our route reference by passing it to the plugin `routes` option. This makes it possible for app integrators to bind an external link from a different plugin to our plugin page. You can read more about how this works in the [External Route References](../architecture/07-routes.md#external-route-references) section.
+We have also provided external access to our route reference by passing it to the plugin `routes` option. This makes it possible for app integrators to bind an external link from a different plugin to our plugin page. You can read more about how this works in the [External Route References](../architecture/36-routes.md#external-route-references) section.
## Utility APIs
@@ -157,18 +162,21 @@ import {
import { exampleApiRef, DefaultExampleApi } from './api';
// highlight-add-start
-const exampleApi = createApiExtension({
- factory: createApiFactory({
- api: exampleApiRef,
- deps: {},
- factory: () => new DefaultExampleApi(),
- }),
+const exampleApi = ApiBlueprint.make({
+ name: 'example',
+ params: {
+ factory: createApiFactory({
+ api: exampleApiRef,
+ deps: {},
+ factory: () => new DefaultExampleApi(),
+ }),
+ },
});
// highlight-add-end
/* Omitted definitions for examplePage, exampleNavItem, and rootRouteRef. */
-export const examplePlugin = createPlugin({
+export const examplePlugin = createFrontendPlugin({
id: 'example',
extensions: [
// highlight-add-next-line
@@ -187,26 +195,28 @@ export const examplePlugin = createPlugin({
There are many different plugins that you can extend with additional functionality through extensions. One such plugin is [the catalog plugin](../../features/software-catalog/), one of the core features of Backstage. It lets you catalog the software in your organization, where each item in the catalog has its own page that can be populated with tools and information relating to that catalog entity. In this example we will explore how our plugin can provide such a tool to display on an entity page.
```tsx title="in src/plugin.ts - An example entity content extension"
-import { createEntityContentExtension } from '@backstage/plugin-catalog-react';
+import { EntityContentBlueprint } from '@backstage/plugin-catalog-react/alpha';
// Entity content extensions are similar to page extensions in that they are rendered at a route,
// although they also have a title to support in-line navigation between the different content.
// Just like a page extension the content is lazy loaded, and you can also provide a
// route reference if you want to be able to generate a URL that links to the content.
-const exampleEntityContent = createEntityContentExtension({
- defaultPath: 'example',
- defaultTitle: 'Example',
- loader: () =>
- import('./components/ExampleEntityContent').then(m => (
-
- )),
+const exampleEntityContent = EntityContentBlueprint.make({
+ params: {
+ defaultPath: 'example',
+ defaultTitle: 'Example',
+ loader: () =>
+ import('./components/ExampleEntityContent').then(m => (
+
+ )),
+ },
});
-export const examplePlugin = createPlugin({
+export const examplePlugin = createFrontendPlugin({
id: 'example',
extensions: [
// highlight-add-next-line
- exampleEntityContent
+ exampleEntityContent,
exampleApi,
examplePage,
exampleNavItem,
@@ -219,4 +229,4 @@ export const examplePlugin = createPlugin({
The `ExampleEntityContent` itself is again a regular React component where you can implement any functionality you want. To access the entity that the content is being rendered for, you can use the `useEntity` hook from `@backstage/plugin-catalog-react`. You can see a full list of APIs provided by the catalog React library in [the API reference](../../reference/plugin-catalog-react.md).
-For a more complete list of the different types of extensions that you can create for your plugin, see the [extension types](./03-extension-types.md) section.
+For a more complete list of the different kinds of extensions that you can create for your plugin, see the [extension blueprints](./03-common-extension-blueprints.md) section.
diff --git a/docs/frontend-system/building-plugins/02-testing.md b/docs/frontend-system/building-plugins/02-testing.md
index 26c9503c6d..225c570fbd 100644
--- a/docs/frontend-system/building-plugins/02-testing.md
+++ b/docs/frontend-system/building-plugins/02-testing.md
@@ -41,7 +41,7 @@ describe('Entity details component', () => {
});
```
-To mock [Utility APIs](../architecture/06-utility-apis.md) that are used by your component you can use the `TestApiProvider` to override individual API implementations. In the snippet below, we wrap the component within a `TestApiProvider` in order to mock the catalog client API:
+To mock [Utility APIs](../architecture/33-utility-apis.md) that are used by your component you can use the `TestApiProvider` to override individual API implementations. In the snippet below, we wrap the component within a `TestApiProvider` in order to mock the catalog client API:
```tsx
import React from 'react';
@@ -85,6 +85,8 @@ describe('Entity details component', () => {
});
```
+This pattern also works for many other context providers. An important example is the `EntityProvider` from the `@backstage/plugin-catalog-react` package, which you can use to provide a mocked entity context to the component.
+
## Testing extensions
To facilitate testing of frontend extensions, the `@backstage/frontend-test-utils` package provides a tester class which starts up an entire frontend harness, complete with a number of default features. You can then provide overrides for extensions whose behavior you need to adjust for the test run.
@@ -93,7 +95,7 @@ A number of features (frontend extensions and overrides) are also accepted by th
### Single extension
-In order to test an extension in isolation, you simply need to pass it into the tester factory, then call the render method on the returned instance:
+In order to test an extension in isolation, you can use `createExtensionTester` to create a tester instance and access the element that the extension outputs. This element can then be rendered as usual with `renderInTestApp`:
```tsx
import { screen } from '@testing-library/react';
@@ -101,90 +103,49 @@ import { createExtensionTester } from '@backstage/frontend-test-utils';
import { indexPageExtension } from './plugin';
describe('Index page', () => {
- it('should render a the index page', () => {
- createExtensionTester(indexPageExtension).render();
+ it('should render a the index page', async () => {
+ await renderInTestApp(
+ createExtensionTester(indexPageExtension).reactElement(),
+ );
expect(screen.getByText('Index Page')).toBeInTheDocument();
});
});
```
-### Extension preset
+This pattern also allows you to wrap the extension with context providers, such as the `TestApiProvider` that was introduced [above](#testing-react-components).
-There are some extensions that rely on other extensions existence, such as a page that links to another page. In that case, you can add more than one extension to the preset of features you want to render in the test, as shown below:
+Note that the `.reactElement()` method will look for the `coreExtensionData.reactElement` data in the extension outputs. If that doesn't exist and the extension outputs something else that you want to test, you can access the output data using the `.get(dataRef)` method instead.
+
+### Multiple extensions
+
+In some cases you might need to test multiple extensions together, in particular when testing inputs. In this case, you can add more extensions to the tester instance using the `.add(...)` method. It also accepts an optional options object as the second argument, which you can use to provide configuration for the extension instance.
```tsx
import { screen } from '@testing-library/react';
import userEvent from '@testing-library/user-event';
import { createExtensionTester } from '@backstage/frontend-test-utils';
-import { indexPageExtension, detailsPageExtension } from './plugin';
+import { indexPageExtension, indexPageHeader } from './plugin';
describe('Index page', async () => {
- it('should link to the details page', () => {
- createExtensionTester(indexPageExtension)
- // Adding more extensions to the preset being tested
- .add(detailsPageExtension)
- .render();
+ it('should link to the index page with header', async () => {
+ const tester = createExtensionTester(indexPageExtension)
+ // Adding the header to be rendered on the index page
+ .add(indexPageHeader);
- await expect(screen.findByText('Index Page')).toBeInTheDocument();
+ await renderInTestApp(tester.reactElement());
- await userEvent.click(screen.getByRole('link', { name: 'See details' }));
+ await expect(screen.findByText('Index page')).toBeInTheDocument();
+ await expect(screen.findByText('Index page header')).toBeInTheDocument();
- await expect(
- screen.findByText('Details Page'),
- ).resolves.toBeInTheDocument();
+ expect(
+ tester.query(indexPageHeader).get(headerDataRef),
+ ).toMatchObject(/* ... */);
});
});
```
-### Mocking apis
-
-If your extensions requires implementation of APIs that aren't wired up by default, you'll have to add overrides to the preset of features being tested:
-
-```tsx
-import { screen } from '@testing-library/react';
-import userEvent from '@testing-library/user-event';
-import { createApiFactory } from '@backestage/core-plugin-api';
-import {
- createExtensionOverrides,
- configApiRef,
- analyticsApiRef,
-} from '@backstage/frontend-plugin-api';
-import {
- createExtensionTester,
- MockConfigApi,
- MockAnalyticsApi,
-} from '@backstage/frontend-test-utils';
-import { indexPageExtension } from './plugin';
-
-describe('Index page', () => {
- it('should capture click events in analytics', async () => {
- // Mocking the analytics api implementation
- const analyticsApiMock = new MockAnalyticsApi();
-
- const analyticsApiOverride = createApiExtension({
- factory: createApiFactory({
- api: analyticsApiRef,
- factory: () => analyticsApiMock,
- }),
- });
-
- createExtensionTester(indexPageExtension)
- // Overriding the analytics api extension
- .add(analyticsApiOverride)
- .render();
-
- await userEvent.click(
- await screen.findByRole('link', { name: 'See details' }),
- );
-
- expect(analyticsApiMock.getEvents()[0]).toMatchObject({
- action: 'click',
- subject: 'See details',
- });
- });
-});
-```
+When testing multiple extensions you may sometimes want to access the output of other extensions than the main test subject. You can use the `.query(ext)` method to query a different extension that has been added to the tester, by passing the extension used with the `createExtensionTester(...).add(ext)`
### Setting configuration
@@ -198,36 +159,26 @@ import { indexPageExtension, detailsPageExtension } from './plugin';
describe('Index page', () => {
it('should accepts a custom title via config', async () => {
- createExtensionTester(indexPageExtension, {
- // Configuration specific of index page
- config: { title: 'Custom index' },
- })
- .add(detailsExtensionPage, {
- // Configuration specific of details page
- config: { title: 'Custom details' },
- })
- .render({
- // Configuration specific of the instance
- config: {
- app: {
- title: 'Custom app',
- },
+ const tester = createExtensionTester(indexPageExtension, {
+ // Extension configuration for the index page
+ config: { title: 'Custom page' },
+ }).add(indexPageHeader, {
+ // Extension configuration for the index page header
+ config: { title: 'Custom page header' },
+ });
+
+ await renderInTestApp(tester.reactElement(), {
+ // Global configuration for the app
+ config: {
+ app: {
+ title: 'Custom app',
},
- });
+ },
+ });
- await expect(
- screen.findByRole('heading', { name: 'Custom app' }),
- ).resolves.toBeInTheDocument();
-
- await expect(
- screen.findByRole('heading', { name: 'Custom index' }),
- ).resolves.toBeInTheDocument();
-
- await userEvent.click(screen.getByRole('link', { name: 'See details' }));
-
- await expect(
- screen.findByText('Custom details'),
- ).resolves.toBeInTheDocument();
+ await expect(screen.findByText('Custom app')).toBeInTheDocument();
+ await expect(screen.findByText('Custom page')).toBeInTheDocument();
+ await expect(screen.findByText('Custom page header')).toBeInTheDocument();
});
});
```
diff --git a/docs/frontend-system/building-plugins/03-extension-types.md b/docs/frontend-system/building-plugins/03-common-extension-blueprints.md
similarity index 64%
rename from docs/frontend-system/building-plugins/03-extension-types.md
rename to docs/frontend-system/building-plugins/03-common-extension-blueprints.md
index 1f3baaa710..5193fd85b1 100644
--- a/docs/frontend-system/building-plugins/03-extension-types.md
+++ b/docs/frontend-system/building-plugins/03-common-extension-blueprints.md
@@ -1,40 +1,40 @@
---
-id: extension-types
-title: Frontend System Extension Types
-sidebar_label: Extension Types
+id: common-extension-blueprints
+title: Common Extension Blueprints
+sidebar_label: Common Extension Blueprints
# prettier-ignore
-description: Extension types provided by the frontend system and core features
+description: Extension blueprints provided by the frontend system and core features
---
> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
-This section covers many of the [extension types](../architecture/03-extensions.md#extension-creators) available at your disposal when building Backstage frontend plugins.
+This section covers many of the [extension blueprints](../architecture/23-extension-blueprints.md) available at your disposal when building Backstage frontend plugins.
-## Built-in extension types
+## Built-in extension blueprints
-These are the extension types provided by the Backstage frontend framework itself.
+These are the [extension blueprints](../architecture/23-extension-blueprints.md) provided by the Backstage frontend framework itself.
-### Api - [Reference](../../reference/frontend-plugin-api.createapiextension.md)
+### Api - [Reference](../../reference/frontend-plugin-api.apiblueprint.md)
An API extension is used to add or override [Utility API factories](../utility-apis/01-index.md) in the app. They are commonly used by plugins for both internal and shared APIs. There are also many built-in Api extensions provided by the framework that you are able to override.
### Component - [Reference](../../reference/frontend-plugin-api.createcomponentextension.md)
-Components extensions are used to override the component associated with a component reference throughout the app.
+Components extensions are used to override the component associated with a component reference throughout the app. This uses an extension creator function rather than a blueprint, but will likely be migrated to a blueprint in the future.
-### NavItem - [Reference](../../reference/frontend-plugin-api.createnavitemextension.md)
+### NavItem - [Reference](../../reference/frontend-plugin-api.navitemblueprint.md)
Navigation item extensions are used to provide menu items that link to different parts of the app. By default nav items are attached to the app nav extension, which by default is rendered as the left sidebar in the app.
-### Page - [Reference](../../reference/frontend-plugin-api.createpageextension.md)
+### Page - [Reference](../../reference/frontend-plugin-api.pageblueprint.md)
Page extensions provide content for a particular route in the app. By default pages are attached to the app routes extensions, which renders the root routes.
-### SignInPage - [Reference](../../reference/frontend-plugin-api.createsigninpageextension.md)
+### SignInPage - [Reference](../../reference/frontend-plugin-api.signinpageblueprint.md)
Sign-in page extension have a single purpose - to implement a custom sign-in page. They are always attached to the app root extension and are rendered before the rest of the app until the user is signed in.
-### Theme - [Reference](../../reference/frontend-plugin-api.createthemeextension.md)
+### Theme - [Reference](../../reference/frontend-plugin-api.themeblueprint.md)
Theme extensions provide custom themes for the app. They are always attached to the app extension and you can have any number of themes extensions installed in an app at once, letting the user choose which theme to use.
@@ -42,22 +42,22 @@ Theme extensions provide custom themes for the app. They are always attached to
Icon bundle extensions provide the ability to replace or provide new icons to the app. You can use the above blueprint to make new extension instances which can be installed into the app.
-### Translation - [Reference](../../reference/frontend-plugin-api.createtranslationextension.md)
+### Translation - [Reference](../../reference/frontend-plugin-api.translationblueprint.md)
Translation extension provide custom translation messages for the app. They can be used both to override the default english messages to custom ones, as well as provide translations for additional languages.
-## Core feature extension types
+## Core feature extension blueprints
-These are the extension types provided by the Backstage core feature plugins.
+These are the [extension blueprints](../architecture/23-extension-blueprints.md) provided by the Backstage core feature plugins.
### EntityCard - [Reference](https://github.com/backstage/backstage/blob/master/plugins/catalog-react/api-report-alpha.md)
-Creates entity cards to be displayed on the entity pages of the catalog plugin.
+Creates entity cards to be displayed on the entity pages of the catalog plugin. Exported as `EntityCardBlueprint`.
### EntityContent - [Reference](https://github.com/backstage/backstage/blob/master/plugins/catalog-react/api-report-alpha.md)
-Creates entity content to be displayed on the entity pages of the catalog plugin.
+Creates entity content to be displayed on the entity pages of the catalog plugin. Exported as `EntityContentBlueprint`.
### SearchResultListItem - [Reference](https://github.com/backstage/backstage/blob/master/plugins/search-react/api-report-alpha.md)
-Creates search result list items for different types of search results, to be displayed in search result lists.
+Creates search result list items for different types of search results, to be displayed in search result lists. Exported as `SearchResultListItemBlueprint`.
diff --git a/docs/frontend-system/building-plugins/04-built-in-data-refs.md b/docs/frontend-system/building-plugins/04-built-in-data-refs.md
index dacbbf30f1..a26f6549b7 100644
--- a/docs/frontend-system/building-plugins/04-built-in-data-refs.md
+++ b/docs/frontend-system/building-plugins/04-built-in-data-refs.md
@@ -8,7 +8,7 @@ description: Configuring or overriding built-in extension data references
> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
-To have a better understanding of extension data references please read [the corresponding architecture section](../architecture/03-extensions.md#extension-data) first.
+To have a better understanding of extension data references please read [the corresponding architecture section](../architecture/20-extensions.md#extension-data) first.
## Built-in extension data references
@@ -24,18 +24,15 @@ The `reactElement` data reference can be used for defining the extension input/o
```tsx
import {
+ createExtension,
coreExtensionData,
- createExtensionInput,
- createPageExtension,
} from '@backstage/frontend-plugin-api';
-const homePage = createPageExtension({
- defaultPath: '/home',
- routeRef: rootRouteRef,
- inputs: {
- props: createExtensionInput({
- children: coreExtensionData.reactElement.optional(),
- }),
+const examplePage = createExtension({
+ name: 'example',
+ output: [coreExtensionData.reactElement],
+ factor() {
+ return [coreExtensionData.reactElement(
Example
)];
},
});
```
diff --git a/docs/frontend-system/building-plugins/05-migrating.md b/docs/frontend-system/building-plugins/05-migrating.md
index 16f465ece7..f0abc97c81 100644
--- a/docs/frontend-system/building-plugins/05-migrating.md
+++ b/docs/frontend-system/building-plugins/05-migrating.md
@@ -8,16 +8,16 @@ description: How to migrate an existing frontend plugin to the new frontend syst
This guide allows you to migrate a frontend plugin and its own components, routes, apis to the new frontend system.
-The main concept is that routes, components, apis are now extensions. You can use the appropriate extension creators to migrate all of them to extensions.
+The main concept is that routes, components, apis are now extensions. You can use the appropriate [extension blueprints](../architecture/23-extension-blueprints.md) to migrate all of them to extensions.
## Migrating the plugin
In the legacy frontend system a plugin was defined in its own `plugin.ts` file as following:
```ts title="my-plugin/src/plugin.ts"
- import { createPlugin } from '@backstage/core-plugin-api';
+ import { createFrontendPlugin } from '@backstage/core-plugin-api';
- export const myPlugin = createPlugin({
+ export const myPlugin = createFrontendPlugin({
id: 'my-plugin',
apis: [],
routes: {
@@ -29,13 +29,13 @@ In the legacy frontend system a plugin was defined in its own `plugin.ts` file a
});
```
-In order to migrate the actual definition of the plugin you need to recreate the plugin using the new `createPlugin` utility exported by `@backstage/frontend-plugin-api`.
-The new `createPlugin` function doesn't accept apis anymore as apis are now extensions.
+In order to migrate the actual definition of the plugin you need to recreate the plugin using the new `createFrontendPlugin` utility exported by `@backstage/frontend-plugin-api`.
+The new `createFrontendPlugin` function doesn't accept apis anymore as apis are now extensions.
```ts title="my-plugin/src/alpha.ts"
- import { createPlugin } from '@backstage/frontend-plugin-api';
+ import { createFrontendPlugin } from '@backstage/frontend-plugin-api';
- export default createPlugin({
+ export default createFrontendPlugin({
id: 'my-plugin',
// bind all the extensions to the plugin
/* highlight-next-line */
@@ -77,7 +77,7 @@ The code above binds all the extensions to the plugin. _Important_: Make sure to
## Migrating Pages
-Pages that were previously created using the `createRoutableExtension` extension function can be migrated to the new Frontend System using the `createPageExtension` extension creator, exported by `@backstage/frontend-plugin-api`.
+Pages that were previously created using the `createRoutableExtension` extension function can be migrated to the new Frontend System using the `PageBlueprint` [extension blueprint](../architecture/23-extension-blueprints.md), exported by `@backstage/frontend-plugin-api`.
For example, given the following page:
@@ -94,33 +94,35 @@ export const FooPage = fooPlugin.provide(
it can be migrated as the following:
```tsx
-import { createPageExtension } from '@backstage/frontend-plugin-api';
+import { PageBlueprint } from '@backstage/frontend-plugin-api';
import {
compatWrapper,
convertLegacyRouteRef,
} from '@backstage/core-compat-api';
-const fooPage = createPageExtension({
- defaultPath: '/foo',
- // you can reuse the existing routeRef
- // by wrapping into the convertLegacyRouteRef.
- routeRef: convertLegacyRouteRef(rootRouteRef),
- // these inputs usually match the props required by the component.
- loader: ({ inputs }) =>
- import('./components/').then(m =>
- // The compatWrapper utility allows you to use the existing
- // legacy frontend utilities used internally by the components.
- compatWrapper(),
- ),
+const fooPage = PageBlueprint.make({
+ params: {
+ defaultPath: '/foo',
+ // you can reuse the existing routeRef
+ // by wrapping into the convertLegacyRouteRef.
+ routeRef: convertLegacyRouteRef(rootRouteRef),
+ // these inputs usually match the props required by the component.
+ loader: ({ inputs }) =>
+ import('./components/').then(m =>
+ // The compatWrapper utility allows you to use the existing
+ // legacy frontend utilities used internally by the components.
+ compatWrapper(),
+ ),
+ },
});
```
-then add the `fooPage` extension to the plugin:
+Then add the `fooPage` extension to the plugin:
```ts title="my-plugin/src/alpha.ts"
- import { createPlugin } from '@backstage/frontend-plugin-api';
+ import { createFrontendPlugin } from '@backstage/frontend-plugin-api';
- export default createPlugin({
+ export default createFrontendPlugin({
id: 'my-plugin',
// bind all the extensions to the plugin
/* highlight-remove-next-line */
@@ -133,7 +135,7 @@ then add the `fooPage` extension to the plugin:
## Migrating Components
-The equivalent utility to replace components created with `createComponentExtension` is `createExtension` from `@backstage/frontend-plugin-api`. However, we recommend searching for a more appropriate extension creator first.
+The equivalent utility to replace components created with `createComponentExtension` depends on the context within which the component is used, typically indicated by the naming pattern of the export. Many of these can be migrated to one of the [existing blueprints](03-common-extension-blueprints.md), but in rare cases it may be necessary to use [`createExtension`](../architecture/20-extensions.md#creating-an-extension) directly.
## Migrating APIs
@@ -182,7 +184,7 @@ const exampleWorkApi = createApiFactory({
The major changes we'll make are
- Change the old `@backstage/core-plugin-api` imports to the new `@backstage/frontend-plugin-api` package as per the top section of this guide
-- Wrap the existing API factory in a `createApiExtension`
+- Wrap the existing API factory in a `ApiBlueprint`
The end result, after simplifying imports and cleaning up a bit, might look like this:
@@ -190,26 +192,28 @@ The end result, after simplifying imports and cleaning up a bit, might look like
import {
storageApiRef,
createApiFactory,
- createApiExtension,
+ ApiBlueprint,
} from '@backstage/frontend-plugin-api';
import { workApiRef } from '@internal/plugin-example-react';
import { WorkImpl } from './WorkImpl';
-const exampleWorkApi = createApiExtension({
- factory: createApiFactory({
- api: workApiRef,
- deps: { storageApi: storageApiRef },
- factory: ({ storageApi }) => new WorkImpl({ storageApi }),
- }),
+const exampleWorkApi = ApiBlueprint.make({
+ params: {
+ factory: createApiFactory({
+ api: workApiRef,
+ deps: { storageApi: storageApiRef },
+ factory: ({ storageApi }) => new WorkImpl({ storageApi }),
+ }),
+ },
});
```
Finally, let's add the `exampleWorkApi` extension to the plugin:
```ts title="my-plugin/src/alpha.ts"
- import { createPlugin } from '@backstage/frontend-plugin-api';
+ import { createFrontendPlugin } from '@backstage/frontend-plugin-api';
- export default createPlugin({
+ export default createFrontendPlugin({
id: 'my-plugin',
// bind all the extensions to the plugin
/* highlight-remove-next-line */
diff --git a/docs/frontend-system/utility-apis/01-index.md b/docs/frontend-system/utility-apis/01-index.md
index 37120a5152..07f7dcc2a8 100644
--- a/docs/frontend-system/utility-apis/01-index.md
+++ b/docs/frontend-system/utility-apis/01-index.md
@@ -8,7 +8,7 @@ description: Working with Utility APIs in the New Frontend System
> **NOTE: The new frontend system is in alpha and is only supported by a small number of plugins.**
-As described [in the architecture section](../architecture/06-utility-apis.md), utility APIs are pieces of shared functionality - interfaces that can be requested by plugins to use. They are defined by a TypeScript interface as well as a reference (an "API ref") used to access its implementation. They can be provided both by plugins and the core framework, and are themselves [extensions](../architecture/03-extensions.md) that can accept inputs, be declaratively configured in your app-config, or transparently be replaced entirely with custom implementations that fulfill the same contract.
+As described [in the architecture section](../architecture/33-utility-apis.md), utility APIs are pieces of shared functionality - interfaces that can be requested by plugins to use. They are defined by a TypeScript interface as well as a reference (an "API ref") used to access its implementation. They can be provided both by plugins and the core framework, and are themselves [extensions](../architecture/20-extensions.md) that can accept inputs, be declaratively configured in your app-config, or transparently be replaced entirely with custom implementations that fulfill the same contract.
## Creating utility APIs
diff --git a/docs/frontend-system/utility-apis/02-creating.md b/docs/frontend-system/utility-apis/02-creating.md
index fcb7ff1a65..01c21fe656 100644
--- a/docs/frontend-system/utility-apis/02-creating.md
+++ b/docs/frontend-system/utility-apis/02-creating.md
@@ -45,9 +45,9 @@ The plugin itself now wants to provide this API and its default implementation,
```tsx title="in @internal/plugin-example"
import {
- createApiExtension,
+ ApiBlueprint,
createApiFactory,
- createPlugin,
+ createFrontendPlugin,
storageApiRef,
StorageApi,
} from '@backstage/frontend-plugin-api';
@@ -62,21 +62,24 @@ class WorkImpl implements WorkApi {
}
}
-const exampleWorkApi = createApiExtension({
- factory: createApiFactory({
- api: workApiRef,
- deps: { storageApi: storageApiRef },
- factory: ({ storageApi }) => {
- return new WorkImpl({ storageApi });
- },
- }),
+const workApi = ApiBlueprint.make({
+ name: 'work',
+ params: {
+ factory: createApiFactory({
+ api: workApiRef,
+ deps: { storageApi: storageApiRef },
+ factory: ({ storageApi }) => {
+ return new WorkImpl({ storageApi });
+ },
+ }),
+ },
});
/**
* The Example plugin.
* @public
*/
-export default createPlugin({
+export default createFrontendPlugin({
id: 'example',
extensions: [exampleWorkApi],
});
@@ -86,43 +89,37 @@ For illustration we make a skeleton implementation class and the API extension a
The code also illustrates how the API factory declares a dependency on another utility API - the core storage API in this case. An instance of that utility API is then provided to the factory function.
-The resulting extension ID of the work API will be the kind `api:` followed by the plugin ID as the namespace, in this case ending up as `api:plugin.example.work`. Check out [the naming patterns doc](../architecture/08-naming-patterns.md) for more information on how this works. You can now use this ID to refer to the API in app-config and elsewhere.
+The extension ID of the work API will be the kind `api:` followed by the plugin ID as the namespace, a `/` separator, and lastly the name we used of the extension. In this case we end up with `api:example/work`. Check out [the naming patterns doc](../architecture/50-naming-patterns.md) for more information on how this works. You can now use this ID to refer to the API in app-config and elsewhere. In case there is a single API that is a central to the functionality of the plugin, most typically an API client, you can choose to omit the name of the extension so that you end up with just `api:`.
## Adding configurability
-Here we will describe how to amend a utility API with the capability of having extension config, which is driven by [your app-config](../../conf/writing.md). You do this by giving an extension config schema to your API extension factory function. Let's make the required additions to our original work example API.
+Here we will describe how to amend a utility API with the capability of having extension config, which is driven by [your app-config](../../conf/writing.md). You do this by giving an extension config schema to your API extension factory function. Let's refactory the example above to also accept configuration, which will require us to use the [override method of the blueprint](../architecture/23-extension-blueprints.md#creating-an-extension-from-a-blueprint-with-overrides).
```tsx title="in @internal/plugin-example"
-/* highlight-add-next-line */
-import { createSchemaFromZod } from '@backstage/frontend-plugin-api';
-
-const exampleWorkApi = createApiExtension({
- /* highlight-add-start */
- api: workApiRef,
- configSchema: createSchemaFromZod(z =>
- z.object({
- goSlow: z.boolean().default(false),
- }),
- ),
- /* highlight-add-end */
- /* highlight-remove-next-line */
- factory: createApiFactory({
- /* highlight-add-next-line */
- factory: ({ config }) => createApiFactory({
- api: workApiRef,
- deps: { storageApi: storageApiRef },
- factory: ({ storageApi }) => {
- /* highlight-add-start */
- if (config.goSlow) {
- /* ... */
- }
- /* highlight-add-end */
+const exampleWorkApi = ApiBlueprint.makeWithOverrides({
+ config: {
+ schema: {
+ goSlow: z => z.boolean().default(false),
},
- }),
+ },
+ factory(originalFactory, { config }) {
+ return originalFactory({
+ factory: createApiFactory({
+ api: workApiRef,
+ deps: { storageApi: storageApiRef },
+ factory: ({ storageApi }) => {
+ return new WorkImpl({
+ storageApi,
+ goSlow: config.goSlow,
+ });
+ },
+ }),
+ });
+ },
});
```
-We wanted users to be able to set a `goSlow` extension config parameter for our API instances. So we passed in a `configSchema` to `createApiExtension` which matches that interface. This example builds it using [the zod library](https://zod.dev/). The actual extension config values will then be passed in a type safe manner in to the `factory` which is now a callback, wherein we can do what we wish with them. When changing to the callback form, we also had to add a top level `api: workApiRef` under `createApiExtension`.
+We wanted users to be able to set a `goSlow` extension config parameter for our API instances, which we declared in our new configuration schema. The actual extension config values will then be passed in a type safe manner in to the blueprint `factory`, wherein we can use them to create our API factory and pass as our blueprint parameters.
Note that the expression "extension config" as used here, is _not_ the same thing as the `configApi` which gives you access to the full app-config. The extension config discussed here is instead the particular configuration settings given to your utility API instance. This is discussed more [in the Configuring section](./04-configuring.md).
@@ -130,11 +127,11 @@ Note also that the extension config schema contained a default value fo the `goS
## Adding inputs
-Inputs are added to Utility APIs in the same way as other extension types:
+Inputs are added to Utility APIs in the same way as other extension blueprints:
-- Declaring a set of `inputs` on your extension
-- If needed, create custom extension data types to be used in those inputs
-- If needed, export an extension creator function for creating that particular attachment type
+- Use `.makeWithOverrides` and declare a set of `inputs` for your extension.
+- If needed, create custom extension data types to be used in those inputs.
+- If needed, create and export an [extension blueprint](../architecture/23-extension-blueprints.md#creating-an-extension-blueprint) for creating that particular attachment type.
This is a power use case and not very commonly used.
diff --git a/docs/frontend-system/utility-apis/03-consuming.md b/docs/frontend-system/utility-apis/03-consuming.md
index 5c53c8617e..bdf3b8dcdb 100644
--- a/docs/frontend-system/utility-apis/03-consuming.md
+++ b/docs/frontend-system/utility-apis/03-consuming.md
@@ -46,23 +46,25 @@ Your utility APIs can depend on other utility APIs in their factories. You do th
```tsx
import {
configApiRef,
- createApiExtension,
+ ApiBlueprint,
createApiFactory,
discoveryApiRef,
} from '@backstage/frontend-plugin-api';
import { MyApiImpl } from './MyApiImpl';
-const myApi = createApiExtension({
- factory: createApiFactory({
- api: myApiRef,
- deps: {
- configApi: configApiRef,
- discoveryApi: discoveryApiRef,
- },
- factory: ({ configApi, discoveryApi }) => {
- return new MyApiImpl({ configApi, discoveryApi });
- },
- }),
+const myApi = ApiBlueprint.make({
+ params: {
+ factory: createApiFactory({
+ api: myApiRef,
+ deps: {
+ configApi: configApiRef,
+ discoveryApi: discoveryApiRef,
+ },
+ factory: ({ configApi, discoveryApi }) => {
+ return new MyApiImpl({ configApi, discoveryApi });
+ },
+ }),
+ },
});
```
diff --git a/docs/frontend-system/utility-apis/04-configuring.md b/docs/frontend-system/utility-apis/04-configuring.md
index 7acf23decf..e403104506 100644
--- a/docs/frontend-system/utility-apis/04-configuring.md
+++ b/docs/frontend-system/utility-apis/04-configuring.md
@@ -12,7 +12,7 @@ Utility APIs are extensions and can therefore optionally be amended with configu
## Configuring
-To configure your Utility API extension, first you'll need to know its ID. That ID is formed from the API ref ID; check [the naming patterns docs](../architecture/08-naming-patterns.md) for details.
+To configure your Utility API extension, first you'll need to know its ID. That ID is formed from the API ref ID; check [the naming patterns docs](../architecture/50-naming-patterns.md) for details.
Our example work API from [the creating section](./02-creating.md) would have the ID `api:plugin.example.work`. You configure it and all other extensions under the `app.extensions` section of your app-config.
@@ -37,7 +37,7 @@ Well written input-enabled extension often have extension creator functions that
## Replacing a Utility API implementation
-Like with other extension types, you replace Utility APIs with your own custom implementation using [extension overrides](../architecture/05-extension-overrides.md).
+Like with other extension types, you replace Utility APIs with your own custom implementation using [extension overrides](../architecture/25-extension-overrides.md).
```tsx title="in your app"
/* highlight-add-start */
@@ -49,13 +49,13 @@ class CustomWorkImpl implements WorkApi {
const myOverrides = createExtensionOverrides({
extensions: [
- createApiExtension({
- api: workApiRef,
- factory: () =>
- createApiFactory({
+ ApiBlueprint.make({
+ params: {
+ factory: createApiFactory({
api: workApiRef,
factory: () => new CustomWorkImpl(),
}),
+ },
}),
],
});
diff --git a/docs/integrations/aws-s3/discovery--old.md b/docs/integrations/aws-s3/discovery--old.md
index 09b6eb6cc0..3a9d30a370 100644
--- a/docs/integrations/aws-s3/discovery--old.md
+++ b/docs/integrations/aws-s3/discovery--old.md
@@ -36,7 +36,7 @@ catalog:
bucketName: sample-bucket
prefix: prefix/ # optional
region: us-east-2 # optional, uses the default region otherwise
- schedule: # same options as in TaskScheduleDefinition
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
@@ -56,7 +56,7 @@ catalog:
bucketName: sample-bucket
prefix: prefix/ # optional
region: us-east-2 # optional, uses the default region otherwise
- schedule: # same options as in TaskScheduleDefinition
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
diff --git a/docs/integrations/aws-s3/discovery.md b/docs/integrations/aws-s3/discovery.md
index db9119680e..4cca448cf2 100644
--- a/docs/integrations/aws-s3/discovery.md
+++ b/docs/integrations/aws-s3/discovery.md
@@ -36,7 +36,7 @@ catalog:
bucketName: sample-bucket
prefix: prefix/ # optional
region: us-east-2 # optional, uses the default region otherwise
- schedule: # same options as in TaskScheduleDefinition
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
@@ -56,7 +56,7 @@ catalog:
bucketName: sample-bucket
prefix: prefix/ # optional
region: us-east-2 # optional, uses the default region otherwise
- schedule: # same options as in TaskScheduleDefinition
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
diff --git a/docs/integrations/azure/discovery--old.md b/docs/integrations/azure/discovery--old.md
index 56a2fe559f..27532fe6ee 100644
--- a/docs/integrations/azure/discovery--old.md
+++ b/docs/integrations/azure/discovery--old.md
@@ -45,7 +45,7 @@ catalog:
project: myproject
repository: service-* # this will match all repos starting with service-*
path: /catalog-info.yaml
- schedule: # optional; same options as in TaskScheduleDefinition
+ schedule: # optional; same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
diff --git a/docs/integrations/azure/discovery.md b/docs/integrations/azure/discovery.md
index c8a8a3af7c..357df7d553 100644
--- a/docs/integrations/azure/discovery.md
+++ b/docs/integrations/azure/discovery.md
@@ -45,7 +45,7 @@ catalog:
project: myproject
repository: service-* # this will match all repos starting with service-*
path: /catalog-info.yaml
- schedule: # optional; same options as in TaskScheduleDefinition
+ schedule: # optional; same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
diff --git a/docs/integrations/bitbucketCloud/discovery.md b/docs/integrations/bitbucketCloud/discovery.md
index 04dc111d30..6ba9c0aa1f 100644
--- a/docs/integrations/bitbucketCloud/discovery.md
+++ b/docs/integrations/bitbucketCloud/discovery.md
@@ -146,7 +146,7 @@ catalog:
filters: # optional
projectKey: '^apis-.*$' # optional; RegExp
repoSlug: '^service-.*$' # optional; RegExp
- schedule: # same options as in TaskScheduleDefinition
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
diff --git a/docs/integrations/bitbucketServer/discovery.md b/docs/integrations/bitbucketServer/discovery.md
index 99e04affa8..133978a8fb 100644
--- a/docs/integrations/bitbucketServer/discovery.md
+++ b/docs/integrations/bitbucketServer/discovery.md
@@ -63,7 +63,7 @@ catalog:
projectKey: '^apis-.*$' # optional; RegExp
repoSlug: '^service-.*$' # optional; RegExp
skipArchivedRepos: true # optional; boolean
- schedule: # same options as in TaskScheduleDefinition
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
diff --git a/docs/integrations/datadog-rum/installation.md b/docs/integrations/datadog-rum/installation.md
index 4dc6c24134..6659bec182 100644
--- a/docs/integrations/datadog-rum/installation.md
+++ b/docs/integrations/datadog-rum/installation.md
@@ -28,6 +28,51 @@ app:
If your [`app-config.yaml`](https://github.com/backstage/backstage/blob/e0506af8fc54074a160fb91c83d6cae8172d3bb3/app-config.yaml#L5) file does not have this configuration, you may have to adjust your [`packages/app/public/index.html`](https://github.com/backstage/backstage/blob/e0506af8fc54074a160fb91c83d6cae8172d3bb3/packages/app/public/index.html#L69) to include the Datadog RUM `init()` section manually.
+Please note that the env value MUST be specified at build time
+
+:::note
+In case after a proper configuration, the events still are not being captured: Copy and paste this section in to your `packages/app/public/index.html` under the `` tag.
+
+```html
+<% if (config.has('app.datadogRum')) { %>
+
+<% } %>
+```
+
The `clientToken` and `applicationId` are generated from the Datadog RUM page
following
[these instructions](https://docs.datadoghq.com/real_user_monitoring/browser/).
diff --git a/docs/integrations/github/discovery--old.md b/docs/integrations/github/discovery--old.md
index 752aa51bde..901462b1cb 100644
--- a/docs/integrations/github/discovery--old.md
+++ b/docs/integrations/github/discovery--old.md
@@ -133,7 +133,7 @@ catalog:
filters:
branch: 'main' # string
repository: '.*' # Regex
- schedule: # same options as in TaskScheduleDefinition
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
@@ -249,7 +249,7 @@ schedule:
timeout: { minutes: 3 }
```
-More information about scheduling can be found on the [TaskScheduleDefinition](https://backstage.io/docs/reference/backend-tasks.taskscheduledefinition) page.
+More information about scheduling can be found on the [SchedulerServiceTaskScheduleDefinition](https://backstage.io/docs/reference/backend-plugin-api.schedulerservicetaskscheduledefinition) page.
Alternatively, or additionally, you can configure [github-apps](github-apps.md) authentication
which carries a much higher rate limit at GitHub.
diff --git a/docs/integrations/github/discovery.md b/docs/integrations/github/discovery.md
index 43e63a618c..b2e998813d 100644
--- a/docs/integrations/github/discovery.md
+++ b/docs/integrations/github/discovery.md
@@ -83,7 +83,7 @@ catalog:
filters:
branch: 'main' # string
repository: '.*' # Regex
- schedule: # same options as in TaskScheduleDefinition
+ schedule: # same options as in SchedulerServiceTaskScheduleDefinition
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
@@ -203,7 +203,7 @@ schedule:
timeout: { minutes: 3 }
```
-More information about scheduling can be found on the [TaskScheduleDefinition](https://backstage.io/docs/reference/backend-tasks.taskscheduledefinition) page.
+More information about scheduling can be found on the [SchedulerServiceTaskScheduleDefinition](https://backstage.io/docs/reference/backend-plugin-api.schedulerservicetaskscheduledefinition) page.
Alternatively, or additionally, you can configure [github-apps](github-apps.md) authentication
which carries a much higher rate limit at GitHub.
diff --git a/docs/integrations/github/org.md b/docs/integrations/github/org.md
index 18865cd630..61e42567a9 100644
--- a/docs/integrations/github/org.md
+++ b/docs/integrations/github/org.md
@@ -94,7 +94,7 @@ Directly under the `githubOrg` is a list of configurations, each entry is a stru
- `id`: A stable id for this provider. Entities from this provider will be associated with this ID, so you should take care not to change it over time since that may lead to orphaned entities and/or conflicts.
- `githubUrl`: The target that this provider should consume
- `orgs` (optional): The list of the GitHub orgs to consume. If you only list a single org the generated group entities will use the `default` namespace, otherwise they will use the org name as the namespace. By default the provider will consume all accessible orgs on the given GitHub instance (support for GitHub App integration only).
-- `schedule`: The refresh schedule to use, matches the structure of [`TaskScheduleDefinitionConfig`](https://backstage.io/docs/reference/backend-tasks.taskscheduledefinitionconfig/)
+- `schedule`: The refresh schedule to use, matches the structure of [`SchedulerServiceTaskScheduleDefinitionConfig`](https://backstage.io/docs/reference/backend-plugin-api.schedulerservicetaskscheduledefinitionconfig/)
### Events Support
diff --git a/docs/integrations/gitlab/discovery.md b/docs/integrations/gitlab/discovery.md
index 70f12f181e..79bd37061a 100644
--- a/docs/integrations/gitlab/discovery.md
+++ b/docs/integrations/gitlab/discovery.md
@@ -154,7 +154,7 @@ catalog:
entityFilename: catalog-info.yaml # Optional. Defaults to `catalog-info.yaml`
projectPattern: '[\s\S]*' # Optional. Filters found projects based on provided patter. Defaults to `[\s\S]*`, which means to not filter anything
excludeRepos: [] # Optional. A list of project paths that should be excluded from discovery, e.g. group/subgroup/repo. Should not start or end with a slash.
- schedule: # Same options as in TaskScheduleDefinition. Optional for the Legacy Backend System
+ schedule: # Same options as in SchedulerServiceTaskScheduleDefinition. Optional for the Legacy Backend System
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
diff --git a/docs/integrations/gitlab/org.md b/docs/integrations/gitlab/org.md
index 65f66aa763..24b64d1116 100644
--- a/docs/integrations/gitlab/org.md
+++ b/docs/integrations/gitlab/org.md
@@ -173,7 +173,7 @@ catalog:
group: org/teams # Required for gitlab.com when `orgEnabled: true`. Optional for self managed. Must not end with slash. Accepts only groups under the provided path (which will be stripped)
allowInherited: true # Allow groups to be ingested even if there are no direct members.
groupPattern: '[\s\S]*' # Optional. Filters found groups based on provided pattern. Defaults to `[\s\S]*`, which means to not filter anything
- schedule: # Same options as in TaskScheduleDefinition. Optional for the Legacy Backend System.
+ schedule: # Same options as in SchedulerServiceTaskScheduleDefinition. Optional for the Legacy Backend System.
# supports cron, ISO duration, "human duration" as used in code
frequency: { minutes: 30 }
# supports ISO duration, "human duration" as used in code
diff --git a/docs/notifications/index.md b/docs/notifications/index.md
new file mode 100644
index 0000000000..95d77a9b7f
--- /dev/null
+++ b/docs/notifications/index.md
@@ -0,0 +1,320 @@
+---
+id: index
+title: Getting Started
+description: How to get started with the notifications and signals
+---
+
+The Backstage Notifications System provides a way for plugins and external services to send notifications to Backstage users.
+These notifications are displayed in the dedicated page of the Backstage frontend UI or by frontend plugins per specific scenarios.
+Additionally, notifications can be sent to external channels (like email) via "processors" implemented within plugins.
+
+Notifications can be optionally integrated with the signals (a push mechanism) to ensure users receive them immediately.
+
+### Upgrade to the latest version of Backstage
+
+To ensure your version of Backstage has all the latest notifications and signals related functionality, it’s important to upgrade to the latest version. The [Backstage upgrade helper](https://backstage.github.io/upgrade-helper/) is a great tool to help ensure that you’ve made all the necessary changes during the upgrade!
+
+## About notifications
+
+Notifications are messages sent to either individual users or groups.
+They are not intended for inter-process communication of any kind.
+
+There are two basic types of notifications:
+
+- **Broadcast**: Messages sent to all users of Backstage.
+- **Entity**: Messages delivered to specific listed entities, such as Users or Groups.
+
+Example of use-cases:
+
+- System-wide announcements or alerts
+- Notifications for component owners: e.g., build failures, successful deployments, new vulnerabilities
+- Notifications for individuals: e.g., updates you have subscribed to, new required training courses
+- Notifications pertaining to a particular entity in the catalog: A notification might apply to an entity and the owning team.
+
+## Installation in Older Environments
+
+Newer versions of instances created by the create-app have both the notifications and signals plugins included by default, this section can be skipped right to the Configuration.
+
+Following installation instructions are valid for enabling the plugins in older environments.
+
+### Add Notifications Backend
+
+```bash
+yarn workspace backend add @backstage/plugin-notifications-backend
+```
+
+Add the notifications to your `backend/src/index.ts`:
+
+```ts
+const backend = createBackend();
+// ...
+backend.add(import('@backstage/plugin-notifications-backend'));
+```
+
+### Add Notifications Frontend
+
+```bash
+yarn workspace app add @backstage/notifications
+```
+
+To add the notifications main menu, add following to your `packages/app/src/components/Root/Root.tsx`:
+
+```tsx
+import { NotificationsSidebarItem } from '@backstage/plugin-notifications';
+
+
+
+
+ // ...
+
+
+
+;
+```
+
+Also add the route to notifications to `packages/app/src/App.tsx`:
+
+```tsx
+import { NotificationsPage } from '@backstage/plugin-notifications';
+
+
+ // ...
+ } />
+;
+```
+
+### Optional: Add Signals Backend
+
+Optionally add Signals to your backend by
+
+```bash
+yarn workspace backend add @backstage/plugin-signals-backend
+```
+
+Add the signals to your `backend/src/index.ts`:
+
+```ts
+const backend = createBackend();
+// ...
+backend.add(import('@backstage/plugin-signals-backend'));
+```
+
+### Optional: Signals Frontend
+
+The use of signals is optional but improves user experience.
+
+Start with:
+
+```bash
+yarn workspace app add @backstage/plugin-signals
+```
+
+To install the plugin, you have to add the following to your `packages/app/src/plugins.ts`:
+
+```ts
+export { signalsPlugin } from '@backstage/plugin-signals';
+```
+
+And make sure that your `packages/app/src/App.tsx` contains:
+
+```ts
+import * as plugins from './plugins';
+
+const app = createApp({
+ // ...
+ plugins: Object.values(plugins),
+ // ...
+});
+```
+
+If the signals plugin is properly configured, it will be automatically discovered by the notifications plugin and used.
+
+## Configuration
+
+### Notifications Backend
+
+The Notifications backend plugin provides an API to create notifications, list notifications per logged-in user, and search based on parameters.
+
+The plugin uses a relational [database](https://backstage.io/docs/getting-started/config/database) for persistence, no specifics are introduced in this context.
+
+No additional configuration in the app-config is needed, except for optional additional modules for `processors`.
+
+### Notifications Frontend
+
+The recipients of notifications have to be entities in the catalog, e.g. of the User or Group kind.
+
+Otherwise no specific configuration is needed for the front-end notifications plugin.
+
+All parametrization is done through component properties, such as the `NotificationsSidebarItem`, which can be used as an active left-side menu item in the front-end.
+
+
+
+In the `packages/app/src/components/Root/Root.tsx`, tweak the [properties](https://backstage.io/docs/reference/plugin-notifications.notificationssidebaritem) of the `` per specific needs.
+
+## Use
+
+New notifications can be sent either by a backend plugin or an external service through the REST API.
+
+### Backend
+
+Regardless of technical feasibility, a backend plugin should avoid directly accessing the notifications REST API.
+Instead, it should integrate with the `@backstage/plugin-notifications-node` to `send` (create) a new notification.
+
+The reasons for this approach include the propagation of authorization in the API request and improved maintenance and backward compatibility in the future.
+
+```ts
+import { notificationService } from '@backstage/plugin-notifications-node';
+
+export const myPlugin = createBackendPlugin({
+ pluginId: 'myPlugin',
+ register(env) {
+ env.registerInit({
+ deps: {
+ // ...
+ notificationService: notificationService,
+ },
+ async init({ config, logger, httpRouter, notificationService }) {
+ httpRouter.use(
+ await createRouter({
+ // ...
+ notificationService,
+ }),
+ );
+ },
+ });
+ },
+});
+```
+
+To emit a new notification:
+
+```ts
+notificationService.send({
+ recipients /* of the broadcast or entity type */,
+ payload /* actual message */,
+});
+```
+
+Refer the [API documentation](https://github.com/backstage/backstage/blob/master/plugins/notifications-node/api-report.md) for further details.
+
+### Signals
+
+The use of signals with notifications is optional but generally enhances user experience and performance.
+
+When a notification is created, a new signal is emitted to a general-purpose message bus to announce it to subscribed listeners.
+
+The frontend maintains a persistent connection (WebSocket) to receive these announcements from the notifications channel.
+The specific details of the updated or created notification should be retrieved via a request to the notifications API, except for new notifications, where the payload is included in the signal for performance reasons.
+
+In a frontend plugin, to subscribe for notifications' signals:
+
+```ts
+import { useSignal } from '@backstage/plugin-signals-react';
+
+const { lastSignal } = useSignal('notifications');
+
+React.useEffect(() => {
+ /* ... */
+}, [lastSignal, notificationsApi]);
+```
+
+### Consuming Notifications
+
+In a front-end plugin, the simplest way to query a notification is by its ID:
+
+```ts
+import { useApi } from '@backstage/core-plugin-api';
+import { notificationsApiRef } from '@backstage/plugin-notifications';
+
+const notificationsApi = useApi(notificationsApiRef);
+
+notificationsApi.getNotification(yourId);
+
+// or with connection to signals:
+notificationsApi.getNotification(lastSignal.notification_id);
+```
+
+### Extending Notifications via Processors
+
+The notifications can be extended with `NotificationProcessor`. These processors allow to decorate notifications before they are sent or/and send the notifications to external services.
+
+Depending on the needs, a processor can modify the content of a notification or route it to different systems like email, Slack, or other services.
+
+A good example of how to write a processor is the [Email Processor](https://github.com/backstage/backstage/tree/master/plugins/notifications-backend-module-email).
+
+Start off by creating a notification processor:
+
+```ts
+import { Notification } from '@backstage/plugin-notifications-common';
+import { NotificationProcessor } from '@backstage/plugin-notifications-node';
+
+class MyNotificationProcessor implements NotificationProcessor {
+ async decorate(notification: Notification): Promise {
+ if (notification.origin === 'plugin-my-plugin') {
+ notification.payload.icon = 'my-icon';
+ }
+ return notification;
+ }
+
+ async send(notification: Notification): Promise {
+ nodemailer.sendEmail({
+ from: 'backstage',
+ to: 'user',
+ subject: notification.payload.title,
+ text: notification.payload.description,
+ });
+ }
+}
+```
+
+Both of the processing functions are optional, and you can implement only one of them.
+
+Add the notification processor to the notification system by:
+
+```ts
+import { notificationsProcessingExtensionPoint } from '@backstage/plugin-notifications-node';
+import { Notification } from '@backstage/plugin-notifications-common';
+
+export const myPlugin = createBackendPlugin({
+ pluginId: 'myPlugin',
+ register(env) {
+ env.registerInit({
+ deps: {
+ notifications: notificationsProcessingExtensionPoint,
+ // ...
+ },
+ async init({ notifications }) {
+ // ...
+ notifications.addProcessor(new MyNotificationProcessor());
+ },
+ });
+ },
+});
+```
+
+### External Services
+
+When the emitter of a notification is a Backstage backend plugin, it is mandatory to use the integration via `@backstage/plugin-notifications-node` as described above.
+
+If the emitter is a service external to Backstage, an HTTP POST request can be issued directly to the API, assuming that authentication is properly configured.
+Refer to the [service-to-service auth documentation](https://backstage.io/docs/auth/service-to-service-auth) for more details, focusing on the Static Tokens section for the simplest setup option.
+
+An example request for creating a broadcast notification might look like:
+
+```bash
+curl -X POST https://[BACKSTAGE_BACKEND]/api/notifications -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_BASE64_SHARED_KEY_TOKEN" -d '{"recipients":{"type":"broadcast"},"payload": {"title": "Title of broadcast message","link": "http://foo.com/bar","severity": "high","topic": "The topic"}}'
+```
+
+## Additional info
+
+An example of a backend plugin sending notifications can be found in https://github.com/backstage/backstage/tree/master/plugins/scaffolder-backend-module-notifications.
+
+Sources of the notifications and signal plugins:
+
+- https://github.com/backstage/backstage/blob/master/plugins/notifications
+
+- https://github.com/backstage/backstage/blob/master/plugins/notifications-backend
+
+- https://github.com/backstage/backstage/blob/master/plugins/notifications-node
+
+- https://github.com/backstage/backstage/blob/master/plugins/signals-react
diff --git a/docs/notifications/notificationsPage.png b/docs/notifications/notificationsPage.png
new file mode 100644
index 0000000000..7c96ab77af
Binary files /dev/null and b/docs/notifications/notificationsPage.png differ
diff --git a/docs/overview/threat-model.md b/docs/overview/threat-model.md
index c0e2d61e25..74c055a86c 100644
--- a/docs/overview/threat-model.md
+++ b/docs/overview/threat-model.md
@@ -41,7 +41,7 @@ The built-in protection against unauthorized access does not by default include
## Common Backend Configuration
-There are many common facilities that are configured centrally and available to all Backstage backend plugins. For example there is a `DatabaseManager` that provides access to a SQL database, `TaskScheduler` for scheduling long-running tasks, `Logger` as a general logging facility, and `UrlReader` for reading content from external sources. These are all configured either directly in code, or within the `backend` block of the static configuration. The appropriate care needs to be taken to ensure that any secrets remain confidential and no malicious configuration is injected.
+There are many common facilities that are configured centrally and available to all Backstage backend plugins. For example there is a `DatabaseManager` that provides access to a SQL database, `SchedulerService` for scheduling long-running tasks, `Logger` as a general logging facility, and `UrlReader` for reading content from external sources. These are all configured either directly in code, or within the `backend` block of the static configuration. The appropriate care needs to be taken to ensure that any secrets remain confidential and no malicious configuration is injected.
In a typical Backstage setup, there is no boundary between plugins that run on the same host. Likewise, there is no boundary between plugins that share the same database access. Any plugin that is running on a host that has access to the logical database of any other plugin should be considered to have full access to that other plugin. For example, even if you deploy the `auth` and `catalog` plugins on separate hosts with separate configuration and credentials, the `catalog` plugin is still considered to have full access to the `auth` plugin as long as the `catalog` plugin has access to the `auth` plugin's logical database. The only way to create a boundary between the two plugins is to deploy them in such a way that they do not have access to each others’ database. This applies to the database facility as well as any other shared resources, such as the cache.
diff --git a/docs/permissions/writing-a-policy.md b/docs/permissions/writing-a-policy.md
index 0f2d4fe091..0762f6b0c6 100644
--- a/docs/permissions/writing-a-policy.md
+++ b/docs/permissions/writing-a-policy.md
@@ -141,4 +141,8 @@ class TestPermissionPolicy implements PermissionPolicy {
In this example, we use [`isResourcePermission`](https://backstage.io/docs/reference/plugin-permission-common.isresourcepermission) to match all permissions with a resource type of `catalog-entity`. Just like `isPermission`, this helper will "narrow" the type of `request.permission` and enable the use of `createCatalogConditionalDecision`. In addition to the behavior you observed before, you should also see that catalog entities are no longer visible unless you are the owner - success!
-_Note:_ Some catalog permissions do not have the `'catalog-entity'` resource type, such as [`catalogEntityCreatePermission`](https://github.com/backstage/backstage/blob/1e5e9fb9de9856a49e60fc70c38a4e4e94c69570/plugins/catalog-common/src/permissions.ts#L49). In those cases, a definitive decision is required because conditions can't be applied to an entity that does not exist yet.
+:::note Note
+
+Some catalog permissions do not have the `'catalog-entity'` resource type, such as [`catalogEntityCreatePermission`](https://github.com/backstage/backstage/blob/1e5e9fb9de9856a49e60fc70c38a4e4e94c69570/plugins/catalog-common/src/permissions.ts#L49). In those cases, a definitive decision is required because conditions can't be applied to an entity that does not exist yet.
+
+:::
diff --git a/docs/plugins/composability.md b/docs/plugins/composability.md
index 1a9c0babf9..a0e0e2d5e6 100644
--- a/docs/plugins/composability.md
+++ b/docs/plugins/composability.md
@@ -329,7 +329,7 @@ You can also use static configuration to bind routes, removing the need to make
changes to the app code. It does however mean that you won't get type safety
when binding routes and compile-time validation of the bindings. Static
configuration of route bindings is done under the `app.routes.bindings` key in
-`app-config.yaml`. It works the same way as [route bindings in the new frontend system](../frontend-system/architecture/07-routes.md#binding-external-route-references),
+`app-config.yaml`. It works the same way as [route bindings in the new frontend system](../frontend-system/architecture/36-routes.md#binding-external-route-references),
for example:
```yaml
@@ -342,7 +342,7 @@ app:
### Default Targets for External Route References
Following the `1.28` release of Backstage you can now define default targets for
-external route references. They work the same way as [default targets in the new frontend system](../frontend-system/architecture/07-routes.md#default-targets-for-external-route-references),
+external route references. They work the same way as [default targets in the new frontend system](../frontend-system/architecture/36-routes.md#default-targets-for-external-route-references),
for example:
```ts
diff --git a/docs/releases/v1.30.0-changelog.md b/docs/releases/v1.30.0-changelog.md
new file mode 100644
index 0000000000..608d94e711
--- /dev/null
+++ b/docs/releases/v1.30.0-changelog.md
@@ -0,0 +1,3093 @@
+# Release v1.30.0
+
+Upgrade Helper: [https://backstage.github.io/upgrade-helper/?to=1.30.0](https://backstage.github.io/upgrade-helper/?to=1.30.0)
+
+## @backstage/backend-app-api@0.9.0
+
+### Minor Changes
+
+- da4fde5: **BREAKING**: Removed several deprecated service factories. These can instead be imported from `@backstage/backend-defaults` package.
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+- 389f5a4: Remove deprecated `urlReaderServiceFactory`, please import from `@backstage/backend-defaults/urlReader` instead.
+
+### Patch Changes
+
+- 8b13183: Added support for the latest version of `BackendFeature`s from `@backstage/backend-plugin-api`, including feature loaders.
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 7c5f3b0: Update the `ServiceRegister` implementation to enable registering multiple service implementations for a given service ref.
+- 80a0737: Added configuration for the `packages` options to config schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/config-loader@1.9.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/cli-common@0.1.14
+ - @backstage/cli-node@0.2.7
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/backend-common@0.24.0
+
+### Minor Changes
+
+- 389f5a4: **BREAKING**: Removed the following `Url Reader` deprecated exports:
+
+ - UrlReader: Use `UrlReaderService` from `@backstage/backend-plugin-api` instead;
+ - AzureUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - BitbucketUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - BitbucketCloudUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - BitbucketServerUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - GithubUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - GitlabUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - GerritUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - GiteaUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - HarnessUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - AwsS3UrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - FetchUrlReader: Import from `@backstage/backend-defaults/urlReader` instead;
+ - UrlReaders: Import from `@backstage/backend-defaults/urlReader` instead;
+ - UrlReadersOptions: Import from `@backstage/backend-defaults/urlReader` instead;
+ - UrlReaderPredicateTuple: Import from `@backstage/backend-defaults/urlReader` instead;
+ - FromReadableArrayOptions: Import from `@backstage/backend-defaults/urlReader` instead;
+ - ReaderFactory: Import from `@backstage/backend-defaults/urlReader` instead;
+ - ReadUrlOptions:Use `UrlReaderServiceReadUrlOptions` from `@backstage/backend-plugin-api` instead;
+ - ReadUrlResponse: Use `UrlReaderServiceReadUrlResponse` from `@backstage/backend-plugin-api` instead;
+ - ReadUrlResponseFactory: Import from `@backstage/backend-defaults/urlReader` instead;
+ - ReadUrlResponseFactoryFromStreamOptions: Import from `@backstage/backend-defaults/urlReader` instead;
+ - ReadTreeOptions: Use `UrlReaderServiceReadTreeOptions` from `@backstage/backend-plugin-api` instead;
+ - ReadTreeResponse: Use `UrlReaderServiceReadTreeResponse` from `@backstage/backend-plugin-api` instead;
+ - ReadTreeResponseFile: Use `UrlReaderServiceReadTreeResponseFile` from `@backstage/backend-plugin-api` instead;
+ - ReadTreeResponseDirOptions: Use `UrlReaderServiceReadTreeResponseDirOptions` from `@backstage/backend-plugin-api` instead;
+ - ReadTreeResponseFactory: Import from `@backstage/backend-defaults/urlReader` instead;
+ - ReadTreeResponseFactoryOptions: Import from `@backstage/backend-defaults/urlReader` instead;
+ - SearchOptions: Use `UrlReaderServiceSearchOptions` from `@backstage/backend-plugin-api` instead;
+ - SearchResponse: Use `UrlReaderServiceSearchResponse` from `@backstage/backend-plugin-api` instead;
+ - SearchResponseFile: Use `UrlReaderServiceSearchResponseFile` from `@backstage/backend-plugin-api` instead.
+
+### Patch Changes
+
+- ba8571e: Setup user agent header for AWS sdk clients, this enables users to better track API calls made from Backstage to AWS APIs through things like CloudTrail.
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+
+- 6795e33: This package is marked as `deprecated` and will be removed in a near future, please follow the deprecated instructions for the exports you still use.
+
+- 7e13b7a: The remaining exports in the package have now been deprecated:
+
+ - `cacheToPluginCacheManager`
+ - `createLegacyAuthAdapters`
+ - `LegacyCreateRouter`
+ - `legacyPlugin`
+ - `loggerToWinstonLogger`
+ - `makeLegacyPlugin`
+
+ Users of these export should fully [migrate to the new backend system](https://backstage.io/docs/backend-system/building-backends/migrating).
+
+- ddde5fe: Internal type refactor.
+
+- b63d378: export `createConfigSecretEnumerator` from `@backstage/backend-common` instead of `@backstage/backend-app-api`.
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/config-loader@1.9.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/backend-dev-utils@0.1.5
+ - @backstage/integration@1.14.0
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/types@1.1.1
+
+## @backstage/backend-dynamic-feature-service@0.3.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- b63d378: Update internal imports
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/backend-app-api@0.9.0
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-catalog-backend@1.25.0
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/config-loader@1.9.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/cli-common@0.1.14
+ - @backstage/cli-node@0.2.7
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-app-node@0.1.23
+ - @backstage/plugin-events-backend@0.3.10
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/backend-plugin-api@0.8.0
+
+### Minor Changes
+
+- 389f5a4: **BREAKING** Deleted the following deprecated `UrlReader` exports
+
+ - 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;
+ - SearchResponseFile: Use `UrlReaderServiceSearchResponseFile` instead.
+
+- 7c5f3b0: The `createServiceRef` function now accepts a new boolean `multiple` option. The `multiple` option defaults to `false` and when set to `true`, it enables that multiple implementation are installed for the created service ref.
+
+ We're looking for ways to make it possible to augment services without the need to replace the entire service.
+
+ Typical example of that being the ability to install support for additional targets for the `UrlReader` service without replacing the service itself. This achieves that by allowing us to define services that can have multiple simultaneous implementation, allowing the `UrlReader` implementation to depend on such a service to collect all possible implementation of support for external targets:
+
+ ```diff
+ // @backstage/backend-defaults
+
+ + export const urlReaderFactoriesServiceRef = createServiceRef({
+ + id: 'core.urlReader.factories',
+ + scope: 'plugin',
+ + multiton: true,
+ + });
+
+ ...
+
+ export const urlReaderServiceFactory = createServiceFactory({
+ service: coreServices.urlReader,
+ deps: {
+ config: coreServices.rootConfig,
+ logger: coreServices.logger,
+ + factories: urlReaderFactoriesServiceRef,
+ },
+ - async factory({ config, logger }) {
+ + async factory({ config, logger, factories }) {
+ return UrlReaders.default({
+ config,
+ logger,
+ + factories,
+ });
+ },
+ });
+ ```
+
+ With that, you can then add more custom `UrlReader` factories by installing more implementations of the `urlReaderFactoriesServiceRef` in your backend instance. Something like:
+
+ ```ts
+ // packages/backend/index.ts
+ import { createServiceFactory } from '@backstage/backend-plugin-api';
+ import { urlReaderFactoriesServiceRef } from '@backstage/backend-defaults';
+ ...
+
+ backend.add(createServiceFactory({
+ service: urlReaderFactoriesServiceRef,
+ deps: {},
+ async factory() {
+ return CustomUrlReader.factory;
+ },
+ }));
+
+ ...
+
+ ```
+
+- c99c620: **BREAKING** Removed the following deprecated types:
+
+ - `ServiceRefConfig` use `ServiceRefOptions`
+ - `RootServiceFactoryConfig` use `RootServiceFactoryOptions`
+ - `PluginServiceFactoryConfig` use `PluginServiceFactoryOptions`
+
+### Patch Changes
+
+- 6061061: Added `createBackendFeatureLoader`, which can be used to create an installable backend feature that can in turn load in additional backend features in a dynamic way.
+
+- ba9abf4: The `SchedulerService` now allows tasks with `frequency: { trigger: 'manual' }`. This means that the task will not be scheduled, but rather run only when manually triggered with `SchedulerService.triggerTask`.
+
+- 8b13183: Added `createBackendFeatureLoader`, which can be used to programmatically select and install backend features.
+
+ A feature loader can return an list of features to be installed, for example in the form on an `Array` or other for of iterable, which allows for the loader to be defined as a generator function. Both synchronous and asynchronous loaders are supported.
+
+ Additionally, a loader can depend on services in its implementation, with the restriction that it can only depend on root-scoped services, and it may not override services that have already been instantiated.
+
+ ```ts
+ const searchLoader = createBackendFeatureLoader({
+ deps: {
+ config: coreServices.rootConfig,
+ },
+ *loader({ config }) {
+ // Example of a custom config flag to enable search
+ if (config.getOptionalString('customFeatureToggle.search')) {
+ yield import('@backstage/plugin-search-backend/alpha');
+ yield import('@backstage/plugin-search-backend-module-catalog/alpha');
+ yield import('@backstage/plugin-search-backend-module-explore/alpha');
+ yield import('@backstage/plugin-search-backend-module-techdocs/alpha');
+ }
+ },
+ });
+ ```
+
+- ddde5fe: Fixed a type issue where plugin and modules depending on multiton services would not receive the correct type.
+
+- f011d1b: fix typo in `getPluginRequestToken` comments
+
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/backend-tasks@0.6.0
+
+### Minor Changes
+
+- fc24d9e: This package is deprecated and will be removed in a near future, follow the instructions below to stop using it:
+
+ - `TaskScheduler`: Please migrate to the new backend system, and depend on `coreServices.scheduler` from `@backstage/backend-plugin-api` instead, or use `DefaultSchedulerService` from \`@backstage/backend-defaults;
+ - `TaskRunner`: Please import `SchedulerServiceTaskRunner` from `@backstage/backend-plugin-api` instead;
+ - `TaskFunction`: Please import `SchedulerServiceTaskFunction` from `@backstage/backend-plugin-api` instead;
+ - `TaskDescriptor`: Please import `SchedulerServiceTaskDescriptor` from `@backstage/backend-plugin-api` instead;
+ - `TaskInvocationDefinition`: Please import `SchedulerServiceTaskInvocationDefinition` from `@backstage/backend-plugin-api` instead;
+ - `TaskScheduleDefinition`: Please import `SchedulerServiceTaskFunction` from `@backstage/backend-plugin-api` instead;
+ - `TaskScheduleDefinitionConfig`: Please import `SchedulerServiceTaskScheduleDefinitionConfig` from `@backstage/backend-plugin-api` instead;
+ - `PluginTaskScheduler`: Please use `SchedulerService` from `@backstage/backend-plugin-api` instead (most likely via `coreServices.scheduler`);
+ - `readTaskScheduleDefinitionFromConfig`: Please import `readSchedulerServiceTaskScheduleDefinitionFromConfig` from `@backstage/backend-plugin-api` instead;
+ - `HumanDuration`: Import `TypesHumanDuration` from `@backstage/types` instead.
+
+### Patch Changes
+
+- ba9abf4: The `PluginTaskScheduler` now allows tasks with `frequency: { trigger: 'manual' }`. This means that the task will not be scheduled, but rather run only when manually triggered with `PluginTaskScheduler.triggerTask`.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/backend-test-utils@0.5.0
+
+### Minor Changes
+
+- 861f162: **BREAKING**: Removed these deprecated helpers:
+
+ - `setupRequestMockHandlers` Use `CreateMockDirectoryOptions` instead.
+ - `CreateMockDirectoryOptions` Use `registerMswTestHooks` instead.
+
+ Stopped exporting the deprecated and internal `isDockerDisabledForTests` helper.
+
+ Removed `get` method from `ServiceFactoryTester` which is replaced by `getSubject`
+
+### Patch Changes
+
+- 8b13183: Internal updates to support latest version of `BackendFeauture`s from `@backstage/backend-plugin-api`.
+- b63d378: Update internal imports
+- 7c5f3b0: Update the `ServiceFactoryTester` to be able to test services that enables multi implementation installation.
+- 4e79d19: The default services for `startTestBackend` and `ServiceFactoryTester` now includes the Root Health Service.
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/backend-app-api@0.9.0
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/catalog-model@1.6.0
+
+### Minor Changes
+
+- 34fa803: Introduce an optional spec.type attribute on the Domain and System entity kinds
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/cli@0.27.0
+
+### Minor Changes
+
+- 32a38e1: **BREAKING**: The lockfile (`yarn.lock`) dependency analysis and mutations have been removed from several commands.
+
+ The `versions:bump` command will no longer attempt to bump and deduplicate dependencies by modifying the lockfile, it will only update `package.json` files.
+
+ The `versions:check` command has been removed, since its only purpose was verification and mutation of the lockfile. We recommend using the `yarn dedupe` command instead, or the `yarn-deduplicate` package if you're using Yarn classic.
+
+ The check that was built into the `package start` command has been removed, it will no longer warn about lockfile mismatches.
+
+ The packages in the Backstage ecosystem handle package duplications much better now than when these CLI features were first introduced, so the need for these features has diminished. By removing them, we drastically reduce the integration between the Backstage CLI and Yarn, making it much easier to add support for other package managers in the future.
+
+### Patch Changes
+
+- 7eb08a6: Add frontend-dynamic-container role to eslint config factory
+- b2d97fd: Fixing loading of additional config files with new `ConfigSources`
+- fbc7819: Use ES2022 in CLI bundler
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 6d898d8: Switched the `process` polyfill to use `require.resolve` for greater compatability.
+- e53074f: Updated default backend plugin to use `RootConfigService` instead of `Config`. This also removes the dependency on `@backstage/config` as it's no longer used.
+- ee2b0e5: The experimental module federation build now has the ability to force the use of development versions of `react` and `react-dom` by setting the `FORCE_REACT_DEVELOPMENT` flag.
+- 239dffc: Remove usage of deprecated functionality from @backstage/config-loader
+- e6e7d86: Switched the target from `'ES2022'` to `'es2022'` for better compatibility with older versions of `swc`.
+- 2ced236: Updated dependency `@module-federation/enhanced` to `0.3.1`
+- 0eedec3: Add support for dynamic plugins via the EXPERIMENTAL_MODULE_FEDERATION environment variable when running `yarn start`.
+- adabb40: New command now supports setting package license
+- dc4fb4f: Fix for `repo build --all` not properly detecting the experimental public entry point.
+- Updated dependencies
+ - @backstage/config-loader@1.9.0
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/cli-common@0.1.14
+ - @backstage/cli-node@0.2.7
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/eslint-plugin@0.1.8
+ - @backstage/release-manifests@0.0.11
+ - @backstage/types@1.1.1
+
+## @backstage/config-loader@1.9.0
+
+### Minor Changes
+
+- 274428f: Add configuration key to File and Remote `ConfigSource`s that enables configuration of parsing logic. Previously limited to yaml, these `ConfigSource`s now allow for a multitude of parsing options (e.g. JSON).
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 1edd6c2: The `env` option of `ConfigSources.default` now correctly allows undefined members.
+- 493feac: Add boolean `allowMissingDefaultConfig` option to `ConfigSources.default` and
+ `ConfigSources.defaultForTargets`, which results in omission of a ConfigSource
+ for the default app-config.yaml configuration file if it's not present.
+- Updated dependencies
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/frontend-app-api@0.8.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 7777b5f: Support icon overriding with the new `IconBundleBlueprint` API.
+- 72754db: Updated usage of `useRouteRef`, which can now always return `undefined`.
+- 3be9aeb: Added support for v2 extensions, which declare their inputs and outputs without using a data map.
+- fe1fbb2: Migrating usages of the deprecated `createExtension` `v1` format to the newer `v2` format, and old `create*Extension` extension creators to blueprints.
+- 6349099: Added config input type to the extensions
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/core-components@0.14.10
+ - @backstage/core-app-api@1.14.2
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/frontend-plugin-api@0.7.0
+
+### Minor Changes
+
+- 72754db: **BREAKING**: All types of route refs are always considered optional by `useRouteRef`, which means the caller must always handle a potential `undefined` return value. Related to this change, the `optional` option from `createExternalRouteRef` has been removed, since it is no longer necessary.
+
+ This is released as an immediate breaking change as we expect the usage of the new route refs to be extremely low or zero, since plugins that support the new system will still use route refs and `useRouteRef` from `@backstage/core-plugin-api` in combination with `convertLegacyRouteRef` from `@backstage/core-compat-api`.
+
+### Patch Changes
+
+- 6f72c2b: Fixing issue with extension blueprints `inputs` merging.
+
+- 210d066: Added support for using the `params` in other properties of the `createExtensionBlueprint` options by providing a callback.
+
+- 9b356dc: Renamed `createPlugin` to `createFrontendPlugin`. The old symbol is still exported but deprecated.
+
+- a376559: Correct the `TConfig` type of data references to only contain config
+
+- 4e53ad6: Introduce a new way to encapsulate extension kinds that replaces the extension creator pattern with `createExtensionBlueprint`
+
+ This allows the creation of extension instances with the following pattern:
+
+ ```tsx
+ // create the extension blueprint which is used to create instances
+ const EntityCardBlueprint = createExtensionBlueprint({
+ kind: 'entity-card',
+ attachTo: { id: 'test', input: 'default' },
+ output: [coreExtensionData.reactElement],
+ factory(params: { text: string }) {
+ return [coreExtensionData.reactElement(
{params.text}
)];
+ },
+ });
+
+ // create an instance of the extension blueprint with params
+ const testExtension = EntityCardBlueprint.make({
+ name: 'foo',
+ params: {
+ text: 'Hello World',
+ },
+ });
+ ```
+
+- 9b89b82: The `ExtensionBoundary` now by default infers whether it's routable from whether it outputs a route path.
+
+- e493020: Deprecated `inputs` and `configSchema` options for `createComponentExtenion`, these will be removed in a future release
+
+- 7777b5f: Added a new `IconBundleBlueprint` that lets you create icon bundle extensions that can be installed in an App in order to override or add new app icons.
+
+ ```tsx
+ import { IconBundleBlueprint } from '@backstage/frontend-plugin-api';
+
+ const exampleIconBundle = IconBundleBlueprint.make({
+ name: 'example-bundle',
+ params: {
+ icons: {
+ user: MyOwnUserIcon,
+ },
+ },
+ });
+ ```
+
+- 99abb6b: Support overriding of plugin extensions using the new `plugin.withOverrides` method.
+
+ ```tsx
+ import homePlugin from '@backstage/plugin-home';
+
+ export default homePlugin.withOverrides({
+ extensions: [
+ homePage.getExtension('page:home').override({
+ *factory(originalFactory) {
+ yield* originalFactory();
+ yield coreExtensionData.reactElement(
My custom home page
);
+ },
+ }),
+ ],
+ });
+ ```
+
+- 813cac4: Add an `ExtensionBoundary.lazy` function to create properly wrapped lazy-loading enabled elements, suitable for use with `coreExtensionData.reactElement`. The page blueprint now automatically leverages this.
+
+- a65cfc8: Add support for accessing extensions definitions provided by a plugin via `plugin.getExtension(...)`. For this to work the extensions must be defined using the v2 format, typically using an extension blueprint.
+
+- 3be9aeb: Extensions have been changed to be declared with an array of inputs and outputs, rather than a map of named data refs. This change was made to reduce confusion around the role of the input and output names, as well as enable more powerful APIs for overriding extensions.
+
+ An extension that was previously declared like this:
+
+ ```tsx
+ const exampleExtension = createExtension({
+ name: 'example',
+ inputs: {
+ items: createExtensionInput({
+ element: coreExtensionData.reactElement,
+ }),
+ },
+ output: {
+ element: coreExtensionData.reactElement,
+ },
+ factory({ inputs }) {
+ return {
+ element: (
+
,
+ ),
+ ];
+ },
+ });
+ ```
+
+- 34f1b2a: Support merging of `inputs` in extension blueprints, but stop merging `output`. In addition, the original factory in extension blueprints now returns a data container that both provides access to the returned data, but can also be forwarded as output.
+
+- 3fb421d: Added support to be able to define `zod` config schema in Blueprints, with built in schema merging from the Blueprint and the extension instances.
+
+- 2d21599: Added support for being able to override extension definitions.
+
+ ```tsx
+ const TestCard = EntityCardBlueprint.make({
+ ...
+ });
+
+ TestCard.override({
+ // override attachment points
+ attachTo: { id: 'something-else', input: 'overridden' },
+ // extend the config schema
+ config: {
+ schema: {
+ newConfig: z => z.string().optional(),
+ }
+ },
+ // override factory
+ *factory(originalFactory, { inputs, config }){
+ const originalOutput = originalFactory();
+
+ yield coreExentsionData.reactElement(
+
+ {originalOutput.get(coreExentsionData.reactElement)}
+
+ );
+ }
+ });
+
+ ```
+
+- 31bfc44: Extension data references can now be defined in a way that encapsulates the ID string in the type, in addition to the data type itself. The old way of creating extension data references is deprecated and will be removed in a future release.
+
+ For example, the following code:
+
+ ```ts
+ export const myExtension =
+ createExtensionDataRef('my-plugin.my-data');
+ ```
+
+ Should be updated to the following:
+
+ ```ts
+ export const myExtension = createExtensionDataRef().with({
+ id: 'my-plugin.my-data',
+ });
+ ```
+
+- 6349099: Added config input type to the extensions
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/integration@1.14.0
+
+### Minor Changes
+
+- 78c1329: Updated `GitlabUrlReader.readUrl` and `GitlabUrlReader.readTree` to accept a user-provided token, supporting both bearer and private tokens.
+
+### Patch Changes
+
+- c591670: Updated functions for `getHarnessEditContentsUrl`, `getHarnessFileContentsUrl`, `getHarnessArchiveUrl`, `getHarnessLatestCommitUrl` and `parseHarnessUrl` to handle account and org level urls
+- Updated dependencies
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-auth-backend-module-cloudflare-access-provider@0.2.0
+
+### Minor Changes
+
+- 75d026a: Support for Cloudflare Custom Headers and Custom Cookie Auth Name
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-auth-node@0.5.0
+
+### Minor Changes
+
+- 579afd0: **BREAKING**: Sign-in resolvers configured via `.signIn.resolvers` now take precedence over sign-in resolvers passed to `signInResolver` option of `createOAuthProviderFactory`. This effectively makes sign-in resolvers passed via the `signInResolver` the default one, which you can then override through configuration.
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-catalog@1.22.0
+
+### Minor Changes
+
+- 6925dcb: Introduces the HasSubdomainsCard component that displays the subdomains of a given domain
+
+### Patch Changes
+
+- 496b8a9: Export `RelatedEntitiesCard` presets to be reused.
+- 604a504: The entity relation cards available for the new frontend system via `/alpha` now have more accurate and granular default filters.
+- 7bd27e1: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead.
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- 6582799: Add `tableOptions` to all tables and additionally `title` to API tables.
+- 6349099: Added config input type to the extensions
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/plugin-search-react@1.7.14
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration-react@1.1.30
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-permission-react@0.4.25
+ - @backstage/plugin-scaffolder-common@1.5.5
+
+## @backstage/plugin-catalog-backend@1.25.0
+
+### Minor Changes
+
+- 163ba08: Deprecated `RouterOptions`, `CatalogBuilder`, and `CatalogEnvironment`. Please make sure to upgrade to the new backend system.
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 776eb56: `ProcessorOutputCollector` returns an error when receiving deferred entities that have an invalid `metadata.annotations` format.
+
+ This allows to return an error on an actual validation issue instead of reporting that the location annotations are missing afterwards, which is misleading for the users.
+
+- 389f5a4: Update deprecated url-reader-related imports.
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+
+- a629fb2: Added setAllowedLocationTypes while introducing a new extension point called CatalogLocationsExtensionPoint
+
+- 51240ee: Preserve default `allowedLocationTypes` when `setAllowedLocationTypes()` of `CatalogLocationsExtensionPoint` is not called.
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/plugin-search-backend-module-catalog@0.2.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/backend-openapi-utils@0.1.16
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-catalog-backend-module-aws@0.4.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- ba8571e: Setup user agent header for AWS sdk clients, this enables users to better track API calls made from Backstage to AWS APIs through things like CloudTrail.
+- 9342ac8: Removed unused dependency
+- 389f5a4: Update deprecated url-reader-related imports.
+- 90a7340: `AwsOrganizationCloudAccountProcessor` configuration field `roleArn` is deprecated in favor of new field `accountId`
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-kubernetes-common@0.8.2
+
+## @backstage/plugin-catalog-backend-module-azure@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 9342ac8: Removed unused dependency
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-catalog-backend-module-backstage-openapi@0.3.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/backend-openapi-utils@0.1.16
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-catalog-backend-module-bitbucket-cloud@0.3.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/plugin-bitbucket-cloud-common@0.2.22
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-catalog-backend-module-bitbucket-server@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 9342ac8: Removed unused dependency
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-catalog-backend-module-gcp@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 9342ac8: Removed unused dependency
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/plugin-kubernetes-common@0.8.2
+
+## @backstage/plugin-catalog-backend-module-gerrit@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 9342ac8: Removed unused dependency
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-catalog-backend-module-github@0.7.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+
+- c1eb809: Fix GitHub `repository` event support.
+
+ - `$.repository.organization` is only provided for `push` events. Switched to `$.organization.login` instead.
+ - `$.repository.url` is not always returning the expected and required value. Use `$.repository.html_url` instead.
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-catalog-backend@1.25.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-catalog-backend-module-github-org@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 9342ac8: Removed unused dependency
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-backend-module-github@0.7.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/config@1.2.0
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-catalog-backend-module-gitlab@0.4.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- c7b14ed: Adds new optional `excludeRepos` configuration option to the Gitlab catalog provider.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-catalog-backend-module-gitlab-org@0.1.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-catalog-backend-module-gitlab@0.4.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-catalog-backend-module-incremental-ingestion@0.5.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-catalog-backend@1.25.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-catalog-backend-module-ldap@0.8.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-catalog-backend-module-msgraph@0.6.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 9342ac8: Removed unused dependency
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 58dff4d: Added option to ingest groups based on their group membership in Azure Entra ID
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-catalog-backend-module-puppetdb@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 9342ac8: Removed unused dependency
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-events-backend-module-aws-sqs@0.4.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- ba8571e: Setup user agent header for AWS sdk clients, this enables users to better track API calls made from Backstage to AWS APIs through things like CloudTrail.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/config@1.2.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-notifications@0.3.0
+
+### Minor Changes
+
+- 0410fc9: By default, set notification as read when opening snackbar or web notification link
+
+### Patch Changes
+
+- 80b84f7: Fixed issue with notification reloading on page change
+- b58e452: Broadcast notifications are now decorated with an icon.
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/plugin-notifications-common@0.0.5
+ - @backstage/plugin-signals-react@0.0.4
+
+## @backstage/plugin-notifications-backend-module-email@0.2.0
+
+### Minor Changes
+
+- def53a7: **BREAKING** Following `NotificationTemplateRenderer` methods now return a Promise and **must** be awaited: `getSubject`, `getText` and `getHtml`.
+
+ Required changes and example usage:
+
+ ```diff
+ import { notificationsEmailTemplateExtensionPoint } from '@backstage/plugin-notifications-backend-module-email';
+ import { Notification } from '@backstage/plugin-notifications-common';
+ +import { getNotificationSubject, getNotificationTextContent, getNotificationHtmlContent } from 'my-notification-processing-library`
+ export const notificationsModuleEmailDecorator = createBackendModule({
+ pluginId: 'notifications',
+ moduleId: 'email.templates',
+ register(reg) {
+ reg.registerInit({
+ deps: {
+ emailTemplates: notificationsEmailTemplateExtensionPoint,
+ },
+ async init({ emailTemplates }) {
+ emailTemplates.setTemplateRenderer({
+ - getSubject(notification) {
+ + async getSubject(notification) {
+ - return `New notification from ${notification.source}`;
+ + const subject = await getNotificationSubject(notification);
+ + return `New notification from ${subject}`;
+ },
+ - getText(notification) {
+ + async getText(notification) {
+ - return notification.content;
+ + const text = await getNotificationTextContent(notification);
+ + return text;
+ },
+ - getHtml(notification) {
+ + async getHtml(notification) {
+ - return `
${notification.content}
`;
+ + const html = await getNotificationHtmlContent(notification);
+ + return html;
+ },
+ });
+ },
+ });
+ },
+ });
+ ```
+
+### Patch Changes
+
+- d55b8e3: Avoid sending broadcast emails as a fallback in case the entity-typed notification user can not be resolved.
+- cdb630d: Add support for stream transport for debugging purposes
+- 83faf24: Notification email processor supports allowing or denying specific email addresses from receiving notifications
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-notifications-node@0.2.4
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/types@1.1.1
+ - @backstage/plugin-notifications-common@0.0.5
+
+## @backstage/plugin-scaffolder@1.24.0
+
+### Minor Changes
+
+- 1552c33: Changed the way to display entities in `MyGroupsPicker` to use `entityPresentationApi` and make it consistent across scaffolder pickers
+- 3fca643: Added field extension `RepoBranchPicker` that supports autocompletion for Bitbucket
+
+### Patch Changes
+
+- 47ed51b: Add an extra bit of height to the EntityPicker dropdown to make it clear there are more options to select from, and to remove the scroll bar when there is less than 10 options
+- 46e5e55: Change scaffolder widgets to use `TextField` component for more flexibility in theme overrides.
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- 2ae63cd: add i18n for scaffolder
+- d18f4eb: Fix undefined in the title of Scaffolder Runs on the page load
+- 896a22d: Fix helper text margin for scaffolder EntityNamePicker and EntityTagsPicker when using outlined text field
+- bbd9f56: Cleaned up codebase of RepoUrlPicker
+- b8600fe: Fix issue with `RepoUrlPicker` not refreshing the credentials for a different host
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-scaffolder-react@1.11.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration-react@1.1.30
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-permission-react@0.4.25
+ - @backstage/plugin-scaffolder-common@1.5.5
+
+## @backstage/plugin-scaffolder-backend@1.24.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+- dcd6a79: Added OpenTelemetry support to Scaffolder metrics
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- c544f81: Add support for status filtering in scaffolder tasks endpoint
+- b63d378: Update internal imports
+- ef87e06: Fix scaffolder action `catalog:write` to write to directories that don't already exist
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/plugin-scaffolder-backend-module-github@0.4.1
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-scaffolder-backend-module-bitbucket-server@0.1.13
+ - @backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.1.13
+ - @backstage/plugin-scaffolder-backend-module-bitbucket@0.2.13
+ - @backstage/plugin-scaffolder-backend-module-gerrit@0.1.15
+ - @backstage/plugin-scaffolder-backend-module-gitea@0.1.13
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-scaffolder-backend-module-azure@0.1.15
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/plugin-scaffolder-backend-module-gitlab@0.4.5
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/plugin-bitbucket-cloud-common@0.2.22
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.1.21
+ - @backstage/plugin-scaffolder-common@1.5.5
+
+## @backstage/plugin-scaffolder-react@1.11.0
+
+### Minor Changes
+
+- 8839381: Add scaffolder option to display object items in separate rows on review page
+
+### Patch Changes
+
+- 072c00c: Fixed a bug in `DefaultTableOutputs` where output elements overlapped on smaller screen sizes
+- 46e5e55: Change scaffolder widgets to use `TextField` component for more flexibility in theme overrides.
+- d0e95a7: Add ability to customise form fields in the UI by exposing `uiSchema` and `formContext` in `FormProps`
+- 4670f06: support `ajv-errors` for scaffolder validation to allow for customizing the error messages
+- 04759f2: Fix null check in `isJsonObject` utility function for scaffolder review state component
+- Updated dependencies
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+ - @backstage/plugin-permission-react@0.4.25
+ - @backstage/plugin-scaffolder-common@1.5.5
+
+## @backstage/plugin-search-backend-module-catalog@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-search-backend-module-explore@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 93fc1a0: Updated dependency `@backstage-community/plugin-explore-common` to `^0.0.4`.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/config@1.2.0
+
+## @backstage/plugin-search-backend-module-stack-overflow-collator@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/config@1.2.0
+
+## @backstage/plugin-search-backend-module-techdocs@0.2.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-techdocs-node@1.12.9
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-search-backend-node@1.3.0
+
+### Minor Changes
+
+- fc24d9e: Stop using `@backstage/backend-tasks` as it will be deleted in near future.
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- 3123c16: Fix package metadata
+- 7c5f3b0: Explicit declare if the service ref accepts `single` or `multiple` implementations.
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-techdocs-common@0.1.0
+
+### Minor Changes
+
+- 4698e1f: Initial release of the techdocs-common package.
+
+## @backstage/app-defaults@1.5.10
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-app-api@1.14.2
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-permission-react@0.4.25
+
+## @backstage/backend-defaults@0.4.2
+
+### Patch Changes
+
+- 0d16b52: Add access restrictions to the JWKS external access method config schema
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 3b429fb: Added deprecation warning to urge users to perform the auth service migration or implement their own token manager service.
+ See for more information.
+- 7681b17: update the `morgan` middleware to use a custom format to prevent PII from being logged
+- 4e79d19: The `createHealthRouter` utility that allows you to create a health check router is now exported via `@backstage/backend-defaults/rootHttpRouter`.
+- ba9abf4: The `SchedulerService` now allows tasks with `frequency: { trigger: 'manual' }`. This means that the task will not be scheduled, but rather run only when manually triggered with `SchedulerService.triggerTask`.
+- 78c1329: Updated `GitlabUrlReader.readUrl` and `GitlabUrlReader.readTree` to accept a user-provided token, supporting both bearer and private tokens.
+- 8e967da: Fixed the routing of the new health check service, the health endpoints should now properly be available at `/.backstage/health/v1/readiness` and `/.backstage/health/v1/liveness`.
+- 7c5f3b0: Update the `UrlReader` service to depends on multiple instances of `UrlReaderFactoryProvider` service.
+- 81f930a: use formatted query to prevent chance of SQL-injection
+- 1d5f298: Avoid excessive numbers of error listeners on cache clients
+- Updated dependencies
+ - @backstage/backend-app-api@0.9.0
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/config-loader@1.9.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/backend-dev-utils@0.1.5
+ - @backstage/integration@1.14.0
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/types@1.1.1
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/backend-dev-utils@0.1.5
+
+### Patch Changes
+
+- 3a35172: Fix `EventEmitter` memory leak in the development utilities
+
+## @backstage/backend-openapi-utils@0.1.16
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/errors@1.2.4
+
+## @backstage/catalog-client@1.6.6
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0
+ - @backstage/errors@1.2.4
+
+## @backstage/core-app-api@1.14.2
+
+### Patch Changes
+
+- 9a46a81: The request to delete the session cookie when running the app in protected mode is now done with a plain `fetch` rather than `FetchApi`. This fixes a bug where the app would immediately try to sign-in again when removing the cookie during logout.
+- Updated dependencies
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/core-compat-api@0.2.8
+
+### Patch Changes
+
+- 72754db: Updated usage of `useRouteRef`, which can now always return `undefined`.
+- fe1fbb2: Migrating usages of the deprecated `createExtension` `v1` format to the newer `v2` format, and old `create*Extension` extension creators to blueprints.
+- 16cf96c: Both `compatWrapper` and `convertLegacyRouteRef` now support converting from the new system to the old.
+- 519b8e0: Added new utilities for converting legacy plugins and extensions to the new system. The `convertLegacyPlugin` option will convert an existing plugin to the new system, although you need to supply extensions for the plugin yourself. To help out with this, there is also a new `convertLegacyPageExtension` which converts an existing page extension to the new system.
+- 6349099: Added config input type to the extensions
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/core-components@0.14.10
+
+### Patch Changes
+
+- 678971a: Move the `Link` component to the `RoutedTabs` instead of the `HeaderTabs` component
+- 13a9c63: Corrected the documentation for the GCP IAP auth module and updated the configuration to follow proxy configuration conventions by ignoring authEnv
+- Updated dependencies
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/theme@0.5.6
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/create-app@0.5.18
+
+### Patch Changes
+
+- c0a705d: Added the Kubernetes plugin to `create-app`
+- d7a0aa3: Bumped create-app version.
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 6c1081c: Updated dockerfile and `app-config.production.yaml` to make it easier to get started with example data
+- bfeba46: Included permission config and enabled it out of the box
+- Updated dependencies
+ - @backstage/cli-common@0.1.14
+
+## @backstage/dev-utils@1.0.37
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/core-app-api@1.14.2
+ - @backstage/catalog-model@1.6.0
+ - @backstage/app-defaults@1.5.10
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30
+ - @backstage/theme@0.5.6
+
+## @backstage/frontend-test-utils@0.1.12
+
+### Patch Changes
+
+- 8209449: Added new APIs for testing extensions
+
+- 72754db: Updated usage of `useRouteRef`, which can now always return `undefined`.
+
+- 3be9aeb: Added support for v2 extensions, which declare their inputs and outputs without using a data map.
+
+- fe1fbb2: Migrating usages of the deprecated `createExtension` `v1` format to the newer `v2` format, and old `create*Extension` extension creators to blueprints.
+
+- 2d21599: Added support for being able to override extension definitions.
+
+ ```tsx
+ const TestCard = EntityCardBlueprint.make({
+ ...
+ });
+
+ TestCard.override({
+ // override attachment points
+ attachTo: { id: 'something-else', input: 'overridden' },
+ // extend the config schema
+ config: {
+ schema: {
+ newConfig: z => z.string().optional(),
+ }
+ },
+ // override factory
+ *factory(originalFactory, { inputs, config }){
+ const originalOutput = originalFactory();
+
+ yield coreExentsionData.reactElement(
+
+ {originalOutput.get(coreExentsionData.reactElement)}
+
+ );
+ }
+ });
+
+ ```
+
+- c00e1a0: Deprecate the `.render` method of the `createExtensionTester` in favour of using `renderInTestApp` directly.
+
+ ```tsx
+ import {
+ renderInTestApp,
+ createExtensionTester,
+ } from '@backstage/frontend-test-utils';
+
+ const tester = createExtensionTester(extension);
+
+ const { getByTestId } = renderInTestApp(tester.reactElement());
+
+ // or if you're not using `coreExtensionData.reactElement` as the output ref
+ const { getByTestId } = renderInTestApp(tester.get(myComponentRef));
+ ```
+
+- 264e10f: Deprecate existing `ExtensionCreators` in favour of their new Blueprint counterparts.
+
+- 264e10f: Refactor `.make` method on Blueprints into two different methods, `.make` and `.makeWithOverrides`.
+
+ When using `createExtensionBlueprint` you can define parameters for the factory function, if you wish to take advantage of these parameters you should use `.make` when creating an extension instance of a Blueprint. If you wish to override more things other than the standard `attachTo`, `name`, `namespace` then you should use `.makeWithOverrides` instead.
+
+ `.make` is reserved for simple creation of extension instances from Blueprints using higher level parameters, whereas `.makeWithOverrides` is lower level and you have more control over the final extension.
+
+- 6349099: Added config input type to the extensions
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/frontend-app-api@0.8.0
+ - @backstage/config@1.2.0
+ - @backstage/test-utils@1.5.10
+ - @backstage/types@1.1.1
+
+## @backstage/integration-react@1.1.30
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+
+## @backstage/repo-tools@0.9.5
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/config-loader@1.9.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/cli-common@0.1.14
+ - @backstage/cli-node@0.2.7
+ - @backstage/errors@1.2.4
+
+## @techdocs/cli@1.8.17
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/plugin-techdocs-node@1.12.9
+ - @backstage/catalog-model@1.6.0
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+
+## @backstage/test-utils@1.5.10
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/core-app-api@1.14.2
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/plugin-permission-react@0.4.25
+
+## @backstage/plugin-api-docs@0.11.8
+
+### Patch Changes
+
+- 770ba02: `ConsumingComponentsCard` and `ProvidingComponentsCard` will now optionally accept `columns` to override which table columns are displayed
+- fe1fbb2: Migrating usages of the deprecated `createExtension` `v1` format to the newer `v2` format, and old `create*Extension` extension creators to blueprints.
+- ebfeb40: Added `resolvers` prop to `AsyncApiDefinitionWidget`. This allows to override the default http/https resolvers, for example to add authentication to requests to internal schema registries.
+- 4b6d2cb: Updated dependency `@graphiql/react` to `^0.23.0`.
+- 6582799: Add `tableOptions` to all tables and additionally `title` to API tables.
+- Updated dependencies
+ - @backstage/plugin-catalog@1.22.0
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/catalog-model@1.6.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-permission-react@0.4.25
+
+## @backstage/plugin-app-backend@0.3.72
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 6bd6fda: Deprecate `createRouter` and its options in favour of the new backend system.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/config-loader@1.9.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-app-node@0.1.23
+
+## @backstage/plugin-app-node@0.1.23
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/config-loader@1.9.0
+
+## @backstage/plugin-app-visualizer@0.1.9
+
+### Patch Changes
+
+- 72754db: Updated usage of `useRouteRef`, which can now always return `undefined`.
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- e493020: Fixing issue with the visualizer crashing when clicking on the detailed view because of `routeRef` parameters
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/core-components@0.14.10
+ - @backstage/core-plugin-api@1.9.3
+
+## @backstage/plugin-auth-backend@0.22.10
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- cc9a7a5: Deprecated `createRouter` and its router options in favour of the new backend system.
+- Updated dependencies
+ - @backstage/plugin-auth-backend-module-cloudflare-access-provider@0.2.0
+ - @backstage/plugin-auth-backend-module-atlassian-provider@0.2.4
+ - @backstage/plugin-auth-backend-module-bitbucket-provider@0.1.6
+ - @backstage/plugin-auth-backend-module-microsoft-provider@0.1.18
+ - @backstage/plugin-auth-backend-module-onelogin-provider@0.1.4
+ - @backstage/plugin-auth-backend-module-aws-alb-provider@0.1.15
+ - @backstage/plugin-auth-backend-module-gcp-iap-provider@0.2.18
+ - @backstage/plugin-auth-backend-module-github-provider@0.1.20
+ - @backstage/plugin-auth-backend-module-gitlab-provider@0.1.20
+ - @backstage/plugin-auth-backend-module-google-provider@0.1.20
+ - @backstage/plugin-auth-backend-module-oauth2-provider@0.2.4
+ - @backstage/plugin-auth-backend-module-oidc-provider@0.2.4
+ - @backstage/plugin-auth-backend-module-okta-provider@0.0.16
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-backend-module-azure-easyauth-provider@0.1.6
+ - @backstage/plugin-auth-backend-module-oauth2-proxy-provider@0.1.16
+
+## @backstage/plugin-auth-backend-module-atlassian-provider@0.2.4
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-aws-alb-provider@0.1.15
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+
+- 4ea354f: Added a `signer` configuration option to validate against the token claims. We strongly recommend that you set this value (typically on the format `arn:aws:elasticloadbalancing:us-east-2:123456789012:loadbalancer/app/my-load-balancer/1234567890123456`) to ensure that the auth provider can safely check the authenticity of any incoming tokens.
+
+ Example:
+
+ ```diff
+ auth:
+ providers:
+ awsalb:
+ # this is the URL of the IdP you configured
+ issuer: 'https://example.okta.com/oauth2/default'
+ # this is the ARN of your ALB instance
+ + signer: 'arn:aws:elasticloadbalancing:us-east-2:123456789012:loadbalancer/app/my-load-balancer/1234567890123456'
+ # this is the region where your ALB instance resides
+ region: 'us-west-2'
+ signIn:
+ resolvers:
+ # typically you would pick one of these
+ - resolver: emailMatchingUserEntityProfileEmail
+ - resolver: emailLocalPartMatchingUserEntityName
+ ```
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-auth-backend@0.22.10
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-auth-backend-module-azure-easyauth-provider@0.1.6
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-auth-backend-module-bitbucket-provider@0.1.6
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-gcp-iap-provider@0.2.18
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- 13a9c63: Corrected the documentation for the GCP IAP auth module and updated the configuration to follow proxy configuration conventions by ignoring authEnv
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-auth-backend-module-github-provider@0.1.20
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-gitlab-provider@0.1.20
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-google-provider@0.1.20
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-guest-provider@0.1.9
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-auth-backend-module-microsoft-provider@0.1.18
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 39f36a9: Updated the Microsoft authenticator to accurately define required scopes, but to also omit the required and additional scopes when requesting resource scopes.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-oauth2-provider@0.2.4
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-oauth2-proxy-provider@0.1.16
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-auth-backend-module-oidc-provider@0.2.4
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-auth-backend@0.22.10
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-okta-provider@0.0.16
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-onelogin-provider@0.1.4
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+
+## @backstage/plugin-auth-backend-module-pinniped-provider@0.1.17
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/config@1.2.0
+
+## @backstage/plugin-auth-backend-module-vmware-cloud-provider@0.2.4
+
+### Patch Changes
+
+- c8f1cae: Add `signIn` to authentication provider configuration schema
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/catalog-model@1.6.0
+
+## @backstage/plugin-auth-react@0.1.5
+
+### Patch Changes
+
+- aeac3e9: feat: Hide visibility of CookieAuthRedirect
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-bitbucket-cloud-common@0.2.22
+
+### Patch Changes
+
+- 3fca643: Added method `listBranchesByRepository` to `BitbucketCloudClient`
+- Updated dependencies
+ - @backstage/integration@1.14.0
+
+## @backstage/plugin-catalog-backend-module-logs@0.0.2
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-backend@1.25.0
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-catalog-backend-module-openapi@0.1.41
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-catalog-backend@1.25.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.1.21
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-scaffolder-common@1.5.5
+
+## @backstage/plugin-catalog-backend-module-unprocessed@0.4.10
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-catalog-unprocessed-entities-common@0.0.4
+
+## @backstage/plugin-catalog-common@1.0.26
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/catalog-model@1.6.0
+
+## @backstage/plugin-catalog-graph@0.4.8
+
+### Patch Changes
+
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- fba7537: Memoize entity graph nodes when applying an `entityFilter` to prevent repeated redraws
+- 4a529c2: Use `entityPresentationApi` for the node title and the icon.
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-catalog-import@0.12.2
+
+### Patch Changes
+
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration-react@1.1.30
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-catalog-node@1.12.5
+
+### Patch Changes
+
+- a629fb2: Added setAllowedLocationTypes while introducing a new extension point called CatalogLocationsExtensionPoint
+- 7c5f3b0: Explicit declare if the service ref accepts `single` or `multiple` implementations.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-catalog-react@1.12.3
+
+### Patch Changes
+
+- 7bd27e1: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead.
+- 31bfc44: Updated alpha definitions of extension data references.
+- 7ca331c: Correct `EntityDisplayName`'s icon alignment with the text.
+- 9b89b82: Internal refactor to remove unnecessary `routable` prop in the implementation of the `createEntityContentExtension` alpha export.
+- bebd569: Fix extra divider displayed on user list picker component
+- 519b8e0: Added utilities for converting existing entity card and content extensions to the new frontend system. This is in particular useful when used in combination with the new `convertLegacyPlugin` utility from `@backstage/core-compat-api`.
+- d001a42: Fix label related accessibility issues with `FavorityEntity`
+- 012e3eb: Entity page extensions created for the new frontend system via the `/alpha` exports will now be enabled by default.
+- 6349099: Added config input type to the extensions
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/core-components@0.14.10
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration-react@1.1.30
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-permission-react@0.4.25
+
+## @backstage/plugin-catalog-unprocessed-entities@0.2.7
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/catalog-model@1.6.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-catalog-unprocessed-entities-common@0.0.4
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
+
+## @backstage/plugin-config-schema@0.1.58
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-devtools@0.1.17
+
+### Patch Changes
+
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-devtools-common@0.1.12
+ - @backstage/plugin-permission-react@0.4.25
+
+## @backstage/plugin-devtools-backend@0.3.9
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 32a38e1: Removed unused code for lockfile analysis.
+- 2886ef7: Deprecated `createRouter` and its router options in favour of the new backend system.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/config-loader@1.9.0
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-devtools-common@0.1.12
+
+## @backstage/plugin-devtools-common@0.1.12
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-events-backend@0.3.10
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/config@1.2.0
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-events-backend-module-azure@0.2.9
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-events-backend-module-bitbucket-cloud@0.2.9
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-events-backend-module-gerrit@0.2.9
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-events-backend-module-github@0.2.9
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/config@1.2.0
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-events-backend-module-gitlab@0.2.9
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/config@1.2.0
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-events-backend-test-utils@0.1.33
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-events-node@0.3.9
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+
+## @backstage/plugin-home@0.7.9
+
+### Patch Changes
+
+- 31bfc44: Updated alpha definitions of extension data references.
+- fe1fbb2: Migrating usages of the deprecated `createExtension` `v1` format to the newer `v2` format, and old `create*Extension` extension creators to blueprints.
+- fdcc059: Fixed a bug on the WelcomeTitle component where the welcome message wasn't correct when the language was set to Spanish
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/core-app-api@1.14.2
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-home-react@0.1.16
+
+## @backstage/plugin-home-react@0.1.16
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-plugin-api@1.9.3
+
+## @backstage/plugin-kubernetes@0.11.13
+
+### Patch Changes
+
+- e6c15cc: Adds support for Backstage's new frontend system, available via the `/alpha` sub-path export.
+- fe1fbb2: Migrating usages of the deprecated `createExtension` `v1` format to the newer `v2` format, and old `create*Extension` extension creators to blueprints.
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/plugin-kubernetes-react@0.4.2
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/catalog-model@1.6.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/plugin-kubernetes-common@0.8.2
+
+## @backstage/plugin-kubernetes-backend@0.18.4
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- b63d378: Update internal imports
+- 8c1aa06: Add `kubernetes.clusterLocatorMethods[].clusters[].customResources` to the configuration schema.
+ This was already documented and supported by the plugin.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-kubernetes-node@0.1.17
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/types@1.1.1
+ - @backstage/plugin-kubernetes-common@0.8.2
+
+## @backstage/plugin-kubernetes-cluster@0.0.14
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/plugin-kubernetes-react@0.4.2
+ - @backstage/core-components@0.14.10
+ - @backstage/catalog-model@1.6.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/plugin-kubernetes-common@0.8.2
+
+## @backstage/plugin-kubernetes-common@0.8.2
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/catalog-model@1.6.0
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-kubernetes-node@0.1.17
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- b63d378: Update internal imports
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-kubernetes-common@0.8.2
+
+## @backstage/plugin-kubernetes-react@0.4.2
+
+### Patch Changes
+
+- 954a593: `Liveness Probe` added in ContainerCard Component of PodDrawer
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/catalog-model@1.6.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-kubernetes-common@0.8.2
+
+## @backstage/plugin-notifications-backend@0.3.4
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- d55b8e3: Avoid sending broadcast emails as a fallback in case the entity-typed notification user can not be resolved.
+- 8013044: fix: consider broadcast union with user
+- 7a05f50: Allow using notifications without users in the catalog
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-notifications-node@0.2.4
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-events-node@0.3.9
+ - @backstage/plugin-notifications-common@0.0.5
+ - @backstage/plugin-signals-node@0.1.9
+
+## @backstage/plugin-notifications-node@0.2.4
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/plugin-notifications-common@0.0.5
+ - @backstage/plugin-signals-node@0.1.9
+
+## @backstage/plugin-org@0.6.28
+
+### Patch Changes
+
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/catalog-model@1.6.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-org-react@0.1.27
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/core-plugin-api@1.9.3
+
+## @backstage/plugin-permission-backend@0.5.47
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-permission-backend-module-allow-all-policy@0.1.20
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-permission-node@0.8.1
+
+## @backstage/plugin-permission-common@0.8.1
+
+### Patch Changes
+
+- df784fe: Add the MetadataResponse type from @backstage/plugin-permission-node, since this
+ type might be used in frontend code.
+- 137fa34: Add the MetadataResponseSerializedRule type from @backstage/plugin-permission-node, since this type might be used in frontend code.
+- Updated dependencies
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-permission-node@0.8.1
+
+### Patch Changes
+
+- df784fe: The MetadataResponse type has been moved to @backstage/plugin-permission-common
+ to match the recent move of MetadataResponseSerializedRule, and should be
+ imported from there going forward. To avoid an immediate breaking change, this
+ type is still re-exported from this package, but is marked as deprecated and
+ will be removed in a future release.
+- 5cd9878: The MetadataResponseSerializedRule type has been moved to @backstage/plugin-permission-common, and should be imported from there going forward. To avoid an immediate breaking change, this type is still re-exported from this package, but is marked as deprecated and will be removed in a future release.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-permission-react@0.4.25
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+
+## @backstage/plugin-proxy-backend@0.5.4
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- b63d378: Update internal imports
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/config@1.2.0
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-scaffolder-backend-module-azure@0.1.15
+
+### Patch Changes
+
+- 187f583: Added examples for publish:azure action and updated its test cases
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-bitbucket@0.2.13
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/plugin-scaffolder-backend-module-bitbucket-server@0.1.13
+ - @backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.1.13
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.1.13
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 3fca643: Added autocompletion support for resource `branches`
+- d57967c: Add ability to set the initial commit message when initializing a repository using the scaffolder action.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/plugin-bitbucket-cloud-common@0.2.22
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-bitbucket-server@0.1.13
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- e3b64be: Added examples for publish:bitbucketServer action and improve its test cases
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-confluence-to-markdown@0.2.24
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-cookiecutter@0.2.47
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- dae85df: Add examples for `fetch:cookiecutter` scaffolder action & improve related tests
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-scaffolder-backend-module-gcp@0.1.1
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-gerrit@0.1.15
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-gitea@0.1.13
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 24de005: Added test cases for publish:gitea examples
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-github@0.4.1
+
+### Patch Changes
+
+- d21d307: Added examples for github:environment:create action and improve its test cases
+- 6d4cb97: Added examples for github:repo:create action and improved test cases
+- cd203f1: Added examples for action github:pages and improved its test cases
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-gitlab@0.4.5
+
+### Patch Changes
+
+- da97131: Added test cases for gitlab:issues:create examples
+
+- fad1b90: Allow the `createGitlabProjectVariableAction` to use oauth tokens
+
+- aab708e: Added test cases for gitlab:issue:edit examples
+
+- ef742dc: Added test cases for gitlab:projectAccessToken:create example
+
+- 1ba4c2f: Added test cases for gitlab:pipeline:trigger examples
+
+- a6603e4: Add custom action for merge request: **auto**
+
+ The **Auto** action selects the committed action between _create_ and _update_.
+
+ The **Auto** action fetches files using the **/projects/repository/tree endpoint**.
+ After fetching, it checks if the file exists locally and in the repository. If it does, it chooses **update**; otherwise, it chooses **create**.
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-notifications@0.0.6
+
+### Patch Changes
+
+- 6fc03c7: Add examples for notification:send scaffolder action & improve related tests
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/plugin-notifications-node@0.2.4
+ - @backstage/plugin-notifications-common@0.0.5
+
+## @backstage/plugin-scaffolder-backend-module-rails@0.4.40
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- 449def7: Add examples for fetch:rails scaffolder action & improve related tests
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/integration@1.14.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-scaffolder-backend-module-sentry@0.1.31
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- 382e868: Added test cases for sentry:project:create examples
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-scaffolder-backend-module-yeoman@0.3.7
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/types@1.1.1
+ - @backstage/plugin-scaffolder-node-test-utils@0.1.10
+
+## @backstage/plugin-scaffolder-common@1.5.5
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/catalog-model@1.6.0
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-scaffolder-node@0.4.9
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- c544f81: Add support for status filtering in scaffolder tasks endpoint
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/integration@1.14.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-scaffolder-common@1.5.5
+
+## @backstage/plugin-scaffolder-node-test-utils@0.1.10
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-common@0.24.0
+ - @backstage/backend-test-utils@0.5.0
+ - @backstage/plugin-scaffolder-node@0.4.9
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-search@1.4.15
+
+### Patch Changes
+
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- 3123c16: Fix package metadata
+- 6349099: Added config input type to the extensions
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/plugin-search-react@1.7.14
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/plugin-search-backend@1.5.15
+
+### Patch Changes
+
+- 3123c16: Fix package metadata
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/backend-openapi-utils@0.1.16
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-search-backend-module-elasticsearch@1.5.4
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/config@1.2.0
+ - @backstage/integration-aws-node@0.1.12
+
+## @backstage/plugin-search-backend-module-pg@0.5.33
+
+### Patch Changes
+
+- 7251567: Removing `@backstage/backend-app-api` dependency
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/config@1.2.0
+
+## @backstage/plugin-search-common@1.2.14
+
+### Patch Changes
+
+- 3123c16: Fix package metadata
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-search-react@1.7.14
+
+### Patch Changes
+
+- 7bd27e1: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead.
+- 31bfc44: Updated alpha definitions of extension data references.
+- 3123c16: Fix package metadata
+- 6349099: Added config input type to the extensions
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/core-components@0.14.10
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/plugin-signals@0.0.9
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/plugin-signals-react@0.0.4
+
+## @backstage/plugin-signals-backend@0.1.9
+
+### Patch Changes
+
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/config@1.2.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-events-node@0.3.9
+ - @backstage/plugin-signals-node@0.1.9
+
+## @backstage/plugin-signals-node@0.1.9
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/config@1.2.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-events-node@0.3.9
+
+## @backstage/plugin-techdocs@1.10.8
+
+### Patch Changes
+
+- 69bd940: Use annotation constants from new techdocs-common package.
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- 27794d1: Allow for more granular control of TechDocsReaderPage styling. Theme overrides can now be provided to TechDocs without affecting the theme in other areas of Backstage.
+- 4490d73: Refactor TechDocs' mkdocs-redirects support.
+- 8543e72: TechDocs redirect feature now includes a notification to the user before they are redirected.
+- 67e76f2: TechDocs now supports the `mkdocs-redirects` plugin. Redirects defined using the `mkdocs-redirect` plugin will be handled automatically in TechDocs. Redirecting to external urls is not supported. In the case that an external redirect url is provided, TechDocs will redirect to the current documentation site home.
+- bdc5471: Fixed issue where header styles were incorrectly generated when themes used CSS variables to define font size.
+- 6349099: Added config input type to the extensions
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/plugin-search-react@1.7.14
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/integration@1.14.0
+ - @backstage/plugin-techdocs-common@0.1.0
+ - @backstage/plugin-auth-react@0.1.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration-react@1.1.30
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-techdocs-react@1.2.7
+
+## @backstage/plugin-techdocs-addons-test-utils@1.0.37
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-catalog@1.22.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/plugin-search-react@1.7.14
+ - @backstage/plugin-techdocs@1.10.8
+ - @backstage/core-app-api@1.14.2
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30
+ - @backstage/test-utils@1.5.10
+ - @backstage/plugin-techdocs-react@1.2.7
+
+## @backstage/plugin-techdocs-backend@1.10.10
+
+### Patch Changes
+
+- 69bd940: Use annotation constants from new techdocs-common package.
+- 93095ee: Make sure node-fetch is version 2.7.0 or greater
+- b77fbf4: Added back `type: 'local'` to TechDocs config schema for `publisher`
+- a16632c: Update configuration schema to match actual behavior
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-techdocs-node@1.12.9
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-search-backend-module-techdocs@0.2.0
+ - @backstage/integration@1.14.0
+ - @backstage/plugin-techdocs-common@0.1.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-catalog-common@1.0.26
+
+## @backstage/plugin-techdocs-module-addons-contrib@1.1.13
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/integration@1.14.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30
+ - @backstage/plugin-techdocs-react@1.2.7
+
+## @backstage/plugin-techdocs-node@1.12.9
+
+### Patch Changes
+
+- 389f5a4: Update deprecated url-reader-related imports.
+- 69bd940: Use annotation constants from new techdocs-common package.
+- 949083d: Update `patchMkdocsYmlPrebuild` to modify `repo_url` and `edit_uri` independently.
+- 5cedd9f: Fix TechDocs Edit URL for nested docs
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/integration@1.14.0
+ - @backstage/plugin-techdocs-common@0.1.0
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration-aws-node@0.1.12
+
+## @backstage/plugin-techdocs-react@1.2.7
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/catalog-model@1.6.0
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/plugin-user-settings@0.8.11
+
+### Patch Changes
+
+- c7603e8: Deprecate the old pattern of `create*Extension`, and replace it with the equivalent Blueprint implementation instead
+- 6349099: Added config input type to the extensions
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/core-components@0.14.10
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/core-app-api@1.14.2
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/plugin-signals-react@0.0.4
+ - @backstage/plugin-user-settings-common@0.0.1
+
+## @backstage/plugin-user-settings-backend@0.2.22
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-signals-node@0.1.9
+ - @backstage/plugin-user-settings-common@0.0.1
+
+## example-app@0.2.100
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-catalog@1.22.0
+ - @backstage/plugin-scaffolder@1.24.0
+ - @backstage/plugin-scaffolder-react@1.11.0
+ - @backstage/cli@0.27.0
+ - @backstage/plugin-notifications@0.3.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/plugin-search-react@1.7.14
+ - @backstage/plugin-home@0.7.9
+ - @backstage/plugin-techdocs@1.10.8
+ - @backstage/core-components@0.14.10
+ - @backstage/plugin-api-docs@0.11.8
+ - @backstage/frontend-app-api@0.8.0
+ - @backstage/plugin-catalog-graph@0.4.8
+ - @backstage/plugin-catalog-import@0.12.2
+ - @backstage/plugin-devtools@0.1.17
+ - @backstage/plugin-org@0.6.28
+ - @backstage/plugin-search@1.4.15
+ - @backstage/plugin-user-settings@0.8.11
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/plugin-kubernetes@0.11.13
+ - @backstage/core-app-api@1.14.2
+ - @backstage/plugin-auth-react@0.1.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/app-defaults@1.5.10
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-catalog-unprocessed-entities@0.2.7
+ - @backstage/plugin-kubernetes-cluster@0.0.14
+ - @backstage/plugin-permission-react@0.4.25
+ - @backstage/plugin-signals@0.0.9
+ - @backstage/plugin-techdocs-module-addons-contrib@1.1.13
+ - @backstage/plugin-techdocs-react@1.2.7
+
+## example-app-next@0.0.14
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-catalog@1.22.0
+ - @backstage/plugin-scaffolder@1.24.0
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-scaffolder-react@1.11.0
+ - @backstage/cli@0.27.0
+ - @backstage/plugin-notifications@0.3.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/plugin-search-react@1.7.14
+ - @backstage/plugin-home@0.7.9
+ - @backstage/plugin-techdocs@1.10.8
+ - @backstage/core-components@0.14.10
+ - @backstage/plugin-api-docs@0.11.8
+ - @backstage/frontend-app-api@0.8.0
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/plugin-app-visualizer@0.1.9
+ - @backstage/plugin-catalog-graph@0.4.8
+ - @backstage/plugin-catalog-import@0.12.2
+ - @backstage/plugin-org@0.6.28
+ - @backstage/plugin-search@1.4.15
+ - @backstage/plugin-user-settings@0.8.11
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/plugin-kubernetes@0.11.13
+ - @backstage/core-app-api@1.14.2
+ - @backstage/plugin-auth-react@0.1.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/app-defaults@1.5.10
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-catalog-unprocessed-entities@0.2.7
+ - @backstage/plugin-kubernetes-cluster@0.0.14
+ - @backstage/plugin-permission-react@0.4.25
+ - @backstage/plugin-signals@0.0.9
+ - @backstage/plugin-techdocs-module-addons-contrib@1.1.13
+ - @backstage/plugin-techdocs-react@1.2.7
+
+## app-next-example-plugin@0.0.14
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/core-components@0.14.10
+
+## example-backend@0.0.29
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/plugin-scaffolder-backend-module-github@0.4.1
+ - @backstage/plugin-auth-backend-module-github-provider@0.1.20
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/plugin-catalog-backend@1.25.0
+ - @backstage/plugin-catalog-backend-module-openapi@0.1.41
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-scaffolder-backend@1.24.0
+ - @backstage/plugin-techdocs-backend@1.10.10
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-search-backend-module-techdocs@0.2.0
+ - @backstage/plugin-search-backend-module-explore@0.2.0
+ - @backstage/plugin-notifications-backend@0.3.4
+ - @backstage/plugin-kubernetes-backend@0.18.4
+ - @backstage/plugin-permission-backend@0.5.47
+ - @backstage/plugin-devtools-backend@0.3.9
+ - @backstage/plugin-signals-backend@0.1.9
+ - @backstage/plugin-proxy-backend@0.5.4
+ - @backstage/plugin-auth-backend@0.22.10
+ - @backstage/plugin-app-backend@0.3.72
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/plugin-catalog-backend-module-backstage-openapi@0.3.0
+ - @backstage/plugin-search-backend-module-catalog@0.2.0
+ - @backstage/plugin-search-backend@1.5.15
+ - @backstage/catalog-model@1.6.0
+ - @backstage/plugin-auth-backend-module-guest-provider@0.1.9
+ - @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.1.21
+ - @backstage/plugin-catalog-backend-module-unprocessed@0.4.10
+ - @backstage/plugin-permission-backend-module-allow-all-policy@0.1.20
+
+## example-backend-legacy@0.2.101
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-catalog-backend@1.25.0
+ - @backstage/plugin-scaffolder-backend-module-confluence-to-markdown@0.2.24
+ - @backstage/plugin-scaffolder-backend-module-rails@0.4.40
+ - @backstage/plugin-search-backend-node@1.3.0
+ - @backstage/plugin-scaffolder-backend@1.24.0
+ - @backstage/plugin-techdocs-backend@1.10.10
+ - @backstage/plugin-permission-common@0.8.1
+ - @backstage/plugin-search-backend-module-techdocs@0.2.0
+ - @backstage/plugin-search-backend-module-explore@0.2.0
+ - @backstage/plugin-kubernetes-backend@0.18.4
+ - @backstage/plugin-permission-backend@0.5.47
+ - @backstage/plugin-devtools-backend@0.3.9
+ - @backstage/plugin-signals-backend@0.1.9
+ - @backstage/plugin-proxy-backend@0.5.4
+ - @backstage/plugin-auth-backend@0.22.10
+ - @backstage/plugin-app-backend@0.3.72
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/plugin-permission-node@0.8.1
+ - @backstage/plugin-scaffolder-backend-module-gitlab@0.4.5
+ - @backstage/plugin-search-backend-module-catalog@0.2.0
+ - @backstage/plugin-search-backend@1.5.15
+ - @backstage/plugin-catalog-node@1.12.5
+ - @backstage/integration@1.14.0
+ - @backstage/plugin-search-backend-module-pg@0.5.33
+ - @backstage/catalog-model@1.6.0
+ - @backstage/catalog-client@1.6.6
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.1.21
+ - @backstage/plugin-catalog-backend-module-unprocessed@0.4.10
+ - @backstage/plugin-events-backend@0.3.10
+ - @backstage/plugin-events-node@0.3.9
+ - @backstage/plugin-search-backend-module-elasticsearch@1.5.4
+ - @backstage/plugin-signals-node@0.1.9
+
+## e2e-test@0.2.19
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/create-app@0.5.18
+ - @backstage/cli-common@0.1.14
+ - @backstage/errors@1.2.4
+
+## techdocs-cli-embedded-app@0.2.99
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-catalog@1.22.0
+ - @backstage/cli@0.27.0
+ - @backstage/plugin-techdocs@1.10.8
+ - @backstage/core-components@0.14.10
+ - @backstage/core-app-api@1.14.2
+ - @backstage/catalog-model@1.6.0
+ - @backstage/app-defaults@1.5.10
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30
+ - @backstage/test-utils@1.5.10
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-techdocs-react@1.2.7
+
+## @internal/plugin-todo-list@1.0.30
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-plugin-api@1.9.3
+
+## @internal/plugin-todo-list-backend@1.0.30
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0
+ - @backstage/backend-common@0.24.0
+ - @backstage/plugin-auth-node@0.5.0
+ - @backstage/errors@1.2.4
+
+## @internal/plugin-todo-list-common@1.0.21
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-permission-common@0.8.1
diff --git a/docs/releases/v1.30.0-next.4-changelog.md b/docs/releases/v1.30.0-next.4-changelog.md
new file mode 100644
index 0000000000..433b5f894c
--- /dev/null
+++ b/docs/releases/v1.30.0-next.4-changelog.md
@@ -0,0 +1,2113 @@
+# Release v1.30.0-next.4
+
+Upgrade Helper: [https://backstage.github.io/upgrade-helper/?to=1.30.0-next.4](https://backstage.github.io/upgrade-helper/?to=1.30.0-next.4)
+
+## @backstage/catalog-model@1.6.0-next.0
+
+### Minor Changes
+
+- 34fa803: Introduce an optional spec.type attribute on the Domain and System entity kinds
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-auth-backend-module-cloudflare-access-provider@0.2.0-next.3
+
+### Minor Changes
+
+- 75d026a: Support for Cloudflare Custom Headers and Custom Cookie Auth Name
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-notifications@0.3.0-next.1
+
+### Minor Changes
+
+- 0410fc9: By default, set notification as read when opening snackbar or web notification link
+
+### Patch Changes
+
+- 80b84f7: Fixed issue with notification reloading on page change
+- Updated dependencies
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/plugin-notifications-common@0.0.5
+ - @backstage/plugin-signals-react@0.0.4
+
+## @backstage/plugin-scaffolder@1.24.0-next.3
+
+### Minor Changes
+
+- 1552c33: Changed the way to display entities in `MyGroupsPicker` to use `entityPresentationApi` and make it consistent across scaffolder pickers
+
+### Patch Changes
+
+- 47ed51b: Add an extra bit of height to the EntityPicker dropdown to make it clear there are more options to select from, and to remove the scroll bar when there is less than 10 options
+- d18f4eb: Fix undefined in the title of Scaffolder Runs on the page load
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-permission-react@0.4.25-next.1
+ - @backstage/plugin-scaffolder-common@1.5.5-next.2
+ - @backstage/plugin-scaffolder-react@1.11.0-next.3
+
+## @backstage/backend-app-api@0.8.1-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/cli-common@0.1.14
+ - @backstage/cli-node@0.2.7
+ - @backstage/config@1.2.0
+ - @backstage/config-loader@1.9.0-next.2
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-permission-node@0.8.1-next.3
+
+## @backstage/backend-common@0.23.4-next.3
+
+### Patch Changes
+
+- ddde5fe: Internal type refactor.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-dev-utils@0.1.4
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+ - @backstage/config-loader@1.9.0-next.2
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/backend-defaults@0.4.2-next.3
+
+### Patch Changes
+
+- 81f930a: use formatted query to prevent chance of SQL-injection
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-app-api@0.8.1-next.3
+ - @backstage/backend-dev-utils@0.1.4
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+ - @backstage/config-loader@1.9.0-next.2
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+ - @backstage/plugin-permission-node@0.8.1-next.3
+
+## @backstage/backend-dynamic-feature-service@0.2.16-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-app-api@0.8.1-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/cli-common@0.1.14
+ - @backstage/cli-node@0.2.7
+ - @backstage/config@1.2.0
+ - @backstage/config-loader@1.9.0-next.2
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-app-node@0.1.23-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-catalog-backend@1.24.1-next.3
+ - @backstage/plugin-events-backend@0.3.10-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/backend-openapi-utils@0.1.16-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/errors@1.2.4
+
+## @backstage/backend-plugin-api@0.8.0-next.3
+
+### Patch Changes
+
+- ddde5fe: Fixed a type issue where plugin and modules depending on multiton services would not receive the correct type.
+- Updated dependencies
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+
+## @backstage/backend-tasks@0.5.28-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/backend-test-utils@0.4.5-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-defaults@0.4.2-next.3
+ - @backstage/backend-app-api@0.8.1-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/catalog-client@1.6.6-next.0
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/errors@1.2.4
+
+## @backstage/cli@0.27.0-next.4
+
+### Patch Changes
+
+- 6d898d8: Switched the `process` polyfill to use `require.resolve` for greater compatability.
+- 2ced236: Updated dependency `@module-federation/enhanced` to `0.3.1`
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/cli-common@0.1.14
+ - @backstage/cli-node@0.2.7
+ - @backstage/config@1.2.0
+ - @backstage/config-loader@1.9.0-next.2
+ - @backstage/errors@1.2.4
+ - @backstage/eslint-plugin@0.1.8
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/release-manifests@0.0.11
+ - @backstage/types@1.1.1
+
+## @backstage/core-compat-api@0.2.8-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/create-app@0.5.18-next.4
+
+### Patch Changes
+
+- bfeba46: Included permission config and enabled it out of the box
+- Updated dependencies
+ - @backstage/cli-common@0.1.14
+
+## @backstage/dev-utils@1.0.37-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/app-defaults@1.5.10-next.2
+ - @backstage/core-app-api@1.14.2-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/theme@0.5.6
+
+## @backstage/frontend-app-api@0.7.5-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/core-app-api@1.14.2-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/frontend-plugin-api@0.7.0-next.3
+
+### Patch Changes
+
+- 6f72c2b: Fixing issue with extension blueprints `inputs` merging.
+
+- 99abb6b: Support overriding of plugin extensions using the new `plugin.withOverrides` method.
+
+ ```tsx
+ import homePlugin from '@backstage/plugin-home';
+
+ export default homePlugin.withOverrides({
+ extensions: [
+ homePage.getExtension('page:home').override({
+ *factory(originalFactory) {
+ yield* originalFactory();
+ yield coreExtensionData.reactElement(
My custom home page
);
+ },
+ }),
+ ],
+ });
+ ```
+
+- a65cfc8: Add support for accessing extensions definitions provided by a plugin via `plugin.getExtension(...)`. For this to work the extensions must be defined using the v2 format, typically using an extension blueprint.
+
+- 34f1b2a: Support merging of `inputs` in extension blueprints, but stop merging `output`. In addition, the original factory in extension blueprints now returns a data container that both provides access to the returned data, but can also be forwarded as output.
+
+- 2d21599: Added support for being able to override extension definitions.
+
+ ```tsx
+ const TestCard = EntityCardBlueprint.make({
+ ...
+ });
+
+ TestCard.override({
+ // override attachment points
+ attachTo: { id: 'something-else', input: 'overridden' },
+ // extend the config schema
+ config: {
+ schema: {
+ newConfig: z => z.string().optional(),
+ }
+ },
+ // override factory
+ *factory(originalFactory, { inputs, config }){
+ const originalOutput = originalFactory();
+
+ yield coreExentsionData.reactElement(
+
+ {originalOutput.get(coreExentsionData.reactElement)}
+
+ );
+ }
+ });
+
+ ```
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/frontend-test-utils@0.1.12-next.3
+
+### Patch Changes
+
+- 2d21599: Added support for being able to override extension definitions.
+
+ ```tsx
+ const TestCard = EntityCardBlueprint.make({
+ ...
+ });
+
+ TestCard.override({
+ // override attachment points
+ attachTo: { id: 'something-else', input: 'overridden' },
+ // extend the config schema
+ config: {
+ schema: {
+ newConfig: z => z.string().optional(),
+ }
+ },
+ // override factory
+ *factory(originalFactory, { inputs, config }){
+ const originalOutput = originalFactory();
+
+ yield coreExentsionData.reactElement(
+
+ {originalOutput.get(coreExentsionData.reactElement)}
+
+ );
+ }
+ });
+
+ ```
+
+- 264e10f: Deprecate existing `ExtensionCreators` in favour of their new Blueprint counterparts.
+
+- 264e10f: Refactor `.make` method on Blueprints into two different methods, `.make` and `.makeWithOverrides`.
+
+ When using `createExtensionBlueprint` you can define parameters for the factory function, if you wish to take advantage of these parameters you should use `.make` when creating an extension instance of a Blueprint. If you wish to override more things other than the standard `attachTo`, `name`, `namespace` then you should use `.makeWithOverrides` instead.
+
+ `.make` is reserved for simple creation of extension instances from Blueprints using higher level parameters, whereas `.makeWithOverrides` is lower level and you have more control over the final extension.
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/frontend-app-api@0.7.5-next.3
+ - @backstage/config@1.2.0
+ - @backstage/test-utils@1.5.10-next.2
+ - @backstage/types@1.1.1
+
+## @backstage/repo-tools@0.9.5-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/cli-common@0.1.14
+ - @backstage/cli-node@0.2.7
+ - @backstage/config-loader@1.9.0-next.2
+ - @backstage/errors@1.2.4
+
+## @techdocs/cli@1.8.17-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-defaults@0.4.2-next.3
+ - @backstage/plugin-techdocs-node@1.12.9-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+
+## @backstage/plugin-api-docs@0.11.8-next.3
+
+### Patch Changes
+
+- 6582799: Add `tableOptions` to all tables and additionally `title` to API tables.
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/plugin-catalog@1.22.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-permission-react@0.4.25-next.1
+
+## @backstage/plugin-app-backend@0.3.72-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/config-loader@1.9.0-next.2
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-app-node@0.1.23-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-app-node@0.1.23-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config-loader@1.9.0-next.2
+
+## @backstage/plugin-app-visualizer@0.1.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+
+## @backstage/plugin-auth-backend@0.22.10-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/plugin-auth-backend-module-cloudflare-access-provider@0.2.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-backend-module-atlassian-provider@0.2.4-next.3
+ - @backstage/plugin-auth-backend-module-aws-alb-provider@0.1.15-next.3
+ - @backstage/plugin-auth-backend-module-azure-easyauth-provider@0.1.6-next.3
+ - @backstage/plugin-auth-backend-module-bitbucket-provider@0.1.6-next.3
+ - @backstage/plugin-auth-backend-module-gcp-iap-provider@0.2.18-next.3
+ - @backstage/plugin-auth-backend-module-github-provider@0.1.20-next.3
+ - @backstage/plugin-auth-backend-module-gitlab-provider@0.1.20-next.3
+ - @backstage/plugin-auth-backend-module-google-provider@0.1.20-next.3
+ - @backstage/plugin-auth-backend-module-microsoft-provider@0.1.18-next.3
+ - @backstage/plugin-auth-backend-module-oauth2-provider@0.2.4-next.3
+ - @backstage/plugin-auth-backend-module-oauth2-proxy-provider@0.1.16-next.3
+ - @backstage/plugin-auth-backend-module-oidc-provider@0.2.4-next.3
+ - @backstage/plugin-auth-backend-module-okta-provider@0.0.16-next.3
+ - @backstage/plugin-auth-backend-module-onelogin-provider@0.1.4-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+
+## @backstage/plugin-auth-backend-module-atlassian-provider@0.2.4-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-aws-alb-provider@0.1.15-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-backend@0.22.10-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-azure-easyauth-provider@0.1.6-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-bitbucket-provider@0.1.6-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-gcp-iap-provider@0.2.18-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-github-provider@0.1.20-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-gitlab-provider@0.1.20-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-google-provider@0.1.20-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-guest-provider@0.1.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-microsoft-provider@0.1.18-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-oauth2-provider@0.2.4-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-oauth2-proxy-provider@0.1.16-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-oidc-provider@0.2.4-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/plugin-auth-backend@0.22.10-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-okta-provider@0.0.16-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-onelogin-provider@0.1.4-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-pinniped-provider@0.1.17-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-backend-module-vmware-cloud-provider@0.2.4-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-auth-node@0.5.0-next.3
+
+## @backstage/plugin-auth-node@0.5.0-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-catalog@1.22.0-next.3
+
+### Patch Changes
+
+- 6582799: Add `tableOptions` to all tables and additionally `title` to API tables.
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/plugin-search-react@1.7.14-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-permission-react@0.4.25-next.1
+ - @backstage/plugin-scaffolder-common@1.5.5-next.2
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-catalog-backend@1.24.1-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-openapi-utils@0.1.16-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+ - @backstage/plugin-search-backend-module-catalog@0.1.29-next.3
+
+## @backstage/plugin-catalog-backend-module-aws@0.3.18-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-kubernetes-common@0.8.2-next.2
+
+## @backstage/plugin-catalog-backend-module-azure@0.1.43-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+
+## @backstage/plugin-catalog-backend-module-backstage-openapi@0.2.6-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-openapi-utils@0.1.16-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+
+## @backstage/plugin-catalog-backend-module-bitbucket-cloud@0.2.10-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-bitbucket-cloud-common@0.2.22-next.1
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-catalog-backend-module-bitbucket-server@0.1.37-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+
+## @backstage/plugin-catalog-backend-module-gcp@0.1.24-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-kubernetes-common@0.8.2-next.2
+
+## @backstage/plugin-catalog-backend-module-gerrit@0.1.40-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+
+## @backstage/plugin-catalog-backend-module-github@0.6.6-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-catalog-backend@1.24.1-next.3
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-catalog-backend-module-github-org@0.1.18-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-backend-module-github@0.6.6-next.3
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-catalog-backend-module-gitlab@0.3.22-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-catalog-backend-module-gitlab-org@0.0.6-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/plugin-catalog-backend-module-gitlab@0.3.22-next.3
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-catalog-backend-module-incremental-ingestion@0.4.28-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-catalog-backend@1.24.1-next.3
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+
+## @backstage/plugin-catalog-backend-module-ldap@0.7.1-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+
+## @backstage/plugin-catalog-backend-module-logs@0.0.2-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-catalog-backend@1.24.1-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-catalog-backend-module-msgraph@0.5.31-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+
+## @backstage/plugin-catalog-backend-module-openapi@0.1.41-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/config@1.2.0
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-backend@1.24.1-next.3
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+
+## @backstage/plugin-catalog-backend-module-puppetdb@0.1.29-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+
+## @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.1.21-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-scaffolder-common@1.5.5-next.2
+
+## @backstage/plugin-catalog-backend-module-unprocessed@0.4.10-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-catalog-unprocessed-entities-common@0.0.4-next.1
+ - @backstage/plugin-permission-common@0.8.1-next.1
+
+## @backstage/plugin-catalog-common@1.0.26-next.2
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-catalog-graph@0.4.8-next.4
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-catalog-import@0.12.2-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+
+## @backstage/plugin-catalog-node@1.12.5-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+
+## @backstage/plugin-catalog-react@1.12.3-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-react@0.4.25-next.1
+
+## @backstage/plugin-catalog-unprocessed-entities@0.2.7-next.1
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+
+## @backstage/plugin-devtools@0.1.17-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-devtools-common@0.1.12-next.1
+ - @backstage/plugin-permission-react@0.4.25-next.1
+
+## @backstage/plugin-devtools-backend@0.3.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/cli-common@0.1.14
+ - @backstage/config@1.2.0
+ - @backstage/config-loader@1.9.0-next.2
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-devtools-common@0.1.12-next.1
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+
+## @backstage/plugin-events-backend@0.3.10-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-events-backend-module-aws-sqs@0.3.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-events-backend-module-azure@0.2.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-events-backend-module-bitbucket-cloud@0.2.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-events-backend-module-gerrit@0.2.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-events-backend-module-github@0.2.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-events-backend-module-gitlab@0.2.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-events-backend-test-utils@0.1.33-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-events-node@0.3.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+
+## @backstage/plugin-home@0.7.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/core-app-api@1.14.2-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-home-react@0.1.16-next.0
+
+## @backstage/plugin-kubernetes@0.11.13-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/plugin-kubernetes-common@0.8.2-next.2
+ - @backstage/plugin-kubernetes-react@0.4.2-next.3
+
+## @backstage/plugin-kubernetes-backend@0.18.4-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-kubernetes-common@0.8.2-next.2
+ - @backstage/plugin-kubernetes-node@0.1.17-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+
+## @backstage/plugin-kubernetes-cluster@0.0.14-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/plugin-kubernetes-common@0.8.2-next.2
+ - @backstage/plugin-kubernetes-react@0.4.2-next.3
+
+## @backstage/plugin-kubernetes-common@0.8.2-next.2
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-permission-common@0.8.1-next.1
+
+## @backstage/plugin-kubernetes-node@0.1.17-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-kubernetes-common@0.8.2-next.2
+
+## @backstage/plugin-kubernetes-react@0.4.2-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-kubernetes-common@0.8.2-next.2
+
+## @backstage/plugin-notifications-backend@0.3.4-next.3
+
+### Patch Changes
+
+- 7a05f50: Allow using notifications without users in the catalog
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+ - @backstage/plugin-notifications-common@0.0.5
+ - @backstage/plugin-notifications-node@0.2.4-next.3
+ - @backstage/plugin-signals-node@0.1.9-next.3
+
+## @backstage/plugin-notifications-backend-module-email@0.2.0-next.3
+
+### Patch Changes
+
+- 83faf24: Notification email processor supports allowing or denying specific email addresses from receiving notifications
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/types@1.1.1
+ - @backstage/plugin-notifications-common@0.0.5
+ - @backstage/plugin-notifications-node@0.2.4-next.3
+
+## @backstage/plugin-notifications-node@0.2.4-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/plugin-notifications-common@0.0.5
+ - @backstage/plugin-signals-node@0.1.9-next.3
+
+## @backstage/plugin-org@0.6.28-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+
+## @backstage/plugin-org-react@0.1.27-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+
+## @backstage/plugin-permission-backend@0.5.47-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+
+## @backstage/plugin-permission-backend-module-allow-all-policy@0.1.20-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+
+## @backstage/plugin-permission-node@0.8.1-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+
+## @backstage/plugin-proxy-backend@0.5.4-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/types@1.1.1
+
+## @backstage/plugin-scaffolder-backend@1.23.1-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.1.13-next.3
+ - @backstage/plugin-scaffolder-backend-module-azure@0.1.15-next.3
+ - @backstage/plugin-scaffolder-backend-module-gitlab@0.4.5-next.3
+ - @backstage/plugin-scaffolder-backend-module-github@0.4.1-next.3
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-scaffolder-backend-module-bitbucket@0.2.13-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-bitbucket-cloud-common@0.2.22-next.1
+ - @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.1.21-next.3
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+ - @backstage/plugin-scaffolder-backend-module-bitbucket-server@0.1.13-next.3
+ - @backstage/plugin-scaffolder-backend-module-gerrit@0.1.15-next.3
+ - @backstage/plugin-scaffolder-backend-module-gitea@0.1.13-next.3
+ - @backstage/plugin-scaffolder-common@1.5.5-next.2
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-azure@0.1.15-next.3
+
+### Patch Changes
+
+- 187f583: Added examples for publish:azure action and updated its test cases
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-bitbucket@0.2.13-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.1.13-next.3
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-scaffolder-backend-module-bitbucket-server@0.1.13-next.3
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-bitbucket-cloud@0.1.13-next.3
+
+### Patch Changes
+
+- d57967c: Add ability to set the initial commit message when initializing a repository using the scaffolder action.
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-bitbucket-cloud-common@0.2.22-next.1
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-bitbucket-server@0.1.13-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-confluence-to-markdown@0.2.24-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-cookiecutter@0.2.47-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-gcp@0.1.1-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-gerrit@0.1.15-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-gitea@0.1.13-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-github@0.4.1-next.3
+
+### Patch Changes
+
+- 6d4cb97: Added examples for github:repo:create action and improved test cases
+- cd203f1: Added examples for action github:pages and improved its test cases
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-gitlab@0.4.5-next.3
+
+### Patch Changes
+
+- da97131: Added test cases for gitlab:issues:create examples
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-notifications@0.0.6-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/plugin-notifications-common@0.0.5
+ - @backstage/plugin-notifications-node@0.2.4-next.3
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-rails@0.4.40-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-sentry@0.1.31-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-backend-module-yeoman@0.3.7-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/types@1.1.1
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+ - @backstage/plugin-scaffolder-node-test-utils@0.1.10-next.3
+
+## @backstage/plugin-scaffolder-common@1.5.5-next.2
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-permission-common@0.8.1-next.1
+
+## @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-scaffolder-common@1.5.5-next.2
+
+## @backstage/plugin-scaffolder-node-test-utils@0.1.10-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-test-utils@0.4.5-next.3
+ - @backstage/types@1.1.1
+ - @backstage/plugin-scaffolder-node@0.4.9-next.3
+
+## @backstage/plugin-scaffolder-react@1.11.0-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+ - @backstage/plugin-permission-react@0.4.25-next.1
+ - @backstage/plugin-scaffolder-common@1.5.5-next.2
+
+## @backstage/plugin-search@1.4.15-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/plugin-search-react@1.7.14-next.3
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-search-backend@1.5.15-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-defaults@0.4.2-next.3
+ - @backstage/backend-openapi-utils@0.1.16-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-search-backend-module-catalog@0.1.29-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-search-backend-module-elasticsearch@1.5.4-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-search-backend-module-explore@0.1.29-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-search-backend-module-pg@0.5.33-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-search-backend-module-stack-overflow-collator@0.1.16-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-search-backend-module-techdocs@0.1.28-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/plugin-techdocs-node@1.12.9-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-search-backend-node@1.2.28-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-search-react@1.7.14-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+ - @backstage/plugin-search-common@1.2.14-next.1
+
+## @backstage/plugin-signals-backend@0.1.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+ - @backstage/plugin-signals-node@0.1.9-next.3
+
+## @backstage/plugin-signals-node@0.1.9-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+
+## @backstage/plugin-techdocs@1.10.8-next.3
+
+### Patch Changes
+
+- 27794d1: Allow for more granular control of TechDocsReaderPage styling. Theme overrides can now be provided to TechDocs without affecting the theme in other areas of Backstage.
+- 8543e72: TechDocs redirect feature now includes a notification to the user before they are redirected.
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/plugin-search-react@1.7.14-next.3
+ - @backstage/config@1.2.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-auth-react@0.1.5-next.0
+ - @backstage/plugin-search-common@1.2.14-next.1
+ - @backstage/plugin-techdocs-common@0.1.0-next.0
+ - @backstage/plugin-techdocs-react@1.2.7-next.1
+
+## @backstage/plugin-techdocs-addons-test-utils@1.0.37-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-techdocs@1.10.8-next.3
+ - @backstage/plugin-catalog@1.22.0-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/plugin-search-react@1.7.14-next.3
+ - @backstage/core-app-api@1.14.2-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/test-utils@1.5.10-next.2
+ - @backstage/plugin-techdocs-react@1.2.7-next.1
+
+## @backstage/plugin-techdocs-backend@1.10.10-next.3
+
+### Patch Changes
+
+- a16632c: Update configuration schema to match actual behavior
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/plugin-techdocs-node@1.12.9-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-search-backend-module-techdocs@0.1.28-next.3
+ - @backstage/plugin-techdocs-common@0.1.0-next.0
+
+## @backstage/plugin-techdocs-module-addons-contrib@1.1.13-next.1
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/plugin-techdocs-react@1.2.7-next.1
+
+## @backstage/plugin-techdocs-node@1.12.9-next.3
+
+### Patch Changes
+
+- 5cedd9f: Fix TechDocs Edit URL for nested docs
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/integration-aws-node@0.1.12
+ - @backstage/plugin-search-common@1.2.14-next.1
+ - @backstage/plugin-techdocs-common@0.1.0-next.0
+
+## @backstage/plugin-techdocs-react@1.2.7-next.1
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/config@1.2.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/version-bridge@1.0.8
+
+## @backstage/plugin-user-settings@0.8.11-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/core-app-api@1.14.2-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/errors@1.2.4
+ - @backstage/theme@0.5.6
+ - @backstage/types@1.1.1
+ - @backstage/plugin-signals-react@0.0.4
+ - @backstage/plugin-user-settings-common@0.0.1
+
+## @backstage/plugin-user-settings-backend@0.2.22-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/config@1.2.0
+ - @backstage/errors@1.2.4
+ - @backstage/types@1.1.1
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-signals-node@0.1.9-next.3
+ - @backstage/plugin-user-settings-common@0.0.1
+
+## example-app@0.2.100-next.4
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-scaffolder@1.24.0-next.3
+ - @backstage/plugin-notifications@0.3.0-next.1
+ - @backstage/cli@0.27.0-next.4
+ - @backstage/plugin-techdocs@1.10.8-next.3
+ - @backstage/plugin-api-docs@0.11.8-next.3
+ - @backstage/plugin-catalog@1.22.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/frontend-app-api@0.7.5-next.3
+ - @backstage/plugin-catalog-graph@0.4.8-next.4
+ - @backstage/plugin-catalog-import@0.12.2-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/plugin-devtools@0.1.17-next.3
+ - @backstage/plugin-home@0.7.9-next.3
+ - @backstage/plugin-kubernetes@0.11.13-next.3
+ - @backstage/plugin-org@0.6.28-next.3
+ - @backstage/plugin-search@1.4.15-next.3
+ - @backstage/plugin-search-react@1.7.14-next.3
+ - @backstage/plugin-user-settings@0.8.11-next.3
+ - @backstage/app-defaults@1.5.10-next.2
+ - @backstage/config@1.2.0
+ - @backstage/core-app-api@1.14.2-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-auth-react@0.1.5-next.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-unprocessed-entities@0.2.7-next.1
+ - @backstage/plugin-kubernetes-cluster@0.0.14-next.3
+ - @backstage/plugin-permission-react@0.4.25-next.1
+ - @backstage/plugin-scaffolder-react@1.11.0-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+ - @backstage/plugin-signals@0.0.9-next.0
+ - @backstage/plugin-techdocs-module-addons-contrib@1.1.13-next.1
+ - @backstage/plugin-techdocs-react@1.2.7-next.1
+
+## example-app-next@0.0.14-next.4
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-scaffolder@1.24.0-next.3
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/plugin-notifications@0.3.0-next.1
+ - @backstage/cli@0.27.0-next.4
+ - @backstage/plugin-techdocs@1.10.8-next.3
+ - @backstage/plugin-api-docs@0.11.8-next.3
+ - @backstage/plugin-catalog@1.22.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/frontend-app-api@0.7.5-next.3
+ - @backstage/plugin-app-visualizer@0.1.9-next.3
+ - @backstage/plugin-catalog-graph@0.4.8-next.4
+ - @backstage/plugin-catalog-import@0.12.2-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/plugin-home@0.7.9-next.3
+ - @backstage/plugin-kubernetes@0.11.13-next.3
+ - @backstage/plugin-org@0.6.28-next.3
+ - @backstage/plugin-search@1.4.15-next.3
+ - @backstage/plugin-search-react@1.7.14-next.3
+ - @backstage/plugin-user-settings@0.8.11-next.3
+ - @backstage/app-defaults@1.5.10-next.2
+ - @backstage/config@1.2.0
+ - @backstage/core-app-api@1.14.2-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-auth-react@0.1.5-next.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-unprocessed-entities@0.2.7-next.1
+ - @backstage/plugin-kubernetes-cluster@0.0.14-next.3
+ - @backstage/plugin-permission-react@0.4.25-next.1
+ - @backstage/plugin-scaffolder-react@1.11.0-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+ - @backstage/plugin-signals@0.0.9-next.0
+ - @backstage/plugin-techdocs-module-addons-contrib@1.1.13-next.1
+ - @backstage/plugin-techdocs-react@1.2.7-next.1
+
+## app-next-example-plugin@0.0.14-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/core-components@0.14.10-next.0
+
+## example-backend@0.0.29-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-scaffolder-backend-module-github@0.4.1-next.3
+ - @backstage/plugin-notifications-backend@0.3.4-next.3
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/plugin-techdocs-backend@1.10.10-next.3
+ - @backstage/backend-defaults@0.4.2-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-scaffolder-backend@1.23.1-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/plugin-app-backend@0.3.72-next.3
+ - @backstage/plugin-auth-backend@0.22.10-next.3
+ - @backstage/plugin-auth-backend-module-github-provider@0.1.20-next.3
+ - @backstage/plugin-auth-backend-module-guest-provider@0.1.9-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-catalog-backend@1.24.1-next.3
+ - @backstage/plugin-catalog-backend-module-backstage-openapi@0.2.6-next.3
+ - @backstage/plugin-catalog-backend-module-openapi@0.1.41-next.3
+ - @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.1.21-next.3
+ - @backstage/plugin-catalog-backend-module-unprocessed@0.4.10-next.3
+ - @backstage/plugin-devtools-backend@0.3.9-next.3
+ - @backstage/plugin-kubernetes-backend@0.18.4-next.3
+ - @backstage/plugin-permission-backend@0.5.47-next.3
+ - @backstage/plugin-permission-backend-module-allow-all-policy@0.1.20-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+ - @backstage/plugin-proxy-backend@0.5.4-next.3
+ - @backstage/plugin-search-backend@1.5.15-next.3
+ - @backstage/plugin-search-backend-module-catalog@0.1.29-next.3
+ - @backstage/plugin-search-backend-module-explore@0.1.29-next.3
+ - @backstage/plugin-search-backend-module-techdocs@0.1.28-next.3
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-signals-backend@0.1.9-next.3
+
+## example-backend-legacy@0.2.101-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-scaffolder-backend-module-gitlab@0.4.5-next.3
+ - @backstage/plugin-techdocs-backend@1.10.10-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/plugin-scaffolder-backend@1.23.1-next.3
+ - @backstage/backend-tasks@0.5.28-next.3
+ - @backstage/catalog-client@1.6.6-next.0
+ - @backstage/config@1.2.0
+ - @backstage/integration@1.14.0-next.0
+ - @backstage/plugin-app-backend@0.3.72-next.3
+ - @backstage/plugin-auth-backend@0.22.10-next.3
+ - @backstage/plugin-auth-node@0.5.0-next.3
+ - @backstage/plugin-catalog-backend@1.24.1-next.3
+ - @backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.1.21-next.3
+ - @backstage/plugin-catalog-backend-module-unprocessed@0.4.10-next.3
+ - @backstage/plugin-catalog-node@1.12.5-next.3
+ - @backstage/plugin-devtools-backend@0.3.9-next.3
+ - @backstage/plugin-events-backend@0.3.10-next.3
+ - @backstage/plugin-events-node@0.3.9-next.3
+ - @backstage/plugin-kubernetes-backend@0.18.4-next.3
+ - @backstage/plugin-permission-backend@0.5.47-next.3
+ - @backstage/plugin-permission-common@0.8.1-next.1
+ - @backstage/plugin-permission-node@0.8.1-next.3
+ - @backstage/plugin-proxy-backend@0.5.4-next.3
+ - @backstage/plugin-scaffolder-backend-module-confluence-to-markdown@0.2.24-next.3
+ - @backstage/plugin-scaffolder-backend-module-rails@0.4.40-next.3
+ - @backstage/plugin-search-backend@1.5.15-next.3
+ - @backstage/plugin-search-backend-module-catalog@0.1.29-next.3
+ - @backstage/plugin-search-backend-module-elasticsearch@1.5.4-next.3
+ - @backstage/plugin-search-backend-module-explore@0.1.29-next.3
+ - @backstage/plugin-search-backend-module-pg@0.5.33-next.3
+ - @backstage/plugin-search-backend-module-techdocs@0.1.28-next.3
+ - @backstage/plugin-search-backend-node@1.2.28-next.3
+ - @backstage/plugin-signals-backend@0.1.9-next.3
+ - @backstage/plugin-signals-node@0.1.9-next.3
+
+## e2e-test@0.2.19-next.4
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/create-app@0.5.18-next.4
+ - @backstage/cli-common@0.1.14
+ - @backstage/errors@1.2.4
+
+## techdocs-cli-embedded-app@0.2.99-next.4
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/cli@0.27.0-next.4
+ - @backstage/plugin-techdocs@1.10.8-next.3
+ - @backstage/plugin-catalog@1.22.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/app-defaults@1.5.10-next.2
+ - @backstage/config@1.2.0
+ - @backstage/core-app-api@1.14.2-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/test-utils@1.5.10-next.2
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-techdocs-react@1.2.7-next.1
+
+## @internal/plugin-todo-list-backend@1.0.30-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/backend-plugin-api@0.8.0-next.3
+ - @backstage/backend-common@0.23.4-next.3
+ - @backstage/errors@1.2.4
+ - @backstage/plugin-auth-node@0.5.0-next.3
diff --git a/docs/releases/v1.30.0.md b/docs/releases/v1.30.0.md
new file mode 100644
index 0000000000..230dc54813
--- /dev/null
+++ b/docs/releases/v1.30.0.md
@@ -0,0 +1,117 @@
+---
+id: v1.30.0
+title: v1.30.0
+description: Backstage Release v1.30.0
+---
+
+These are the release notes for the v1.30.0 release of [Backstage](https://backstage.io/).
+
+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](https://backstage.io/docs/frontend-system/building-plugins/migrating) to their plugins.**
+
+At the end of last year in the [1.21 release](https://backstage.io/docs/releases/v1.21.0), 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](https://backstage.io/docs/frontend-system/architecture/migrations#130), or can see the ongoing progress in the [meta issue](https://github.com/backstage/backstage/issues/19545). 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/` 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;
+- `SearchResponseFile`: Use `UrlReaderServiceSearchResponseFile` instead.
+
+### BREAKING: Auth Sign In Resolver Priority
+
+Sign-in resolvers configured via `.signIn.resolvers` in your app-config now take precedence over sign-in resolvers passed to `signInResolver` option of `createOAuthProviderFactory`. This effectively makes sign-in resolvers passed via the `signInResolver` the default ones, which you can then override through configuration, simplifying deploying the same code in multiple environments.
+
+### BREAKING: `@backstage/cli`
+
+The lockfile (`yarn.lock`) dependency analysis and mutations have been removed from several commands. This means that `versions:bump` will no longer attempt to deduplicate after bumping and modifying the lockfile.
+
+The `versions:check` command has also been removed as its only purpose was to verify and mutate the lockfile. We recommend using the `yarn dedupe` command instead, or the `yarn-deduplicate` package if you're using Yarn classic, as a replacement. This change was made in order for us to support other Package Managers in the future and remove the coupling with `yarn`.
+
+### BREAKING: `@backstage/backend-test-utils`
+
+- `setupRequestMockHandlers` is removed; use `CreateMockDirectoryOptions` instead.
+- `CreateMockDirectoryOptions` is removed; use `registerMswTestHooks` instead.
+- Stopped exporting the deprecated and internal `isDockerDisabledForTests` helper.
+- Removed `get` method from `ServiceFactoryTester` which is replaced by `getSubject`
+
+### Scaffolder Internationalization
+
+Thanks to [@mario-mui](https://github.com/mario-mui) we now have i18n support for another core feature! Contributed in [#25827](https://github.com/backstage/backstage/pull/25827)
+
+### Dynamic Backend Feature Loaders
+
+You can now use `createBackendFeatureLoader` to dynamically load features in the backend, for example based on runtime configuration, and many other exciting possibilities. Check out [the docs](https://backstage.io/docs/backend-system/architecture/feature-loaders)!
+
+## Security Fixes
+
+The AWS ALB auth provider now has a configuration option `signer`, which should be set to the ARN of your ALB instance. We strongly recommend that you set this configuration value, since it will help strengthen your installation.
+
+Example:
+
+```diff
+ auth:
+ providers:
+ awsalb:
+ issuer: ...
+ # put your actual ARN here
++ signer: 'arn:aws:elasticloadbalancing:us-east-2:123456789012:loadbalancer/app/my-load-balancer/1234567890123456'
+ region: ...
+ signIn:
+ resolvers:
+ - resolver: ...
+```
+
+## Upgrade path
+
+We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for [keeping Backstage updated](https://backstage.io/docs/getting-started/keeping-backstage-updated).
+
+## Links and References
+
+Below you can find a list of links and references to help you learn about and start using this new release.
+
+- [Backstage official website](https://backstage.io/), [documentation](https://backstage.io/docs/), and [getting started guide](https://backstage.io/docs/getting-started/)
+- [GitHub repository](https://github.com/backstage/backstage)
+- Backstage's [versioning and support policy](https://backstage.io/docs/overview/versioning-policy)
+- [Community Discord](https://discord.gg/backstage-687207715902193673) for discussions and support
+- [Changelog](https://github.com/backstage/backstage/tree/master/docs/releases/v1.30.0-changelog.md)
+- Backstage [Demos](https://backstage.io/demos), [Blog](https://backstage.io/blog), [Roadmap](https://backstage.io/docs/overview/roadmap) and [Plugins](https://backstage.io/plugins)
+
+Sign up for our [newsletter](https://info.backstage.spotify.com/newsletter_subscribe) if you want to be informed about what is happening in the world of Backstage.
diff --git a/docs/tutorials/auth-service-migration.md b/docs/tutorials/auth-service-migration.md
index 9e2633a12a..d12b0d5906 100644
--- a/docs/tutorials/auth-service-migration.md
+++ b/docs/tutorials/auth-service-migration.md
@@ -24,6 +24,8 @@ backend:
dangerouslyDisableDefaultAuthPolicy: true
```
+Please note that this functionality will be removed in a future release, and you should migrate to using the new auth services as soon as possible or you would have to support your own service for issuing tokens.
+
In short, this will allow requests through to plugins in your backend, even if they do not include any credentials. The requests will still be treated as unauthenticated however, which not all plugin endpoints may accept. For more information on the impact of this configuration, see the [auth service documentation](../backend-system/core-services/auth.md).
### Migrating the backend
diff --git a/docs/tutorials/setup-opentelemetry.md b/docs/tutorials/setup-opentelemetry.md
index faaeab49f4..cba8ba7049 100644
--- a/docs/tutorials/setup-opentelemetry.md
+++ b/docs/tutorials/setup-opentelemetry.md
@@ -83,6 +83,28 @@ CMD ["node", "--require", "./instrumentation.js", "packages/backend", "--config"
If you need to disable/configure some OpenTelemetry feature there are lots of [environment variables](https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/) which you can tweak.
+### Available Metrics
+
+The following metrics are available:
+
+- `catalog_entities_count`: Total amount of entities in the catalog
+- `catalog_registered_locations_count`: Total amount of registered locations in the catalog
+- `catalog_relations_count`: Total amount of relations between entities
+- `catalog.processed.entities.count`: Amount of entities processed
+- `catalog.processing.duration`: Time spent executing the full processing flow
+- `catalog.processors.duration`: Time spent executing catalog processors
+- `catalog.processing.queue.delay`: The amount of delay between being scheduled for processing, and the start of actually being processed
+- `catalog.stitched.entities.count`: Amount of entities stitched
+- `catalog.stitching.duration`: Time spent executing the full stitching flow
+- `catalog.stitching.queue.length`: Number of entities currently in the stitching queue
+- `catalog.stitching.queue.delay`: The amount of delay between being scheduled for stitching, and the start of actually being stitched
+- `scaffolder.task.count`: Count of task runs
+- `scaffolder.task.duration`: Duration of a task run
+- `scaffolder.step.count`: Count of step runs
+- `scaffolder.step.duration`: Duration of a step runs
+- `backend_tasks.task.runs.count`: Total number of times a task has been run
+- `backend_tasks.task.runs.duration`: Histogram of task run durations
+
## References
- [Getting started with OpenTelemetry Node.js](https://opentelemetry.io/docs/instrumentation/js/getting-started/nodejs/)
diff --git a/microsite/data/plugins/catalog-backend-module-gcp.yaml b/microsite/data/plugins/catalog-backend-module-gcp.yaml
new file mode 100644
index 0000000000..b5df858862
--- /dev/null
+++ b/microsite/data/plugins/catalog-backend-module-gcp.yaml
@@ -0,0 +1,16 @@
+---
+title: GCP Entity Providers
+author: BackToStage
+authorUrl: https://backtostage.app/?utm_source=backstage.io&utm_medium=marketplace&utm_campaign=catalog-backend-module-gcp
+category: Catalog
+description: Import your Infrastructure from GCP into Backstage as Resource Entities
+documentation: https://github.com/backtostage/backstage-plugins/blob/main/plugins/catalog-backend-module-gcp/README.md
+iconUrl: https://avatars1.githubusercontent.com/u/2810941?s=280&v=4
+npmPackageName: '@backtostage/plugin-catalog-backend-module-gcp'
+tags:
+ - cloud
+ - project
+ - resources
+ - gcp
+ - cloudsql
+addedDate: '2024-08-01'
diff --git a/microsite/data/plugins/kubernetes-gpt-analyzer.yaml b/microsite/data/plugins/kubernetes-gpt-analyzer.yaml
new file mode 100644
index 0000000000..78bd0fe4c4
--- /dev/null
+++ b/microsite/data/plugins/kubernetes-gpt-analyzer.yaml
@@ -0,0 +1,16 @@
+---
+title: VeeCode Kubernetes GPT Analyzer
+author: VeeCode Platform
+authorUrl: https://platform.vee.codes/
+category: Monitoring
+description: The Kubernetes GPT Analyzer plug-in uses artificial intelligence with the help of k8s-operator to analyze and optimize your Kubernetes entities, improving the management and performance of your cluster. It makes it easier to detect anomalies and suggest best practices.
+documentation: https://platform.vee.codes/plugin/Kubernetes%20GPT%20Analyzer/
+iconUrl: https://veecode-platform.github.io/support/imgs/logo_4.svg
+npmPackageName: '@veecode-platform/backstage-plugin-kubernetes-gpt-analyzer'
+tags:
+ - monitor
+ - ai
+ - kubernetes
+ - k8soperator
+ - gpt
+addedDate: '2024-07-31'
diff --git a/microsite/data/plugins/simple-icons.yaml b/microsite/data/plugins/simple-icons.yaml
new file mode 100644
index 0000000000..45722ab421
--- /dev/null
+++ b/microsite/data/plugins/simple-icons.yaml
@@ -0,0 +1,10 @@
+---
+title: Simple Icons
+author: dweber019
+authorUrl: https://github.com/dweber019
+category: Visualization
+description: The Simple Icons plugin will add additional icons to be used as link icons.
+documentation: https://github.com/dweber019/backstage-plugins/tree/main/plugins/simple-icons
+iconUrl: https://raw.githubusercontent.com/dweber019/backstage-plugins/main/plugins/simple-icons/docs/pluginIcon.png
+npmPackageName: '@dweber019/backstage-plugin-simple-icons'
+addedDate: '2024-07-30'
diff --git a/microsite/docusaurus.config.ts b/microsite/docusaurus.config.ts
index 67f6de4962..67018c6e33 100644
--- a/microsite/docusaurus.config.ts
+++ b/microsite/docusaurus.config.ts
@@ -241,7 +241,7 @@ const config: Config = {
position: 'left',
},
{
- to: 'docs/releases/v1.29.0',
+ to: 'docs/releases/v1.30.0',
label: 'Releases',
position: 'left',
},
diff --git a/microsite/sidebars.json b/microsite/sidebars.json
index a0c310ae47..92567c844d 100644
--- a/microsite/sidebars.json
+++ b/microsite/sidebars.json
@@ -1,6 +1,7 @@
{
"releases": {
"Release Notes": [
+ "releases/v1.30.0",
"releases/v1.29.0",
"releases/v1.28.0",
"releases/v1.27.0",
@@ -134,6 +135,7 @@
"features/search/concepts",
"features/search/architecture",
"features/search/search-engines",
+ "features/search/collators",
"features/search/how-to-guides"
]
},
@@ -297,6 +299,7 @@
"conf/writing",
"conf/defining"
],
+ "Notifications": ["notifications/index"],
"Auth and identity": [
"auth/index",
{
@@ -451,13 +454,15 @@
"items": [
"frontend-system/architecture/index",
"frontend-system/architecture/app",
- "frontend-system/architecture/extensions",
"frontend-system/architecture/plugins",
+ "frontend-system/architecture/extensions",
+ "frontend-system/architecture/extension-blueprints",
"frontend-system/architecture/extension-overrides",
+ "frontend-system/architecture/references",
"frontend-system/architecture/utility-apis",
"frontend-system/architecture/routes",
"frontend-system/architecture/naming-patterns",
- "frontend-system/architecture/references"
+ "frontend-system/architecture/migrations"
]
},
{
@@ -466,7 +471,7 @@
"items": [
"frontend-system/building-plugins/index",
"frontend-system/building-plugins/testing",
- "frontend-system/building-plugins/extension-types",
+ "frontend-system/building-plugins/common-extension-blueprints",
"frontend-system/building-plugins/built-in-data-refs",
"frontend-system/building-plugins/migrating"
]
diff --git a/mkdocs.yml b/mkdocs.yml
index 3b0c7d9caf..33c9af3286 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -71,6 +71,7 @@ nav:
- Concepts: 'features/search/concepts.md'
- Search Architecture: 'features/search/architecture.md'
- Search Engines: 'features/search/search-engines.md'
+ - Collators: 'features/search/collators.md'
- HOW TO guides: 'features/search/how-to-guides.md'
- TechDocs:
- Overview: 'features/techdocs/README.md'
diff --git a/package.json b/package.json
index 0e60de31e1..e99233dbf7 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
{
"name": "root",
- "version": "1.30.0-next.3",
+ "version": "1.30.0",
"private": true,
"repository": {
"type": "git",
diff --git a/packages/app-defaults/CHANGELOG.md b/packages/app-defaults/CHANGELOG.md
index 410841fec9..72c172e395 100644
--- a/packages/app-defaults/CHANGELOG.md
+++ b/packages/app-defaults/CHANGELOG.md
@@ -1,5 +1,16 @@
# @backstage/app-defaults
+## 1.5.10
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-app-api@1.14.2
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-permission-react@0.4.25
+
## 1.5.10-next.2
### Patch Changes
diff --git a/packages/app-defaults/package.json b/packages/app-defaults/package.json
index 284e832ae5..ee21affccf 100644
--- a/packages/app-defaults/package.json
+++ b/packages/app-defaults/package.json
@@ -1,6 +1,6 @@
{
"name": "@backstage/app-defaults",
- "version": "1.5.10-next.2",
+ "version": "1.5.10",
"description": "Provides the default wiring of a Backstage App",
"backstage": {
"role": "web-library"
diff --git a/packages/app-next-example-plugin/CHANGELOG.md b/packages/app-next-example-plugin/CHANGELOG.md
index 62a7b18df0..af5b4a5c24 100644
--- a/packages/app-next-example-plugin/CHANGELOG.md
+++ b/packages/app-next-example-plugin/CHANGELOG.md
@@ -1,5 +1,21 @@
# app-next-example-plugin
+## 0.0.14
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/core-components@0.14.10
+
+## 0.0.14-next.3
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/core-components@0.14.10-next.0
+
## 0.0.14-next.2
### Patch Changes
diff --git a/packages/app-next-example-plugin/api-report.md b/packages/app-next-example-plugin/api-report.md
index c89a7b599b..4698edec6b 100644
--- a/packages/app-next-example-plugin/api-report.md
+++ b/packages/app-next-example-plugin/api-report.md
@@ -3,11 +3,47 @@
> Do not edit this file. It is a report generated by [API Extractor](https://api-extractor.com/).
```ts
+import { AnyRouteRefParams } from '@backstage/frontend-plugin-api';
import { BackstagePlugin } from '@backstage/frontend-plugin-api';
+import { ConfigurableExtensionDataRef } from '@backstage/frontend-plugin-api';
+import { ExtensionDefinition } from '@backstage/frontend-plugin-api';
import { default as React_2 } from 'react';
+import { RouteRef } from '@backstage/frontend-plugin-api';
// @public (undocumented)
-const examplePlugin: BackstagePlugin<{}, {}>;
+const examplePlugin: BackstagePlugin<
+ {},
+ {},
+ {
+ 'page:example': ExtensionDefinition<
+ {
+ path: string | undefined;
+ },
+ {
+ path?: string | undefined;
+ },
+ | ConfigurableExtensionDataRef<
+ React_2.JSX.Element,
+ 'core.reactElement',
+ {}
+ >
+ | ConfigurableExtensionDataRef
+ | ConfigurableExtensionDataRef<
+ RouteRef,
+ 'core.routing.ref',
+ {
+ optional: true;
+ }
+ >,
+ {},
+ {
+ kind: 'page';
+ namespace: undefined;
+ name: undefined;
+ }
+ >;
+ }
+>;
export default examplePlugin;
// @public (undocumented)
diff --git a/packages/app-next-example-plugin/package.json b/packages/app-next-example-plugin/package.json
index ad179ebbe5..5bb8318e2b 100644
--- a/packages/app-next-example-plugin/package.json
+++ b/packages/app-next-example-plugin/package.json
@@ -1,6 +1,6 @@
{
"name": "app-next-example-plugin",
- "version": "0.0.14-next.2",
+ "version": "0.0.14",
"description": "Backstage internal example plugin",
"backstage": {
"role": "frontend-plugin",
diff --git a/packages/app-next-example-plugin/src/plugin.tsx b/packages/app-next-example-plugin/src/plugin.tsx
index 99c377b7e5..818e8abc84 100644
--- a/packages/app-next-example-plugin/src/plugin.tsx
+++ b/packages/app-next-example-plugin/src/plugin.tsx
@@ -16,17 +16,19 @@
import React from 'react';
import {
- createPageExtension,
- createPlugin,
+ PageBlueprint,
+ createFrontendPlugin,
} from '@backstage/frontend-plugin-api';
-export const ExamplePage = createPageExtension({
- defaultPath: '/example',
- loader: () => import('./Component').then(m => ),
+export const ExamplePage = PageBlueprint.make({
+ params: {
+ defaultPath: '/example',
+ loader: () => import('./Component').then(m => ),
+ },
});
/** @public */
-export const examplePlugin = createPlugin({
+export const examplePlugin = createFrontendPlugin({
id: 'example',
extensions: [ExamplePage],
});
diff --git a/packages/app-next/CHANGELOG.md b/packages/app-next/CHANGELOG.md
index 6382efa811..5d3a1d5a3c 100644
--- a/packages/app-next/CHANGELOG.md
+++ b/packages/app-next/CHANGELOG.md
@@ -1,5 +1,91 @@
# example-app-next
+## 0.0.14
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-catalog@1.22.0
+ - @backstage/plugin-scaffolder@1.24.0
+ - @backstage/frontend-plugin-api@0.7.0
+ - @backstage/plugin-scaffolder-react@1.11.0
+ - @backstage/cli@0.27.0
+ - @backstage/plugin-notifications@0.3.0
+ - @backstage/plugin-catalog-react@1.12.3
+ - @backstage/plugin-search-react@1.7.14
+ - @backstage/plugin-home@0.7.9
+ - @backstage/plugin-techdocs@1.10.8
+ - @backstage/core-components@0.14.10
+ - @backstage/plugin-api-docs@0.11.8
+ - @backstage/frontend-app-api@0.8.0
+ - @backstage/core-compat-api@0.2.8
+ - @backstage/plugin-app-visualizer@0.1.9
+ - @backstage/plugin-catalog-graph@0.4.8
+ - @backstage/plugin-catalog-import@0.12.2
+ - @backstage/plugin-org@0.6.28
+ - @backstage/plugin-search@1.4.15
+ - @backstage/plugin-user-settings@0.8.11
+ - @backstage/plugin-search-common@1.2.14
+ - @backstage/plugin-kubernetes@0.11.13
+ - @backstage/core-app-api@1.14.2
+ - @backstage/plugin-auth-react@0.1.5
+ - @backstage/catalog-model@1.6.0
+ - @backstage/app-defaults@1.5.10
+ - @backstage/config@1.2.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-catalog-common@1.0.26
+ - @backstage/plugin-catalog-unprocessed-entities@0.2.7
+ - @backstage/plugin-kubernetes-cluster@0.0.14
+ - @backstage/plugin-permission-react@0.4.25
+ - @backstage/plugin-signals@0.0.9
+ - @backstage/plugin-techdocs-module-addons-contrib@1.1.13
+ - @backstage/plugin-techdocs-react@1.2.7
+
+## 0.0.14-next.4
+
+### Patch Changes
+
+- Updated dependencies
+ - @backstage/plugin-scaffolder@1.24.0-next.3
+ - @backstage/frontend-plugin-api@0.7.0-next.3
+ - @backstage/plugin-notifications@0.3.0-next.1
+ - @backstage/cli@0.27.0-next.4
+ - @backstage/plugin-techdocs@1.10.8-next.3
+ - @backstage/plugin-api-docs@0.11.8-next.3
+ - @backstage/plugin-catalog@1.22.0-next.3
+ - @backstage/catalog-model@1.6.0-next.0
+ - @backstage/core-compat-api@0.2.8-next.3
+ - @backstage/frontend-app-api@0.7.5-next.3
+ - @backstage/plugin-app-visualizer@0.1.9-next.3
+ - @backstage/plugin-catalog-graph@0.4.8-next.4
+ - @backstage/plugin-catalog-import@0.12.2-next.3
+ - @backstage/plugin-catalog-react@1.12.3-next.3
+ - @backstage/plugin-home@0.7.9-next.3
+ - @backstage/plugin-kubernetes@0.11.13-next.3
+ - @backstage/plugin-org@0.6.28-next.3
+ - @backstage/plugin-search@1.4.15-next.3
+ - @backstage/plugin-search-react@1.7.14-next.3
+ - @backstage/plugin-user-settings@0.8.11-next.3
+ - @backstage/app-defaults@1.5.10-next.2
+ - @backstage/config@1.2.0
+ - @backstage/core-app-api@1.14.2-next.0
+ - @backstage/core-components@0.14.10-next.0
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/integration-react@1.1.30-next.0
+ - @backstage/theme@0.5.6
+ - @backstage/plugin-auth-react@0.1.5-next.0
+ - @backstage/plugin-catalog-common@1.0.26-next.2
+ - @backstage/plugin-catalog-unprocessed-entities@0.2.7-next.1
+ - @backstage/plugin-kubernetes-cluster@0.0.14-next.3
+ - @backstage/plugin-permission-react@0.4.25-next.1
+ - @backstage/plugin-scaffolder-react@1.11.0-next.3
+ - @backstage/plugin-search-common@1.2.14-next.1
+ - @backstage/plugin-signals@0.0.9-next.0
+ - @backstage/plugin-techdocs-module-addons-contrib@1.1.13-next.1
+ - @backstage/plugin-techdocs-react@1.2.7-next.1
+
## 0.0.14-next.3
### Patch Changes
diff --git a/packages/app-next/package.json b/packages/app-next/package.json
index a12371a135..fa37cce5c8 100644
--- a/packages/app-next/package.json
+++ b/packages/app-next/package.json
@@ -1,6 +1,6 @@
{
"name": "example-app-next",
- "version": "0.0.14-next.3",
+ "version": "0.0.14",
"private": true,
"repository": {
"type": "git",
diff --git a/packages/app-next/src/App.tsx b/packages/app-next/src/App.tsx
index b57c680474..170decee42 100644
--- a/packages/app-next/src/App.tsx
+++ b/packages/app-next/src/App.tsx
@@ -26,10 +26,15 @@ import homePlugin, {
import {
coreExtensionData,
createExtension,
- createApiExtension,
createExtensionOverrides,
+ ApiBlueprint,
} from '@backstage/frontend-plugin-api';
-import techdocsPlugin from '@backstage/plugin-techdocs/alpha';
+import {
+ techdocsPlugin,
+ TechDocsIndexPage,
+ TechDocsReaderPage,
+ EntityTechdocsContent,
+} from '@backstage/plugin-techdocs';
import appVisualizerPlugin from '@backstage/plugin-app-visualizer';
import { homePage } from './HomePage';
import { convertLegacyApp } from '@backstage/core-compat-api';
@@ -40,10 +45,14 @@ import { createApiFactory, configApiRef } from '@backstage/core-plugin-api';
import {
ScmAuth,
ScmIntegrationsApi,
+ scmAuthApiRef,
scmIntegrationsApiRef,
} from '@backstage/integration-react';
import kubernetesPlugin from '@backstage/plugin-kubernetes/alpha';
import { signInPageOverrides } from './overrides/SignInPage';
+import { convertLegacyPlugin } from '@backstage/core-compat-api';
+import { convertLegacyPageExtension } from '@backstage/core-compat-api';
+import { convertLegacyEntityContentExtension } from '@backstage/plugin-catalog-react/alpha';
/*
@@ -74,28 +83,45 @@ TODO:
/* app.tsx */
+const convertedTechdocsPlugin = convertLegacyPlugin(techdocsPlugin, {
+ extensions: [
+ // TODO: We likely also need a way to convert an entire tree similar to collectLegacyRoutes
+ convertLegacyPageExtension(TechDocsIndexPage),
+ convertLegacyPageExtension(TechDocsReaderPage, {
+ defaultPath: '/docs/:namespace/:kind/:name/*',
+ }),
+ convertLegacyEntityContentExtension(EntityTechdocsContent),
+ ],
+});
+
const homePageExtension = createExtension({
name: 'myhomepage',
attachTo: { id: 'page:home', input: 'props' },
- output: {
- children: coreExtensionData.reactElement,
- title: titleExtensionDataRef,
- },
+ output: [coreExtensionData.reactElement, titleExtensionDataRef],
factory() {
- return { children: homePage, title: 'just a title' };
+ return [
+ coreExtensionData.reactElement(homePage),
+ titleExtensionDataRef('just a title'),
+ ];
},
});
-const scmAuthExtension = createApiExtension({
- factory: ScmAuth.createDefaultApiFactory(),
+const scmAuthExtension = ApiBlueprint.make({
+ namespace: scmAuthApiRef.id,
+ params: {
+ factory: ScmAuth.createDefaultApiFactory(),
+ },
});
-const scmIntegrationApi = createApiExtension({
- factory: createApiFactory({
- api: scmIntegrationsApiRef,
- deps: { configApi: configApiRef },
- factory: ({ configApi }) => ScmIntegrationsApi.fromConfig(configApi),
- }),
+const scmIntegrationApi = ApiBlueprint.make({
+ namespace: scmIntegrationsApiRef.id,
+ params: {
+ factory: createApiFactory({
+ api: scmIntegrationsApiRef,
+ deps: { configApi: configApiRef },
+ factory: ({ configApi }) => ScmIntegrationsApi.fromConfig(configApi),
+ }),
+ },
});
const collectedLegacyPlugins = convertLegacyApp(
@@ -107,7 +133,7 @@ const collectedLegacyPlugins = convertLegacyApp(
const app = createApp({
features: [
pagesPlugin,
- techdocsPlugin,
+ convertedTechdocsPlugin,
userSettingsPlugin,
homePlugin,
appVisualizerPlugin,
diff --git a/packages/app-next/src/examples/pagesPlugin.tsx b/packages/app-next/src/examples/pagesPlugin.tsx
index 095c992e18..8eca7d1e6c 100644
--- a/packages/app-next/src/examples/pagesPlugin.tsx
+++ b/packages/app-next/src/examples/pagesPlugin.tsx
@@ -17,11 +17,11 @@
import React from 'react';
import { Link } from '@backstage/core-components';
import {
- createPageExtension,
- createPlugin,
+ createFrontendPlugin,
createRouteRef,
createExternalRouteRef,
useRouteRef,
+ PageBlueprint,
} from '@backstage/frontend-plugin-api';
import { Route, Routes } from 'react-router-dom';
@@ -37,95 +37,101 @@ export const pageXRouteRef = createRouteRef();
// path: '/page2',
// });
-const IndexPage = createPageExtension({
+const IndexPage = PageBlueprint.make({
name: 'index',
- defaultPath: '/',
- routeRef: indexRouteRef,
- loader: async () => {
- const Component = () => {
- const page1Link = useRouteRef(page1RouteRef);
- return (
-
;
+ };
+ return ;
+ },
},
}),
],
@@ -250,7 +263,7 @@ describe('createApp', () => {
content [
routes [
-
+
]
]
diff --git a/packages/frontend-app-api/src/wiring/createApp.tsx b/packages/frontend-app-api/src/wiring/createApp.tsx
index d82d0ca782..ca42dce3e4 100644
--- a/packages/frontend-app-api/src/wiring/createApp.tsx
+++ b/packages/frontend-app-api/src/wiring/createApp.tsx
@@ -17,18 +17,18 @@
import React, { JSX, ReactNode } from 'react';
import { ConfigReader } from '@backstage/config';
import {
+ ApiBlueprint,
AppTree,
appTreeApiRef,
componentsApiRef,
coreExtensionData,
- createApiExtension,
- createThemeExtension,
- createTranslationExtension,
FrontendFeature,
IconBundleBlueprint,
iconsApiRef,
RouteResolutionApi,
routeResolutionApiRef,
+ ThemeBlueprint,
+ TranslationBlueprint,
} from '@backstage/frontend-plugin-api';
import { App } from '../extensions/App';
import { AppRoutes } from '../extensions/AppRoutes';
@@ -100,7 +100,7 @@ import {
import { InternalAppContext } from './InternalAppContext';
import { AppRoot } from '../extensions/AppRoot';
// eslint-disable-next-line @backstage/no-relative-monorepo-imports
-import { toInternalBackstagePlugin } from '../../../frontend-plugin-api/src/wiring/createPlugin';
+import { toInternalBackstagePlugin } from '../../../frontend-plugin-api/src/wiring/createFrontendPlugin';
// eslint-disable-next-line @backstage/no-relative-monorepo-imports
import { toInternalExtensionOverrides } from '../../../frontend-plugin-api/src/wiring/createExtensionOverrides';
import { DefaultComponentsApi } from '../apis/implementations/ComponentsApi';
@@ -110,7 +110,9 @@ import { stringifyError } from '@backstage/errors';
import { icons as defaultIcons } from '../../../app-defaults/src/defaults';
import { getBasePath } from '../routing/getBasePath';
-const DefaultApis = defaultApis.map(factory => createApiExtension({ factory }));
+const DefaultApis = defaultApis.map(factory =>
+ ApiBlueprint.make({ namespace: factory.api.id, params: { factory } }),
+);
export const builtinExtensions = [
App,
@@ -357,23 +359,21 @@ function createApiHolder(
const pluginApis =
tree.root.edges.attachments
.get('apis')
- ?.map(e => e.instance?.getData(createApiExtension.factoryDataRef))
+ ?.map(e => e.instance?.getData(ApiBlueprint.dataRefs.factory))
.filter((x): x is AnyApiFactory => !!x) ?? [];
const themeExtensions =
tree.root.edges.attachments
.get('themes')
- ?.map(e => e.instance?.getData(createThemeExtension.themeDataRef))
+ ?.map(e => e.instance?.getData(ThemeBlueprint.dataRefs.theme))
.filter((x): x is AppTheme => !!x) ?? [];
const translationResources =
tree.root.edges.attachments
.get('translations')
- ?.map(e =>
- e.instance?.getData(createTranslationExtension.translationDataRef),
- )
+ ?.map(e => e.instance?.getData(TranslationBlueprint.dataRefs.translation))
.filter(
- (x): x is typeof createTranslationExtension.translationDataRef.T => !!x,
+ (x): x is typeof TranslationBlueprint.dataRefs.translation.T => !!x,
) ?? [];
const extensionIcons = tree.root.edges.attachments
diff --git a/packages/frontend-app-api/src/wiring/discovery.test.ts b/packages/frontend-app-api/src/wiring/discovery.test.ts
index 6008ce6746..8570ca1bc7 100644
--- a/packages/frontend-app-api/src/wiring/discovery.test.ts
+++ b/packages/frontend-app-api/src/wiring/discovery.test.ts
@@ -14,7 +14,7 @@
* limitations under the License.
*/
-import { createPlugin } from '@backstage/frontend-plugin-api';
+import { createFrontendPlugin } from '@backstage/frontend-plugin-api';
import { getAvailableFeatures } from './discovery';
import { ConfigReader } from '@backstage/config';
@@ -42,7 +42,7 @@ describe('getAvailableFeatures', () => {
});
it('should discover a plugin', () => {
- const testPlugin = createPlugin({ id: 'test' });
+ const testPlugin = createFrontendPlugin({ id: 'test' });
globalSpy.mockReturnValue({
modules: [{ default: testPlugin }],
});
@@ -67,9 +67,9 @@ describe('getAvailableFeatures', () => {
});
it('should discover multiple plugins', () => {
- const test1Plugin = createPlugin({ id: 'test1' });
- const test2Plugin = createPlugin({ id: 'test2' });
- const test3Plugin = createPlugin({ id: 'test3' });
+ const test1Plugin = createFrontendPlugin({ id: 'test1' });
+ const test2Plugin = createFrontendPlugin({ id: 'test2' });
+ const test3Plugin = createFrontendPlugin({ id: 'test3' });
globalSpy.mockReturnValue({
modules: [
{ default: test1Plugin },
diff --git a/packages/frontend-plugin-api/CHANGELOG.md b/packages/frontend-plugin-api/CHANGELOG.md
index 302d541b18..cce56f0855 100644
--- a/packages/frontend-plugin-api/CHANGELOG.md
+++ b/packages/frontend-plugin-api/CHANGELOG.md
@@ -1,5 +1,249 @@
# @backstage/frontend-plugin-api
+## 0.7.0
+
+### Minor Changes
+
+- 72754db: **BREAKING**: All types of route refs are always considered optional by `useRouteRef`, which means the caller must always handle a potential `undefined` return value. Related to this change, the `optional` option from `createExternalRouteRef` has been removed, since it is no longer necessary.
+
+ This is released as an immediate breaking change as we expect the usage of the new route refs to be extremely low or zero, since plugins that support the new system will still use route refs and `useRouteRef` from `@backstage/core-plugin-api` in combination with `convertLegacyRouteRef` from `@backstage/core-compat-api`.
+
+### Patch Changes
+
+- 6f72c2b: Fixing issue with extension blueprints `inputs` merging.
+- 210d066: Added support for using the `params` in other properties of the `createExtensionBlueprint` options by providing a callback.
+- 9b356dc: Renamed `createPlugin` to `createFrontendPlugin`. The old symbol is still exported but deprecated.
+- a376559: Correct the `TConfig` type of data references to only contain config
+- 4e53ad6: Introduce a new way to encapsulate extension kinds that replaces the extension creator pattern with `createExtensionBlueprint`
+
+ This allows the creation of extension instances with the following pattern:
+
+ ```tsx
+ // create the extension blueprint which is used to create instances
+ const EntityCardBlueprint = createExtensionBlueprint({
+ kind: 'entity-card',
+ attachTo: { id: 'test', input: 'default' },
+ output: [coreExtensionData.reactElement],
+ factory(params: { text: string }) {
+ return [coreExtensionData.reactElement(
{params.text}
)];
+ },
+ });
+
+ // create an instance of the extension blueprint with params
+ const testExtension = EntityCardBlueprint.make({
+ name: 'foo',
+ params: {
+ text: 'Hello World',
+ },
+ });
+ ```
+
+- 9b89b82: The `ExtensionBoundary` now by default infers whether it's routable from whether it outputs a route path.
+- e493020: Deprecated `inputs` and `configSchema` options for `createComponentExtenion`, these will be removed in a future release
+- 7777b5f: Added a new `IconBundleBlueprint` that lets you create icon bundle extensions that can be installed in an App in order to override or add new app icons.
+
+ ```tsx
+ import { IconBundleBlueprint } from '@backstage/frontend-plugin-api';
+
+ const exampleIconBundle = IconBundleBlueprint.make({
+ name: 'example-bundle',
+ params: {
+ icons: {
+ user: MyOwnUserIcon,
+ },
+ },
+ });
+ ```
+
+- 99abb6b: Support overriding of plugin extensions using the new `plugin.withOverrides` method.
+
+ ```tsx
+ import homePlugin from '@backstage/plugin-home';
+
+ export default homePlugin.withOverrides({
+ extensions: [
+ homePage.getExtension('page:home').override({
+ *factory(originalFactory) {
+ yield* originalFactory();
+ yield coreExtensionData.reactElement(
My custom home page
);
+ },
+ }),
+ ],
+ });
+ ```
+
+- 813cac4: Add an `ExtensionBoundary.lazy` function to create properly wrapped lazy-loading enabled elements, suitable for use with `coreExtensionData.reactElement`. The page blueprint now automatically leverages this.
+- a65cfc8: Add support for accessing extensions definitions provided by a plugin via `plugin.getExtension(...)`. For this to work the extensions must be defined using the v2 format, typically using an extension blueprint.
+- 3be9aeb: Extensions have been changed to be declared with an array of inputs and outputs, rather than a map of named data refs. This change was made to reduce confusion around the role of the input and output names, as well as enable more powerful APIs for overriding extensions.
+
+ An extension that was previously declared like this:
+
+ ```tsx
+ const exampleExtension = createExtension({
+ name: 'example',
+ inputs: {
+ items: createExtensionInput({
+ element: coreExtensionData.reactElement,
+ }),
+ },
+ output: {
+ element: coreExtensionData.reactElement,
+ },
+ factory({ inputs }) {
+ return {
+ element: (
+
,
+ ),
+ ];
+ },
+ });
+ ```
+
+- 34f1b2a: Support merging of `inputs` in extension blueprints, but stop merging `output`. In addition, the original factory in extension blueprints now returns a data container that both provides access to the returned data, but can also be forwarded as output.
+- 3fb421d: Added support to be able to define `zod` config schema in Blueprints, with built in schema merging from the Blueprint and the extension instances.
+- 2d21599: Added support for being able to override extension definitions.
+
+ ```tsx
+ const TestCard = EntityCardBlueprint.make({
+ ...
+ });
+
+ TestCard.override({
+ // override attachment points
+ attachTo: { id: 'something-else', input: 'overridden' },
+ // extend the config schema
+ config: {
+ schema: {
+ newConfig: z => z.string().optional(),
+ }
+ },
+ // override factory
+ *factory(originalFactory, { inputs, config }){
+ const originalOutput = originalFactory();
+
+ yield coreExentsionData.reactElement(
+
+ {originalOutput.get(coreExentsionData.reactElement)}
+
+ );
+ }
+ });
+
+ ```
+
+- 31bfc44: Extension data references can now be defined in a way that encapsulates the ID string in the type, in addition to the data type itself. The old way of creating extension data references is deprecated and will be removed in a future release.
+
+ For example, the following code:
+
+ ```ts
+ export const myExtension =
+ createExtensionDataRef('my-plugin.my-data');
+ ```
+
+ Should be updated to the following:
+
+ ```ts
+ export const myExtension = createExtensionDataRef().with({
+ id: 'my-plugin.my-data',
+ });
+ ```
+
+- 6349099: Added config input type to the extensions
+- Updated dependencies
+ - @backstage/core-components@0.14.10
+ - @backstage/core-plugin-api@1.9.3
+ - @backstage/types@1.1.1
+ - @backstage/version-bridge@1.0.8
+
+## 0.7.0-next.3
+
+### Patch Changes
+
+- 6f72c2b: Fixing issue with extension blueprints `inputs` merging.
+- 99abb6b: Support overriding of plugin extensions using the new `plugin.withOverrides` method.
+
+ ```tsx
+ import homePlugin from '@backstage/plugin-home';
+
+ export default homePlugin.withOverrides({
+ extensions: [
+ homePage.getExtension('page:home').override({
+ *factory(originalFactory) {
+ yield* originalFactory();
+ yield coreExtensionData.reactElement(
)],
+ }),
+ )
+ .render();
+
+ await waitFor(() => {
+ expect(getByText('Hi')).toBeInTheDocument();
+ expect(getByTestId('Robin-1')).toBeInTheDocument();
+ expect(getByText('Its Me')).toBeInTheDocument();
+ });
+ });
+});
diff --git a/packages/frontend-plugin-api/src/blueprints/AppRootWrapperBlueprint.tsx b/packages/frontend-plugin-api/src/blueprints/AppRootWrapperBlueprint.tsx
new file mode 100644
index 0000000000..da11bd8cb0
--- /dev/null
+++ b/packages/frontend-plugin-api/src/blueprints/AppRootWrapperBlueprint.tsx
@@ -0,0 +1,47 @@
+/*
+ * Copyright 2024 The Backstage Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import React from 'react';
+import { ComponentType, PropsWithChildren } from 'react';
+import { createExtensionBlueprint, createExtensionDataRef } from '../wiring';
+
+const componentDataRef = createExtensionDataRef<
+ ComponentType>
+>().with({ id: 'app.root.wrapper' });
+
+/**
+ * Creates a extensions that render a React wrapper at the app root, enclosing
+ * the app layout. This is useful for example for adding global React contexts
+ * and similar.
+ *
+ * @public
+ */
+export const AppRootWrapperBlueprint = createExtensionBlueprint({
+ kind: 'app-root-wrapper',
+ attachTo: { id: 'app/root', input: 'wrappers' },
+ output: [componentDataRef],
+ dataRefs: {
+ component: componentDataRef,
+ },
+ *factory(params: { Component: ComponentType> }) {
+ // todo(blam): not sure that this wrapping is even necessary anymore.
+ const Component = (props: PropsWithChildren<{}>) => {
+ return {props.children};
+ };
+
+ yield componentDataRef(Component);
+ },
+});
diff --git a/packages/frontend-plugin-api/src/extensions/IconBundleBlueprint.ts b/packages/frontend-plugin-api/src/blueprints/IconBundleBlueprint.ts
similarity index 99%
rename from packages/frontend-plugin-api/src/extensions/IconBundleBlueprint.ts
rename to packages/frontend-plugin-api/src/blueprints/IconBundleBlueprint.ts
index deeabdb44c..52d6e2482d 100644
--- a/packages/frontend-plugin-api/src/extensions/IconBundleBlueprint.ts
+++ b/packages/frontend-plugin-api/src/blueprints/IconBundleBlueprint.ts
@@ -13,6 +13,7 @@
* See the License for the specific language governing permissions and
* limitations under the License.
*/
+
import { IconComponent } from '../icons';
import { createExtensionBlueprint, createExtensionDataRef } from '../wiring';
diff --git a/packages/frontend-plugin-api/src/blueprints/NavItemBlueprint.test.tsx b/packages/frontend-plugin-api/src/blueprints/NavItemBlueprint.test.tsx
new file mode 100644
index 0000000000..daa21f88bb
--- /dev/null
+++ b/packages/frontend-plugin-api/src/blueprints/NavItemBlueprint.test.tsx
@@ -0,0 +1,106 @@
+/*
+ * Copyright 2024 The Backstage Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+import { createExtensionTester } from '@backstage/frontend-test-utils';
+import { createRouteRef } from '../routing';
+import { NavItemBlueprint } from './NavItemBlueprint';
+
+describe('NavItemBlueprint', () => {
+ const mockRouteRef = createRouteRef();
+ const MockIcon = () => null;
+
+ it('should return an extension with sensible defaults', () => {
+ const extension = NavItemBlueprint.make({
+ params: {
+ icon: MockIcon,
+ routeRef: mockRouteRef,
+ title: 'TEST',
+ },
+ });
+
+ expect(extension).toMatchInlineSnapshot(`
+ {
+ "$$type": "@backstage/ExtensionDefinition",
+ "attachTo": {
+ "id": "app/nav",
+ "input": "items",
+ },
+ "configSchema": {
+ "parse": [Function],
+ "schema": {
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "title": {
+ "type": "string",
+ },
+ },
+ "type": "object",
+ },
+ },
+ "disabled": false,
+ "factory": [Function],
+ "inputs": {},
+ "kind": "nav-item",
+ "name": undefined,
+ "namespace": undefined,
+ "output": [
+ [Function],
+ ],
+ "override": [Function],
+ "toString": [Function],
+ "version": "v2",
+ }
+ `);
+ });
+
+ it('should return the correct extension data', () => {
+ const extension = NavItemBlueprint.make({
+ params: {
+ icon: MockIcon,
+ routeRef: mockRouteRef,
+ title: 'TEST',
+ },
+ });
+
+ const tester = createExtensionTester(extension);
+
+ expect(tester.get(NavItemBlueprint.dataRefs.target)).toEqual({
+ title: 'TEST',
+ icon: MockIcon,
+ routeRef: mockRouteRef,
+ });
+ });
+
+ it('should allow overriding of the title using config', () => {
+ const extension = NavItemBlueprint.make({
+ params: {
+ icon: MockIcon,
+ routeRef: mockRouteRef,
+ title: 'TEST',
+ },
+ });
+
+ const tester = createExtensionTester(extension, {
+ config: { title: 'OVERRIDDEN' },
+ });
+
+ expect(tester.get(NavItemBlueprint.dataRefs.target)).toEqual({
+ title: 'OVERRIDDEN',
+ icon: MockIcon,
+ routeRef: mockRouteRef,
+ });
+ });
+});
diff --git a/packages/frontend-plugin-api/src/blueprints/NavItemBlueprint.ts b/packages/frontend-plugin-api/src/blueprints/NavItemBlueprint.ts
new file mode 100644
index 0000000000..197f72da73
--- /dev/null
+++ b/packages/frontend-plugin-api/src/blueprints/NavItemBlueprint.ts
@@ -0,0 +1,63 @@
+/*
+ * Copyright 2024 The Backstage Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import { IconComponent } from '@backstage/core-plugin-api';
+import { RouteRef } from '../routing';
+import { createExtensionBlueprint, createExtensionDataRef } from '../wiring';
+
+// TODO(Rugvip): Should this be broken apart into separate refs? title/icon/routeRef
+const targetDataRef = createExtensionDataRef<{
+ title: string;
+ icon: IconComponent;
+ routeRef: RouteRef;
+}>().with({ id: 'core.nav-item.target' });
+
+/**
+ * Creates extensions that make up the items of the nav bar.
+ *
+ * @public
+ */
+export const NavItemBlueprint = createExtensionBlueprint({
+ kind: 'nav-item',
+ attachTo: { id: 'app/nav', input: 'items' },
+ output: [targetDataRef],
+ dataRefs: {
+ target: targetDataRef,
+ },
+ factory: (
+ {
+ icon,
+ routeRef,
+ title,
+ }: {
+ title: string;
+ icon: IconComponent;
+ routeRef: RouteRef;
+ },
+ { config },
+ ) => [
+ targetDataRef({
+ title: config.title ?? title,
+ icon,
+ routeRef,
+ }),
+ ],
+ config: {
+ schema: {
+ title: z => z.string().optional(),
+ },
+ },
+});
diff --git a/packages/frontend-plugin-api/src/blueprints/NavLogoBlueprint.test.tsx b/packages/frontend-plugin-api/src/blueprints/NavLogoBlueprint.test.tsx
new file mode 100644
index 0000000000..621dca72ba
--- /dev/null
+++ b/packages/frontend-plugin-api/src/blueprints/NavLogoBlueprint.test.tsx
@@ -0,0 +1,73 @@
+/*
+ * Copyright 2024 The Backstage Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import React from 'react';
+import { NavLogoBlueprint } from './NavLogoBlueprint';
+import { createExtensionTester } from '@backstage/frontend-test-utils';
+
+describe('NavLogoBlueprint', () => {
+ it('should create an extension with sensible defaults', () => {
+ const extension = NavLogoBlueprint.make({
+ params: {
+ logoFull:
;
+
+ const extension = NavLogoBlueprint.make({
+ name: 'test',
+ params: {
+ logoFull,
+ logoIcon,
+ },
+ });
+
+ const tester = createExtensionTester(extension);
+
+ expect(tester.get(NavLogoBlueprint.dataRefs.logoElements)).toEqual({
+ logoFull,
+ logoIcon,
+ });
+ });
+});
diff --git a/packages/frontend-plugin-api/src/blueprints/NavLogoBlueprint.ts b/packages/frontend-plugin-api/src/blueprints/NavLogoBlueprint.ts
new file mode 100644
index 0000000000..4a37859975
--- /dev/null
+++ b/packages/frontend-plugin-api/src/blueprints/NavLogoBlueprint.ts
@@ -0,0 +1,48 @@
+/*
+ * Copyright 2024 The Backstage Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import { createExtensionBlueprint, createExtensionDataRef } from '../wiring';
+
+const logoElementsDataRef = createExtensionDataRef<{
+ logoIcon?: JSX.Element;
+ logoFull?: JSX.Element;
+}>().with({ id: 'core.nav-logo.logo-elements' });
+
+/**
+ * Creates an extension that replaces the logo in the nav bar with your own.
+ *
+ * @public
+ */
+export const NavLogoBlueprint = createExtensionBlueprint({
+ kind: 'nav-logo',
+ attachTo: { id: 'app/nav', input: 'logos' },
+ output: [logoElementsDataRef],
+ dataRefs: {
+ logoElements: logoElementsDataRef,
+ },
+ *factory({
+ logoIcon,
+ logoFull,
+ }: {
+ logoIcon: JSX.Element;
+ logoFull: JSX.Element;
+ }) {
+ yield logoElementsDataRef({
+ logoIcon,
+ logoFull,
+ });
+ },
+});
diff --git a/packages/frontend-plugin-api/src/blueprints/PageBlueprint.test.tsx b/packages/frontend-plugin-api/src/blueprints/PageBlueprint.test.tsx
new file mode 100644
index 0000000000..dedc5454bd
--- /dev/null
+++ b/packages/frontend-plugin-api/src/blueprints/PageBlueprint.test.tsx
@@ -0,0 +1,157 @@
+/*
+ * Copyright 2024 The Backstage Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+import React from 'react';
+import { createRouteRef } from '../routing';
+import { PageBlueprint } from './PageBlueprint';
+import {
+ createExtensionTester,
+ renderInTestApp,
+} from '@backstage/frontend-test-utils';
+import {
+ coreExtensionData,
+ createExtensionBlueprint,
+ createExtensionInput,
+} from '../wiring';
+import { waitFor } from '@testing-library/react';
+
+describe('PageBlueprint', () => {
+ const mockRouteRef = createRouteRef();
+
+ it('should return an extension when calling make with sensible defaults', () => {
+ const myPage = PageBlueprint.make({
+ name: 'test-page',
+ params: {
+ loader: () => Promise.resolve(
,
+ ),
+ ];
+ },
+ });
+
+ const tester = createExtensionTester(myPage).add(
+ CardBlueprint.make({ name: 'card', params: {} }),
+ );
+
+ const { getByTestId, getByText } = renderInTestApp(tester.reactElement());
+
+ await waitFor(() => expect(getByTestId('card')).toBeInTheDocument());
+ await waitFor(() =>
+ expect(getByText("I'm a lovely card")).toBeInTheDocument(),
+ );
+ });
+});
diff --git a/packages/frontend-plugin-api/src/blueprints/PageBlueprint.tsx b/packages/frontend-plugin-api/src/blueprints/PageBlueprint.tsx
new file mode 100644
index 0000000000..303e99daaa
--- /dev/null
+++ b/packages/frontend-plugin-api/src/blueprints/PageBlueprint.tsx
@@ -0,0 +1,57 @@
+/*
+ * Copyright 2024 The Backstage Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import { RouteRef } from '../routing';
+import { coreExtensionData, createExtensionBlueprint } from '../wiring';
+import { ExtensionBoundary } from '../components';
+
+/**
+ * Createx extensions that are routable React page components.
+ *
+ * @public
+ */
+export const PageBlueprint = createExtensionBlueprint({
+ kind: 'page',
+ attachTo: { id: 'app/routes', input: 'routes' },
+ output: [
+ coreExtensionData.routePath,
+ coreExtensionData.reactElement,
+ coreExtensionData.routeRef.optional(),
+ ],
+ config: {
+ schema: {
+ path: z => z.string().optional(),
+ },
+ },
+ *factory(
+ {
+ defaultPath,
+ loader,
+ routeRef,
+ }: {
+ defaultPath: string;
+ loader: () => Promise;
+ routeRef?: RouteRef;
+ },
+ { config, node },
+ ) {
+ yield coreExtensionData.routePath(config.path ?? defaultPath);
+ yield coreExtensionData.reactElement(ExtensionBoundary.lazy(node, loader));
+ if (routeRef) {
+ yield coreExtensionData.routeRef(routeRef);
+ }
+ },
+});
diff --git a/packages/frontend-plugin-api/src/blueprints/RouterBlueprint.test.tsx b/packages/frontend-plugin-api/src/blueprints/RouterBlueprint.test.tsx
new file mode 100644
index 0000000000..fe40aaa8d7
--- /dev/null
+++ b/packages/frontend-plugin-api/src/blueprints/RouterBlueprint.test.tsx
@@ -0,0 +1,170 @@
+/*
+ * Copyright 2024 The Backstage Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+import React from 'react';
+import { RouterBlueprint } from './RouterBlueprint';
+import { MemoryRouter } from 'react-router-dom';
+import { render, waitFor } from '@testing-library/react';
+import { createSpecializedApp } from '@backstage/frontend-app-api';
+import {
+ coreExtensionData,
+ createExtension,
+ createExtensionInput,
+ createExtensionOverrides,
+} from '../wiring';
+import { MockConfigApi } from '@backstage/test-utils';
+import { PageBlueprint } from './PageBlueprint';
+
+describe('RouterBlueprint', () => {
+ it('should return an extension when calling make with sensible defaults', () => {
+ const extension = RouterBlueprint.make({
+ params: {
+ Component: props =>