Merge branch 'master' into anderoo/github-deployments-ghe

.changeset/chatty-ghosts-lay.md

@@ -1,5 +0,0 @@
----
-'@backstage/plugin-sonarqube': patch
----
-
-Export isSonarQubeAvailable.

.changeset/clever-walls-bow.md

@@ -1,5 +0,0 @@
----
-'@backstage/plugin-scaffolder-backend': patch
----
-
-Add built-in publish action for creating GitHub pull requests.

.changeset/dry-elephants-doubt.md

@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-github-deployments': patch
+---
+
+Adds extraColumns field to GitHub Deployments card

.changeset/fair-carrots-tell.md

@@ -0,0 +1,5 @@
+---
+'@backstage/cli': patch
+---
+
+Add `config:docs` command that opens up reference documentation for the local configuration schema in a browser.

.changeset/fluffy-suns-repair.md

@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-scaffolder': patch
+---
+
+Respect top-level UI schema keys in scaffolder forms. Allows more advanced RJSF features such as explicit field ordering.

.changeset/fresh-cheetahs-rush.md

@@ -0,0 +1,5 @@
+---
+'@backstage/cli': patch
+---
+
+No longer add newly created plugins to `plugins.ts` in the app, as it is no longer needed.

.changeset/good-glasses-build.md

@@ -0,0 +1,6 @@
+---
+'@backstage/core-api': patch
+'@backstage/core': patch
+---
+
+Add support for discovering plugins through the app element tree, removing the need to register them explicitly.

.changeset/loud-apricots-fix.md

@@ -1,31 +0,0 @@
----
-'@backstage/create-app': patch
-'@backstage/plugin-scaffolder': minor
----
-
-Expose the catalog-import route as an external route from the scaffolder.
-
-This will make it possible to hide the "Register Existing Component" button
-when you for example are running backstage with `catalog.readonly=true`.
-
-As a consequence of this change you need add a new binding to your createApp call to
-keep the button visible. However, if you instead want to hide the button you can safely
-ignore the following example.
-
-To bind the external route from the catalog-import plugin to the scaffolder template
-index page, make sure you have the appropriate imports and add the following
-to the createApp call:
-
-```typescript
-import { catalogImportPlugin } from '@backstage/plugin-catalog-import';
-
-const app = createApp({
-  // ...
-  bindRoutes({ bind }) {
-    // ...
-    bind(scaffolderPlugin.externalRoutes, {
-      registerComponent: catalogImportPlugin.routes.importPage,
-    });
-  },
-});
-```

.changeset/moody-pigs-repeat.md

@@ -0,0 +1,5 @@
+---
+'@backstage/core': patch
+---
+
+Exported SignInProviderConfig to strongly type SignInPage providers

.changeset/quiet-badgers-cheer.md

@@ -0,0 +1,11 @@
+---
+'@backstage/create-app': patch
+---
+
+Removed `plugins.ts` from the app, as plugins are now discovered through the react tree.
+
+To apply this change to an existing app, simply delete `packages/app/src/plugins.ts` along with the import and usage in `packages/app/src/App.tsx`.
+
+Note that there are a few plugins that require explicit registration, in which case you would need to keep them in `plugins.ts`. The set of plugins that need explicit registration is any plugin that doesn't have a component extension that gets rendered as part of the app element tree. An example of such a plugin in the main Backstage repo is `@backstage/plugin-badges`. In the case of the badges plugin this is because there is not yet a component-based API for adding context menu items to the entity layout.
+
+If you have plugins that still rely on route registration through the `register` method of `createPlugin`, these need to be kept in `plugins.ts` as well. However, it is recommended to migrate these to export an extensions component instead.

.changeset/real-apples-visit.md

@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-catalog-backend': patch
+---
+
+GithubDiscoveryProcessor now excludes archived repositories so they won't be added to Backstage.

.changeset/rude-items-bow.md

@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-kubernetes-backend': patch
+---
+
+Kubernetes client TLS verification is now configurable and defaults to true

.changeset/six-turtles-sip.md

@@ -0,0 +1,6 @@
+---
+'@backstage/backend-common': patch
+---
+
+Support configuration of file storage for SQLite databases. Every plugin has its
+own database file at the specified path.

.changeset/sour-plums-enjoy.md

@@ -0,0 +1,7 @@
+---
+'@backstage/create-app': patch
+---
+
+Fix system diagram card to be on the system page
+
+To apply the same fix to an existing application, in `EntityPage.tsx` simply move the `<EntityLayout.route>` for the `/diagram` path from the `groupPage` down into the `systemPage` element.

.changeset/stale-carpets-poke.md

@@ -0,0 +1,30 @@
+---
+'@backstage/plugin-catalog-backend': patch
+---
+
+Externalize repository processing for BitbucketDiscoveryProcessor.
+
+Add an extension point where you can customize how a matched Bitbucket repository should
+be processed. This can for example be used if you want to generate the catalog-info.yaml
+automatically based on other files in a repository, while taking advantage of the
+build-in repository crawling functionality.
+
+`BitbucketDiscoveryProcessor.fromConfig` now takes an optional parameter `options.parser` where
+you can customize the logic for each repository found. The default parser has the same
+behaviour as before, where it emits an optional location for the matched repository
+and lets the other processors take care of further processing.
+
+```typescript
+const customRepositoryParser: BitbucketRepositoryParser = async function* customRepositoryParser({
+  client,
+  repository,
+}) {
+  // Custom logic for interpret the matching repository.
+  // See defaultRepositoryParser for an example
+};
+
+const processor = BitbucketDiscoveryProcessor.fromConfig(env.config, {
+  parser: customRepositoryParser,
+  logger: env.logger,
+});
+```

.changeset/stale-chefs-retire.md

@@ -0,0 +1,5 @@
+---
+'@backstage/core': patch
+---
+
+Adding close button on support menu

.changeset/techdocs-swift-mugs-invent.md

@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-techdocs': patch
+---
+
+Add a test id to the shadow root element of the Reader to access it easily in e2e tests