Version Packages

2020-12-17 10:16:33 +00:00
parent 9d7b50f2f3
commit 6e9f4d4a15
101 changed files with 862 additions and 432 deletions
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-Add support for Github Enterprise in GitHubOrgReaderProcessor so you can properly ingest users of a GHE organization.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-org': patch
---
-
-Wrap entity cards on smaller screens
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-cost-insights': patch
---
-
-pin all projects selection to the top of menu list
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-Break the refresh loop into several smaller transactions
@@ -1,6 +0,0 @@
---
-'@backstage/catalog-model': patch
---
-
-Introduce a `profile` section for group entities that can optional include a
-`displayName`, `email` and `picture`.
@@ -1,7 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-Support `profile` of groups including `displayName`, `email`, and `picture` in
-`LdapOrgReaderProcessor`. The source fields for them can be configured in the
-`ldapOrg` provider.
@@ -1,6 +0,0 @@
---
-'@backstage/plugin-org': patch
---
-
-Ensure a name is always displayed for user entities in the org plugin. This can happen when there is no profile
-displayName provided (e.g. a GitHub user that has not added a name to their profile)
@@ -1,45 +0,0 @@
---
-'@backstage/techdocs-common': minor
-'@backstage/plugin-techdocs': minor
-'@backstage/plugin-techdocs-backend': minor
---
-
-_Breaking changes_
-
-1. Added option to use Google Cloud Storage as a choice to store the static generated files for TechDocs.
-   It can be configured using `techdocs.publisher.type` option in `app-config.yaml`.
-   Step-by-step guide to configure GCS is available here https://backstage.io/docs/features/techdocs/using-cloud-storage
-   Set `techdocs.publisher.type` to `'local'` if you want to continue using local filesystem to store TechDocs files.
-
-2. `techdocs.builder` is now required and can be set to `'local'` or `'external'`. (Set it to `'local'` for now, since CI/CD build
-   workflow for TechDocs will be available soon (in few weeks)).
-   If builder is set to 'local' and you open a TechDocs page, `techdocs-backend` will try to generate the docs, publish to storage and
-   show the generated docs afterwords.
-   If builder is set to `'external'`, `techdocs-backend` will only fetch the docs and will NOT try to generate and publish. In this case of `'external'`,
-   we assume that docs are being built in the CI/CD pipeline of the repository.
-   TechDocs will not assume a default value for `techdocs.builder`. It is better to explicitly define it in the `app-config.yaml`.
-
-3. When configuring TechDocs in your backend, there is a difference in how a new publisher is created.
-
-```
---  const publisher = new LocalPublish(logger, discovery);
-+++  const publisher = Publisher.fromConfig(config, logger, discovery);
-```
-
-Based on the config `techdocs.publisher.type`, the publisher could be either Local publisher or Google Cloud Storage publisher.
-
-4. `techdocs.storageUrl` is now a required config. Should be `http://localhost:7000/api/techdocs/static/docs` in most setups.
-
-5. Parts of `@backstage/plugin-techdocs-backend` have been moved to a new package `@backstage/techdocs-common` to generate docs. Also to publish docs
-   to-and-fro between TechDocs and a storage (either local or external). However, a Backstage app does NOT need to import the `techdocs-common` package -
-   app should only import `@backstage/plugin-techdocs` and `@backstage/plugin-techdocs-backend`.
-
-_Patch changes_
-
-1. See all of TechDocs config options and its documentation https://backstage.io/docs/features/techdocs/configuration
-
-2. Logic about serving static files and metadata retrieval have been abstracted away from the router in `techdocs-backend` to the instance of publisher.
-
-3. Removed Material UI Spinner from TechDocs header. Spinners cause unnecessary UX distraction.
-   Case 1 (when docs are built and are to be served): Spinners appear for a split second before the name of site shows up. This unnecessarily distracts eyes because spinners increase the size of the Header. A dot (.) would do fine. Definitely more can be done.
-   Case 2 (when docs are being generated): There is already a linear progress bar (which is recommended in Storybook).
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-auth-backend': patch
---
-
-Added configuration schema for the commonly used properties
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-Break out GithubOrgReaderProcessor config into its own file for consistency with the other org processors.
@@ -1,6 +0,0 @@
---
-'@backstage/core': patch
-'@backstage/plugin-org': patch
---
-
-Add a `<Avatar>` component to `@backstage/core`.
@@ -1,6 +0,0 @@
---
-'@backstage/backend-common': patch
-'@backstage/integration': patch
---
-
-Implement readTree on BitBucketUrlReader and getBitbucketDownloadUrl
@@ -1,5 +0,0 @@
---
-'@backstage/catalog-model': patch
---
-
-Ignore relations when comparing entities. This stops the refresh loop from rewriting entities over and over.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-import': patch
---
-
-Add description to Pull Request when registering a new component
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-pagerduty': patch
---
-
-Supporting Timezones
@@ -1,6 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-Support `profile` of groups including `displayName` and `picture` in
-`GithubOrgReaderProcessor`. Fixes the import of `description` for groups.
@@ -1,6 +0,0 @@
---
-'@backstage/backend-common': patch
-'@backstage/integration': patch
---
-
-Introduce readTree method for GitLab URL Reader
@@ -1,26 +0,0 @@
---
-'@backstage/plugin-catalog-backend': minor
---
-
-Write relations directly as part of batch add / update of entities.
-
-Slight change of the `CommonDatabase` contract:
-
-## `addEntity` removed
-
-This method was unused by the core, and rendered unnecessary when `addEntities`
-exists.
-
-If you were a user of `addEntity`, please call `addEntities` instead, with an
-array of one element.
-
-## `DbEntityRequest` has a new field `relations`
-
-This is the structure that is passed to `addEntities` and `updateEntity`. It
-used to be the case that you needed to call `setRelations` separately, but now
-this instead happens directly when you call `addEntities` or `updateEntity`.
-
-If you were using `addEntities` or `updateEntity` directly, please adapt your
-code to add the `relations` array to each request. If you were calling
-`setRelations` separately next to these methods, you no longer need to do so,
-after adding the relations to the `DbEntityRequest`s.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-Batch the writing of statuses after refreshes. This reduced the runtime on sqlite from 16s to 0.2s, and on pg from 60s to 1s on my machine, for the huge LDAP set.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-Add index to foreign key columns. Postgres (and others) do not do this on the "source" side of a foreign key relation, which was what led to the slowness on large datasets. The full LDAP dataset ingestion now takes two minutes, which is not optimal yet but still a huge improvement over before when it basically never finished :)
@@ -1,5 +0,0 @@
---
-'@backstage/integration': patch
---
-
-Validate that integration config contains a valid host
@@ -1,20 +0,0 @@
---
-'@backstage/create-app': patch
---
-
-In the techdocs-backend plugin (`packages/backend/src/plugins/techdocs.ts`), create a publisher using
-
-```
-  const publisher = Publisher.fromConfig(config, logger, discovery);
-```
-
-instead of
-
-```
-  const publisher = new LocalPublish(logger, discovery);
-```
-
-An instance of `publisher` can either be a local filesystem publisher or a Google Cloud Storage publisher.
-
-Read more about the configs here https://backstage.io/docs/features/techdocs/configuration
-(You will also have to update `techdocs.storage.type` to `local` or `googleGcs`. And `techdocs.builder` to either `local` or `external`.)
@@ -1,5 +0,0 @@
---
-'@backstage/core-api': patch
---
-
-Use auth provider ID to create unique session storage keys for GitHub and SAML Auth.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Re-enable symlink resolution during bundling, and switch to using a resolve plugin for external linked packages.
@@ -1,9 +0,0 @@
---
-'@backstage/plugin-org': patch
---
-
-Display the new `profile` fields (`displayName`, `email`, and `picture`) for
-groups on the `GroupProfileCard`.
-
-This also resolves some cases where `profile` fields are missing for users or
-groups and for example falls back to displaying the entity name. Adds additional test data to the ACME Corp dataset.
@@ -1,7 +0,0 @@
---
-'@backstage/catalog-model': minor
-'@backstage/plugin-catalog-backend': minor
---
-
-Remove `implementsApis` from `Component` entities. Deprecation happened in [#3449](https://github.com/backstage/backstage/pull/3449).
-Use `providesApis` instead.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-scaffolder-backend': patch
---
-
-Added configuration schema for the commonly used properties
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-sentry': patch
---
-
-Added configuration schema for the commonly used properties
@@ -1,7 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-Support `profile` of groups including `displayName` and `email` in
-`MicrosoftGraphOrgReaderProcessor`. Importing `picture` doesn't work yet, as
-the Microsoft Graph API does not expose them correctly.