Merge remote-tracking branch 'origin/master' into natasha/b2b-auth

Signed-off-by: Mike Lewis <mtlewis@users.noreply.github.com>

.changeset/afraid-chairs-warn.md

@@ -0,0 +1,6 @@
+---
+'@backstage/errors': patch
+---
+
+Deprecate `parseErrorResponse` in favour of `parseErrorResponseBody`. Deprecate `data` field inside `ErrorResponse` in favour of `body`.
+Rename the error name for unknown errors from `unknown` to `error`.

.changeset/backstage-changelog.js

@@ -23,13 +23,13 @@ const {
 async function getDependencyReleaseLine(changesets, dependenciesUpdated) {
   if (dependenciesUpdated.length === 0) return '';
 
-  const updatedDepenenciesList = dependenciesUpdated.map(
+  const updatedDependenciesList = dependenciesUpdated.map(
     dependency => `  - ${dependency.name}@${dependency.newVersion}`,
   );
 
   // Return one `Updated dependencies` bullet instead of repeating for each changeset; this
   // sacrifices the commit shas for brevity.
-  return ['- Updated dependencies', ...updatedDepenenciesList].join('\n');
+  return ['- Updated dependencies', ...updatedDependenciesList].join('\n');
 }
 
 module.exports = {

.changeset/curly-points-hide.md

@@ -0,0 +1,6 @@
+---
+'@backstage/plugin-tech-insights-backend': patch
+'@backstage/plugin-tech-insights-backend-module-jsonfc': patch
+---
+
+Update README docs to use correct function/parameter names

.changeset/forty-teachers-argue.md

@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-auth-backend': patch
+---
+
+Switched to using the standardized JSON error responses for all provider endpoints.

.changeset/giant-bees-applaud.md

@@ -0,0 +1,5 @@
+---
+'@backstage/cli': patch
+---
+
+Switch the default test coverage provider from the jest default one to `'v8'`, which provides much better coverage information when using the default Backstage test setup. This is considered a bug fix as the current coverage information is often very inaccurate.

.changeset/large-mugs-repair.md

@@ -0,0 +1,5 @@
+---
+'@backstage/cli': patch
+---
+
+Disable ES transforms in tests transformed by the `jestSucraseTransform.js`. This is not considered a breaking change since all code is already transpiled this way in the development setup.

.changeset/large-pears-agree.md

@@ -0,0 +1,5 @@
+---
+'@backstage/create-app': patch
+---
+
+DefaultTechDocsCollator is now included in the search backend, and the Search Page updated with the SearchType component that includes the techdocs type

.changeset/pretty-trains-appear.md

@@ -0,0 +1,34 @@
+---
+'@backstage/backend-common': patch
+'@backstage/cli': patch
+'@backstage/core-app-api': patch
+'@backstage/create-app': patch
+'@backstage/techdocs-common': patch
+'@backstage/plugin-auth-backend': patch
+'@backstage/plugin-azure-devops-backend': patch
+'@backstage/plugin-badges-backend': patch
+'@backstage/plugin-bazaar-backend': patch
+'@backstage/plugin-catalog-backend': patch
+'@backstage/plugin-code-coverage-backend': patch
+'@backstage/plugin-github-actions': patch
+'@backstage/plugin-jenkins-backend': patch
+'@backstage/plugin-proxy-backend': patch
+'@backstage/plugin-rollbar-backend': patch
+'@backstage/plugin-search-backend': patch
+'@backstage/plugin-techdocs': patch
+'@backstage/plugin-techdocs-backend': patch
+---
+
+Change default port of backend from 7000 to 7007.
+
+This is due to the AirPlay Receiver process occupying port 7000 and preventing local Backstage instances on MacOS to start.
+
+You can change the port back to 7000 or any other value by providing an `app-config.yaml` with the following values:
+
+```
+backend:
+  listen: 0.0.0.0:7123
+  baseUrl: http://localhost:7123
+```
+
+More information can be found here: https://backstage.io/docs/conf/writing

.changeset/purple-grapes-attack.md

@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-permission-common': minor
+---
+
+Accept configApi rather than enabled flag in PermissionClient constructor.

.changeset/smart-fans-complain.md

@@ -0,0 +1,42 @@
+---
+'@backstage/plugin-catalog-backend': minor
+---
+
+**BREAKING** EntitiesSearchFilter fields have changed.
+
+EntitiesSearchFilter now has only two fields: `key` and `value`. The `matchValueIn` and `matchValueExists` fields are no longer are supported. Previous filters written using the `matchValueIn` and `matchValueExists` fields can be rewritten as follows:
+
+Filtering by existence of key only:
+
+```diff
+  filter: {
+    {
+      key: 'abc',
+-     matchValueExists: true,
+    },
+  }
+```
+
+Filtering by key and values:
+
+```diff
+  filter: {
+    {
+      key: 'abc',
+-     matchValueExists: true,
+-     matchValueIn: ['xyz'],
++     values: ['xyz'],
+    },
+  }
+```
+
+Negation of filters can now be achieved through a `not` object:
+
+```
+filter: {
+  not: {
+    key: 'abc',
+    values: ['xyz'],
+  },
+}
+```

.changeset/smooth-vans-boil.md

@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-catalog-backend': patch
+---
+
+Index User entities by displayName to be able to search by full name. Added displayName (if present) to the 'text' field in the indexed document.

.changeset/weak-berries-sing.md

@@ -0,0 +1,5 @@
+---
+'@backstage/cli': patch
+---
+
+Update the default routes to use id instead of title

.changeset/wet-seas-deliver.md

@@ -0,0 +1,63 @@
+---
+'@backstage/core-app-api': patch
+'@backstage/test-utils': patch
+---
+
+The `ApiRegistry` from `@backstage/core-app-api` class has been deprecated and will be removed in a future release. To replace it, we have introduced two new helpers that are exported from `@backstage/test-utils`, namely `TestApiProvider` and `TestApiRegistry`.
+
+These two new helpers are more tailored for writing tests and development setups, as they allow for partial implementations of each of the APIs.
+
+When migrating existing code it is typically best to prefer usage of `TestApiProvider` when possible, so for example the following code:
+
+```tsx
+render(
+  <ApiProvider
+    apis={ApiRegistry.from([
+      [identityApiRef, mockIdentityApi as unknown as IdentityApi]
+    ])}
+  >
+    {...}
+  </ApiProvider>
+)
+```
+
+Would be migrated to this:
+
+```tsx
+render(
+  <TestApiProvider apis={[[identityApiRef, mockIdentityApi]]}>
+    {...}
+  </TestApiProvider>
+)
+```
+
+In cases where the `ApiProvider` is used in a more standalone way, for example to reuse a set of APIs across multiple tests, the `TestApiRegistry` can be used instead. Note that the `TestApiRegistry` only has a single static factory method, `.from()`, and it is slightly different from the existing `.from()` method on `ApiRegistry` in that it doesn't require the API pairs to be wrapped in an outer array.
+
+Usage that looks like this:
+
+```ts
+const apis = ApiRegistry.with(
+  identityApiRef,
+  mockIdentityApi as unknown as IdentityApi,
+).with(configApiRef, new ConfigReader({}));
+```
+
+OR like this:
+
+```ts
+const apis = ApiRegistry.from([
+  [identityApiRef, mockIdentityApi as unknown as IdentityApi],
+  [configApiRef, new ConfigReader({})],
+]);
+```
+
+Would be migrated to this:
+
+```ts
+const apis = TestApiRegistry.from(
+  [identityApiRef, mockIdentityApi],
+  [configApiRef, new ConfigReader({})],
+);
+```
+
+If your app is still using the `ApiRegistry` to construct the `apis` for `createApp`, we recommend that you move over to use the new method of supplying API factories instead, using `createApiFactory`.

.changeset/yellow-pandas-draw.md

@@ -0,0 +1,5 @@
+---
+'@backstage/core-components': patch
+---
+
+Pin sidebar by default for easier navigation