Merge branch 'scaffolder-gitlab-mr-publish-v2' of https://github.com/Balasundaram/backstage into scaffolder-gitlab-mr-publish-v2

2021-12-09 13:07:16 -05:00
parent ed52f74ab3 0dea6ea33b
commit 5c1b87d044
1415 changed files with 53701 additions and 8811 deletions
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Switched to dynamically determining the packages that are unsafe to repack when executing the CLI within the Backstage main repo.
@@ -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 = {
@@ -0,0 +1,9 @@
+---
+'@backstage/core-components': minor
+---
+
+The `SignInPage` has been updated to use the new `onSignInSuccess` callback that was introduced in the same release. While existing code will usually continue to work, it is technically a breaking change because of the dependency on `SignInProps` from the `@backstage/core-plugin-api`. For more information on this change and instructions on how to migrate existing code, see the [`@backstage/core-app-api` CHANGELOG.md](https://github.com/backstage/backstage/blob/master/packages/core-app-api/CHANGELOG.md).
+
+Added a new `UserIdentity` class which helps create implementations of the `IdentityApi`. It provides a couple of static factory methods such as the most relevant `create`, and `createGuest` to create an `IdentityApi` for a guest user.
+
+Also provides a deprecated `fromLegacy` method to create an `IdentityApi` from the now deprecated `SignInResult`. This method will be removed in the future when `SignInResult` is also removed.
@@ -0,0 +1,6 @@
+---
+'@backstage/plugin-auth-backend': patch
+---
+
+Fixes potential bug introduced in `0.4.10` which causes `OAuth2AuthProvider` to authenticate using credentials in both POST payload and headers.
+This might break some stricter OAuth2 implementations so there is now a `includeBasicAuth` config option that can manually be set to `true` to enable this behavior.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-kubernetes': patch
---
-
-fix: kubernetes plugin shall pass id token on get clusters request if possible
@@ -0,0 +1,17 @@
+---
+'@backstage/core-plugin-api': minor
+---
+
+The `IdentityApi` has received several updates. The `getUserId`, `getProfile`, and `getIdToken` have all been deprecated.
+
+The replacement for `getUserId` is the new `getBackstageIdentity` method, which provides both the `userEntityRef` as well as the `ownershipEntityRefs` that are used to resolve ownership. Existing usage of the user ID would typically be using a fixed entity kind and namespace, for example `` `user:default/${identityApi.getUserId()}` ``, this kind of usage should now instead use the `userEntityRef` directly.
+
+The replacement for `getProfile` is the new async `getProfileInfo`.
+
+The replacement for `getIdToken` is the new `getCredentials` method, which provides an optional token to the caller like before, but it is now wrapped in an object for forwards compatibility.
+
+The deprecated `idToken` field of the `BackstageIdentity` type has been removed, leaving only the new `token` field, which should be used instead. The `BackstageIdentity` also received a new `identity` field, which is a decoded version of the information within the token. Furthermore the `BackstageIdentity` has been renamed to `BackstageIdentityResponse`, with the old name being deprecated.
+
+We expect most of the breaking changes in this update to have low impact since the `IdentityApi` implementation is provided by the app, but it is likely that some tests need to be updated.
+
+Another breaking change is that the `SignInPage` props have been updated, and the `SignInResult` type is now deprecated. This is unlikely to have any impact on the usage of this package, but it is an important change that you can find more information about in the [`@backstage/core-app-api` CHANGELOG.md](https://github.com/backstage/backstage/blob/master/packages/core-app-api/CHANGELOG.md).
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-cloudbuild': patch
+---
+
+Remove unnecessary dependency.
@@ -0,0 +1,7 @@
+---
+'@backstage/core-components': patch
+'@backstage/create-app': patch
+'@backstage/plugin-catalog': patch
+---
+
+Addressed some peer dependency warnings
@@ -1,8 +0,0 @@
---
-'@backstage/core-components': patch
-'@backstage/theme': patch
---
-
-Added a warning variant to `DismissableBanner` component. If you are using a
-custom theme, you will need to add the optional `palette.banner.warning` color,
-otherwise this variant will fall back to the `palette.banner.error` color.
@@ -1,7 +0,0 @@
---
-'@backstage/plugin-catalog-backend-module-msgraph': patch
---
-
-Tweak logic for msgraph catalog ingesting for display names with security groups
-
-Previously security groups that weren't mail enabled were imported with UUIDs, now they use the display name.
@@ -0,0 +1,35 @@
+---
+'@backstage/core-app-api': minor
+---
+
+**BREAKING CHANGE**
+
+The app `SignInPage` component has been updated to switch out the `onResult` callback for a new `onSignInSuccess` callback. This is an immediate breaking change without any deprecation period, as it was deemed to be the way of making this change that had the lowest impact.
+
+The new `onSignInSuccess` callback directly accepts an implementation of an `IdentityApi`, rather than a `SignInResult`. The `SignInPage` from `@backstage/core-component` has been updated to fit this new API, and as long as you pass on `props` directly you should not see any breakage.
+
+However, if you implement your own custom `SignInPage`, then this will be a breaking change and you need to migrate over to using the new callback. While doing so you can take advantage of the `UserIdentity.fromLegacy` helper from `@backstage/core-components` to make the migration simpler by still using the `SignInResult` type. This helper is also deprecated though and is only provided for immediate migration. Long-term it will be necessary to build the `IdentityApi` using for example `UserIdentity.create` instead.
+
+The following is an example of how you can migrate existing usage immediately using `UserIdentity.fromLegacy`:
+
+```ts
+onResult(signInResult);
+// becomes
+onSignInSuccess(UserIdentity.fromLegacy(signInResult));
+```
+
+The following is an example of how implement the new `onSignInSuccess` callback of the `SignInPage` using `UserIdentity.create`:
+
+```ts
+const identityResponse = await authApi.getBackstageIdentity();
+// Profile is optional and will be removed, but allows the
+// synchronous getProfile method of the IdentityApi to be used.
+const profile = await authApi.getProfile();
+onSignInSuccess(
+  UserIdentity.create({
+    identity: identityResponse.identity,
+    authApi,
+    profile,
+  }),
+);
+```
@@ -1,5 +0,0 @@
---
-'@backstage/backend-common': patch
---
-
-AWSS3UrlReader now throws a `NotModifiedError` (exported from @backstage/backend-common) when s3 returns a 304 response.
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-scaffolder': patch
+---
+
+Can specify allowedOwners to the RepoUrlPicker picker in a template definition
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-jenkins-backend': patch
---
-
-Don't require a validation pattern for the Jenkins base URL.
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-scaffolder-backend': patch
+---
+
+Bump esbuild to ^0.14.1
@@ -1,5 +0,0 @@
---
-'@backstage/core-components': patch
---
-
-Allow for `cellStyle` property on `TableColumn` to be a function as well as `React.CSSProperties` as per the Material UI Table component
@@ -0,0 +1,14 @@
+---
+'@backstage/plugin-kubernetes': minor
+'@backstage/plugin-kubernetes-backend': minor
+'@backstage/plugin-kubernetes-common': minor
+---
+
+Add pod metrics lookup and display in pod table.
+
+## Backwards incompatible changes
+
+If your Kubernetes distribution does not have the [metrics server](https://github.com/kubernetes-sigs/metrics-server) installed,
+you will need to set the `skipMetricsLookup` config flag to `false`.
+
+See the [configuration docs](https://backstage.io/docs/features/kubernetes/configuration) for more details.
@@ -0,0 +1,60 @@
+---
+'@backstage/app-defaults': patch
+'@backstage/core-app-api': patch
+'@backstage/core-components': patch
+'@backstage/core-plugin-api': patch
+'@backstage/dev-utils': patch
+'@backstage/integration-react': patch
+'@backstage/test-utils': patch
+'@backstage/version-bridge': patch
+'@backstage/plugin-allure': patch
+'@backstage/plugin-analytics-module-ga': patch
+'@backstage/plugin-api-docs': patch
+'@backstage/plugin-azure-devops': patch
+'@backstage/plugin-badges': patch
+'@backstage/plugin-bazaar': patch
+'@backstage/plugin-bitrise': patch
+'@backstage/plugin-catalog': patch
+'@backstage/plugin-catalog-graph': patch
+'@backstage/plugin-catalog-import': patch
+'@backstage/plugin-catalog-react': patch
+'@backstage/plugin-circleci': patch
+'@backstage/plugin-cloudbuild': patch
+'@backstage/plugin-code-coverage': patch
+'@backstage/plugin-config-schema': patch
+'@backstage/plugin-cost-insights': patch
+'@backstage/plugin-explore': patch
+'@backstage/plugin-firehydrant': patch
+'@backstage/plugin-fossa': patch
+'@backstage/plugin-gcp-projects': patch
+'@backstage/plugin-git-release-manager': patch
+'@backstage/plugin-github-actions': patch
+'@backstage/plugin-github-deployments': patch
+'@backstage/plugin-gitops-profiles': patch
+'@backstage/plugin-graphiql': patch
+'@backstage/plugin-home': patch
+'@backstage/plugin-ilert': patch
+'@backstage/plugin-jenkins': patch
+'@backstage/plugin-kafka': patch
+'@backstage/plugin-kubernetes': patch
+'@backstage/plugin-lighthouse': patch
+'@backstage/plugin-newrelic': patch
+'@backstage/plugin-org': patch
+'@backstage/plugin-pagerduty': patch
+'@backstage/plugin-permission-react': patch
+'@backstage/plugin-rollbar': patch
+'@backstage/plugin-scaffolder': patch
+'@backstage/plugin-search': patch
+'@backstage/plugin-sentry': patch
+'@backstage/plugin-shortcuts': patch
+'@backstage/plugin-sonarqube': patch
+'@backstage/plugin-splunk-on-call': patch
+'@backstage/plugin-tech-insights': patch
+'@backstage/plugin-tech-radar': patch
+'@backstage/plugin-techdocs': patch
+'@backstage/plugin-todo': patch
+'@backstage/plugin-user-settings': patch
+'@backstage/plugin-xcmetrics': patch
+---
+
+Moved React dependencies to `peerDependencies` and allow both React v16 and v17 to be used.
@@ -0,0 +1,25 @@
+---
+'@backstage/backend-common': patch
+'@backstage/core-app-api': patch
+'@backstage/core-components': patch
+'@backstage/core-plugin-api': patch
+'@backstage/dev-utils': patch
+'@backstage/techdocs-common': patch
+'@backstage/test-utils': patch
+'@backstage/plugin-analytics-module-ga': patch
+'@backstage/plugin-auth-backend': patch
+'@backstage/plugin-catalog-backend': patch
+'@backstage/plugin-config-schema': patch
+'@backstage/plugin-github-deployments': patch
+'@backstage/plugin-pagerduty': patch
+'@backstage/plugin-permission-node': patch
+'@backstage/plugin-permission-react': patch
+'@backstage/plugin-search-backend': patch
+'@backstage/plugin-search-backend-module-elasticsearch': patch
+'@backstage/plugin-search-backend-module-pg': patch
+'@backstage/plugin-techdocs-backend': patch
+'@backstage/plugin-todo': patch
+'@backstage/plugin-todo-backend': patch
+---
+
+Minor improvement to the API reports, by not unpacking arguments directly
@@ -1,7 +0,0 @@
---
-'@backstage/backend-common': patch
-'@backstage/cli': patch
-'@backstage/config-loader': patch
---
-
-Reading app config from a remote server
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-catalog-backend': patch
+---
+
+The `pagedRequest` method in the GitLab ingestion client is now public for re-use and may be used to make other calls to the GitLab API. Developers can now pass in a type into the GitLab `paginated` and `pagedRequest` functions as generics instead of forcing `any` (defaults to `any` to maintain compatibility). The `GitLabClient` now provides a `isSelfManaged` convenience method.
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-catalog-backend': patch
+---
+
+Reject catalog entities that have duplicate fields that vary only in casing.
@@ -0,0 +1,5 @@
+---
+'@backstage/backend-common': patch
+---
+
+Add possibility to use custom error handler
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-techdocs': patch
+---
+
+Switch to using `LogViewer` component from `@backstage/core-components` to display build logs.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-search-backend-module-elasticsearch': patch
---
-
-Pinning version of elastic search client to 7.13.0 to prevent breaking change towards third party ElasticSearch clusters on 7.14.0.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-ilert': patch
---
-
-Change the version of `@date-io/luxon` from 2.x to 1.x to make it compatible with material-ui-pickers
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-scaffolder': patch
+---
+
+Fix bug with setting owner in RepoUrlPicker causing validation failure
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-kafka': patch
---
-
-Use IdentityApi to provide Auth Token for KafkaBackendClient Api calls
@@ -1,5 +0,0 @@
---
-'@backstage/test-utils': patch
---
-
-Update Keyboard deprecation with a link to the recommended successor
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-scaffolder-backend': patch
---
-
-Expose some classes and interfaces public so TaskWorkers can run externally from the scaffolder API.
@@ -0,0 +1,8 @@
+---
+'@backstage/plugin-permission-backend': patch
+'@backstage/plugin-permission-node': patch
+---
+
+Updated to use the new `BackstageIdentityResponse` type from `@backstage/plugin-auth-backend`.
+
+The `BackstageIdentityResponse` type is backwards compatible with the `BackstageIdentity`, and provides an additional `identity` field with the claims of the user.
@@ -0,0 +1,5 @@
+---
+'@backstage/core-components': patch
+---
+
+Introduce new `LogViewer` component that can be used to display logs. It supports copying, searching, filtering, and displaying text with ANSI color escape codes.
@@ -1,9 +0,0 @@
---
-'@backstage/plugin-azure-devops': patch
-'@backstage/plugin-azure-devops-backend': minor
-'@backstage/plugin-azure-devops-common': patch
---
-
-refactor(`@backstage/plugin-azure-devops`): Consume types from `@backstage/plugin-azure-devops-common`.
-Stop re-exporting types from `@backstage/plugin-azure-devops-backend`.
-Added new types to `@backstage/plugin-azure-devops-common`.
@@ -1,5 +0,0 @@
---
-'@backstage/catalog-client': patch
---
-
-Improved API documentation for catalog-client.
@@ -1,15 +0,0 @@
---
-'@backstage/techdocs-common': patch
---
-
-1. Techdocs publisher constructors now use parameter objects when being
-   instantiated
-
-2. Internal refactor of `LocalPublish` publisher to use `fromConfig` for
-   creation to be aligned with other publishers; this does not impact
-   `LocalPublish` usage.
-
-```diff
- const publisher = new LocalPublish(config, logger, discovery);
-+ const publisher = LocalPublish.fromConfig(config, logger, discovery);
-```
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-scaffolder-backend-module-rails': minor
+---
+
+update publish format from ESM to CJS
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-auth-backend': patch
---
-
-Only use settings that have a value when creating a new FirestoreKeyStore instance
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-sentry': patch
---
-
-fix: sentry-plugin can forward identity token to backend (for case when it requires authorization)
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-code-coverage': patch
---
-
-Change represented test date from epoch to something more human friendly. Round test coverage to 2 decimal places.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Make `ExitCodeError` call `super` early to avoid compiler warnings
@@ -1,14 +0,0 @@
---
-'@backstage/create-app': patch
---
-
-Updated the app template to no longer include the `--no-private` flag for the `create-plugin` command.
-
-To apply this change to an existing application, remove the `--no-private` flag from the `create-plugin` command in the root `package.json`:
-
-```diff
-   "prettier:check": "prettier --check .",
-  "create-plugin": "backstage-cli create-plugin --scope internal --no-private",
-+  "create-plugin": "backstage-cli create-plugin --scope internal",
-   "remove-plugin": "backstage-cli remove-plugin"
-```
@@ -0,0 +1,11 @@
+---
+'@backstage/plugin-auth-backend': minor
+---
+
+**BREAKING CHANGE** The `idToken` field of `BackstageIdentity` has been removed, with the `token` taking its place. This means you may need to update existing `signIn.resolver` implementations to return an `token` rather than an `idToken`. This also applies to custom auth providers.
+
+The `BackstageIdentity` type has been deprecated and will be removed in the future. Taking its place is the new `BackstageSignInResult` type with the same shape.
+
+This change also introduces the new `BackstageIdentityResponse` that mirrors the type with the same name from `@backstage/core-plugin-api`. The `BackstageIdentityResponse` type is different from the `BackstageSignInResult` in that it also has a `identity` field which is of type `BackstageUserIdentity` and is a decoded version of the information within the token.
+
+When implementing a custom auth provider that is not based on the `OAuthAdapter` you may need to convert `BackstageSignInResult` into a `BackstageIdentityResponse`, this can be done using the new `prepareBackstageIdentityResponse` function.
@@ -0,0 +1,5 @@
+---
+'@backstage/core-components': patch
+---
+
+Standardize on `classnames` instead of both that and `clsx`.
@@ -1,5 +0,0 @@
---
-'@backstage/config-loader': patch
---
-
-Bump msw to the same version as the rest
@@ -2,4 +2,4 @@
 '@backstage/plugin-catalog-backend': patch
 ---

-Allow singleton and flexibly nested EntityFilters
+Honor database migration configuration
@@ -0,0 +1,5 @@
+---
+'@backstage/core-components': patch
+---
+
+Use ellipsis style for overflowed text in sidebar menu
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-code-coverage': patch
---
-
-Make dates in X-Axis sort in ascending order
@@ -0,0 +1,10 @@
+---
+'@backstage/cli': patch
+---
+
+Add cli option to minify the generated code of a plugin or backend package
+
+```
+backstage-cli plugin:build --minify
+backstage-cli backend:build --minify
+```
@@ -0,0 +1,6 @@
+---
+'@backstage/plugin-azure-devops-backend': patch
+'@backstage/plugin-azure-devops-common': patch
+---
+
+Added getting builds by definition name
@@ -1,5 +0,0 @@
---
-'@backstage/core-components': patch
---
-
-fixed route resolving (issue #7741) when user cannot select a tab in any of the tabbed pages (like the Catalog page) if it shares the same initial letters as a preceding tab. (i.e. where tab with a path of /ci is followed by a path of /ci-2, user cannot select /ci-2 as /ci will always be selected first).
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-github-actions': patch
+---
+
+Switch to using `LogViewer` component from `@backstage/core-components` to display build logs.
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-circleci': patch
+---
+
+Switch to using `LogViewer` component from `@backstage/core-components` to display action output.
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-search': patch
+---
+
+Export SearchApi interface from plugin
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-auth-backend': patch
---
-
-Added forwarding of the `audience` option for the SAML provider, making it possible to enable `audience` verification.
@@ -1,42 +0,0 @@
---
-'@backstage/plugin-scaffolder': patch
-'@backstage/plugin-scaffolder-backend': patch
---
-
-Adds a new endpoint for consuming logs from the Scaffolder that uses long polling instead of Server Sent Events.
-
-This is useful if Backstage is accessed from an environment that doesn't support SSE correctly, which happens in combination with certain enterprise HTTP Proxy servers.
-
-It is intended to switch the endpoint globally for the whole instance.
-If you want to use it, you can provide a reconfigured API to the `scaffolderApiRef`:
-
-```tsx
-// packages/app/src/apis.ts
-
-// ...
-import {
-  scaffolderApiRef,
-  ScaffolderClient,
-} from '@backstage/plugin-scaffolder';
-
-export const apis: AnyApiFactory[] = [
-  // ...
-
-  createApiFactory({
-    api: scaffolderApiRef,
-    deps: {
-      discoveryApi: discoveryApiRef,
-      identityApi: identityApiRef,
-      scmIntegrationsApi: scmIntegrationsApiRef,
-    },
-    factory: ({ discoveryApi, identityApi, scmIntegrationsApi }) =>
-      new ScaffolderClient({
-        discoveryApi,
-        identityApi,
-        scmIntegrationsApi,
-        // use long polling instead of an eventsource
-        useLongPollingLogs: true,
-      }),
-  }),
-];
-```
@@ -0,0 +1,5 @@
+---
+'@backstage/cli': patch
+---
+
+Updated the frontend plugin template to put React dependencies in `peerDependencies` by default, as well as allowing both React v16 and v17. This change can be applied to existing plugins by running `yarn backstage-cli plugin:diff` within the plugin package directory.
@@ -0,0 +1,5 @@
+---
+'@backstage/backend-common': patch
+---
+
+Add options argument to support additional database migrations configuration
@@ -1,14 +0,0 @@
---
-'@backstage/create-app': patch
---
-
-Removed the version pinning of the packages `graphql-language-service-interface` and `graphql-language-service-parser`. This should no longer be necessary.
-
-You can apply the same change in your repository by ensuring that the following does _NOT_ appear in your root `package.json`.
-
-```json
-"resolutions": {
-  "graphql-language-service-interface": "2.8.2",
-  "graphql-language-service-parser": "1.9.0"
-  },
-```
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-analytics-module-ga': patch
+---
+
+Support self hosted analytics.js script via `scriptSrc` config option
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-react': patch
---
-
-export `loadIdentityOwnerRefs` and `loadCatalogOwnerRefs` all the way
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-scaffolder': patch
+---
+
+Switch to using `LogViewer` component from `@backstage/core-components` to display scaffolder logs.
@@ -1,5 +0,0 @@
---
-'@backstage/core-app-api': patch
---
-
-I have added default icons for the catalog, scaffolder, techdocs, and search.
@@ -0,0 +1,5 @@
+---
+'@backstage/backend-common': patch
+---
+
+Add knexConfig config section
@@ -1,5 +0,0 @@
---
-'@backstage/core-components': patch
---
-
-Add Theme Overrides for Sidebar
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Bumped `@spotify/eslint-config-typescript` from `v10` to `v12`, dropping support for Node.js v12.
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-techdocs': patch
+---
+
+The problem of lowercase entity triplets which causes docs to not load on entity page is fixed.
@@ -1,5 +0,0 @@
---
-'@backstage/techdocs-common': patch
---
-
-Default TechDocs container used at docs generation-time is now [v0.3.5](https://github.com/backstage/techdocs-container/releases/tag/v0.3.5).
@@ -0,0 +1,7 @@
+---
+'@backstage/techdocs-common': minor
+'@backstage/plugin-techdocs-backend': minor
+---
+
+Added the ability for the TechDocs Backend to (optionally) leverage a cache
+store to improve performance when reading files from a cloud storage provider.
@@ -1,5 +0,0 @@
---
-'@backstage/techdocs-common': patch
---
-
-Updated to properly join URL segments under any OS for both AWS S3 and GCP
@@ -1,6 +0,0 @@
---
-'@backstage/core-app-api': patch
-'@backstage/core-plugin-api': patch
---
-
-Improve API documentation for @backstage/core-plugin-api
@@ -0,0 +1,42 @@
+---
+'@backstage/create-app': patch
+---
+
+TechDocs Backend may now (optionally) leverage a cache store to improve
+performance when reading content from a cloud storage provider.
+
+To apply this change to an existing app, pass the cache manager from the plugin
+environment to the `createRouter` function in your backend:
+
+```diff
+// packages/backend/src/plugins/techdocs.ts
+
+export default async function createPlugin({
+  logger,
+  config,
+  discovery,
+  reader,
+  cache,
+}: PluginEnvironment): Promise<Router> {
+
+  // ...
+
+  return await createRouter({
+    preparers,
+    generators,
+    publisher,
+    logger,
+    config,
+    discovery,
+    cache,
+  });
+```
+
+If your `PluginEnvironment` does not include a cache manager, be sure you've
+applied [the cache management change][cm-change] to your backend as well.
+
+[Additional configuration][td-rec-arch] is required if you wish to enable
+caching in TechDocs.
+
+[cm-change]: https://github.com/backstage/backstage/blob/master/packages/create-app/CHANGELOG.md#patch-changes-6
+[td-rec-arch]: https://backstage.io/docs/features/techdocs/architecture#recommended-deployment
@@ -0,0 +1,5 @@
+---
+'@backstage/create-app': patch
+---
+
+Bump @spotify/prettier-config
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-xcmetrics': patch
+---
+
+Handle a case where XCode data from backend (before 0.0.8) could be missing
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-catalog-react': patch
+---
+
+Fix typo in catalog-react package.json
@@ -0,0 +1,5 @@
+---
+'@backstage/plugin-bazaar-backend': patch
+---
+
+Handle migration error when old data is present in the database
@@ -0,0 +1,5 @@
+---
+'@backstage/create-app': patch
+---
+
+Removed the `scaffolder.github.visibility` configuration that is no longer used from the default app template.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-azure-devops': patch
---
-
-Simplified queue time calculation in `BuildTable`.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-scaffolder-backend': patch
---
-
-Fix a bug where only file mode 775 is considered an executable
@@ -1,7 +0,0 @@
---
-'@backstage/plugin-scaffolder-backend-module-cookiecutter': patch
-'@backstage/plugin-scaffolder-backend-module-rails': patch
-'@backstage/plugin-scaffolder-backend-module-yeoman': patch
---
-
-Add missing API docs to scaffolder action plugins
@@ -1,5 +0,0 @@
---
-'@backstage/core-plugin-api': patch
---
-
-Deprecate unused ApiRef types