Merge branch 'master' into rugvip/depr

This commit is contained in:
Patrik Oldsberg
2022-01-17 13:07:16 +01:00
committed by GitHub
106 changed files with 2791 additions and 1360 deletions
+5
View File
@@ -0,0 +1,5 @@
---
'@backstage/plugin-permission-react': minor
---
**BREAKING**: Update to use renamed request and response types from @backstage/plugin-permission-common.
+6
View File
@@ -0,0 +1,6 @@
---
'@backstage/core-components': patch
'@backstage/plugin-api-docs': patch
---
chore(deps): bump `react-syntax-highligher` and `swagger-ui-react`
+5
View File
@@ -0,0 +1,5 @@
---
'@backstage/plugin-permission-backend': minor
---
**BREAKING**: Wrap batched requests and responses to /authorize in an envelope object. The latest version of the PermissionClient in @backstage/permission-common uses the new format - as long as the permission-backend is consumed using this client, no other changes are necessary.
+7
View File
@@ -0,0 +1,7 @@
---
'@backstage/plugin-permission-common': minor
---
**BREAKING**: Authorize API request and response types have been updated. The existing `AuthorizeRequest` and `AuthorizeResponse` types now match the entire request and response objects for the /authorize endpoint, and new types `AuthorizeQuery` and `AuthorizeDecision` have been introduced for individual items in the request and response batches respectively.
**BREAKING**: PermissionClient has been updated to use the new request and response format in the latest version of @backstage/permission-backend.
+13
View File
@@ -0,0 +1,13 @@
---
'@backstage/plugin-org': patch
---
For the component `EntityMembersListCard` you can now specify the pageSize. For example:
```tsx
<Grid item xs={12}>
<EntityMembersListCard pageSize={100} />
</Grid>
```
If left empty it will by default use 50.
+10
View File
@@ -0,0 +1,10 @@
---
'@backstage/plugin-catalog': patch
'@backstage/plugin-cost-insights': patch
'@backstage/plugin-shortcuts': patch
'@backstage/plugin-user-settings': patch
---
**@backstage/plugin-user-settings:** Hide Header on mobile screens to improve the UI & give more space to the content. Furthermore, the "Pin Sidebar" setting is removed on mobile screens, as the mobile sidebar is always pinned to the bottom.
**Other plugins:** Smaller style adjustments across plugins to improve the UI on mobile devices.
+11
View File
@@ -0,0 +1,11 @@
---
'@backstage/core-components': patch
---
The `Bar` component will now render a `MobileSidebar` instead of the current sidebar on smaller screens. The state of the `MobileSidebar` will be treated as always open.
---
**Add MobileSidebar:** A navigation component, which sticks to the bottom. If there is no content in the Sidebar, it won't be rendered. If there are `children ` in the `Sidebar`, but no `SidebarGroup`s as `children`, it will render all `children` into a default overlay menu, which can be displayed by clicking a menu item. If `SidebarGroup`s are provided, it will render them in the bottom navigation. Additionally, a `MobileSidebarContext`, which wraps the component, will save the selected menu item.
**Add SidebarGroup:** Groups items of the `Sidebar` together. On bigger screens, this won't have any effect at the moment. On smaller screens, it will render a given icon into the `MobileSidebar`. If a route is provided, clicking the `SidebarGroup` in the `MobileSidebar` will route to the page. If no route is provided, it will add a provided icon to the `MobileSidebar` as a menu item & will render the children into an overlay menu, which will be displayed when the menu item is clicked.
+5
View File
@@ -0,0 +1,5 @@
---
'@backstage/plugin-catalog-backend': patch
---
Now when entities are deleted, the parent entity state is updated such that it will "heal" accidental deletes on the next refresh round.
+5
View File
@@ -0,0 +1,5 @@
---
'@backstage/plugin-org': patch
---
Fixed typo in `MembersListCard` component
+22
View File
@@ -0,0 +1,22 @@
---
'@backstage/backend-common': patch
'@backstage/config': patch
'@backstage/config-loader': patch
'@backstage/plugin-app-backend': patch
---
Loading of app configurations now reference the `@deprecated` construct from
JSDoc to determine if a property in-use has been deprecated. Users are notified
of deprecated keys in the format:
```txt
The configuration key 'catalog.processors.githubOrg' of app-config.yaml is deprecated and may be removed soon. Configure a GitHub integration instead.
```
When the `withDeprecatedKeys` option is set to `true` in the `process` method
of `loadConfigSchema`, the user will be notified that deprecated keys have been
identified in their app configuration.
The `backend-common` and `plugin-app-backend` packages have been updated to set
`withDeprecatedKeys` to true so that users are notified of deprecated settings
by default.
+12
View File
@@ -0,0 +1,12 @@
---
'@backstage/cli': patch
---
Introduce `--deprecated` option to `config:check` to log all deprecated app configuration properties
```sh
$ yarn backstage-cli config:check --lax --deprecated
config:check --lax --deprecated
Loaded config from app-config.yaml
The configuration key 'catalog.processors.githubOrg' of app-config.yaml is deprecated and may be removed soon. Configure a GitHub integration instead.
```
+6
View File
@@ -0,0 +1,6 @@
---
'@backstage/plugin-permission-node': minor
---
**BREAKING**: `PolicyAuthorizeRequest` type has been renamed to `PolicyAuthorizeQuery`.
**BREAKING**: Update to use renamed request and response types from @backstage/plugin-permission-common.
+128
View File
@@ -0,0 +1,128 @@
{
"mode": "pre",
"tag": "next",
"initialVersions": {
"example-app": "0.2.60",
"@backstage/app-defaults": "0.1.4",
"example-backend": "0.2.60",
"@backstage/backend-common": "0.10.3",
"@backstage/backend-tasks": "0.1.3",
"@backstage/backend-test-utils": "0.1.13",
"@backstage/catalog-client": "0.5.4",
"@backstage/catalog-model": "0.9.9",
"@backstage/cli": "0.11.0",
"@backstage/cli-common": "0.1.6",
"@backstage/codemods": "0.1.29",
"@backstage/config": "0.1.12",
"@backstage/config-loader": "0.9.2",
"@backstage/core-app-api": "0.4.0",
"@backstage/core-components": "0.8.4",
"@backstage/core-plugin-api": "0.5.0",
"@backstage/create-app": "0.4.12",
"@backstage/dev-utils": "0.2.17",
"e2e-test": "0.2.0",
"embedded-techdocs-app": "0.2.59",
"@backstage/errors": "0.2.0",
"@backstage/integration": "0.7.1",
"@backstage/integration-react": "0.1.18",
"@backstage/search-common": "0.2.1",
"storybook": "0.2.1",
"@techdocs/cli": "0.8.10",
"@backstage/techdocs-common": "0.11.3",
"@backstage/test-utils": "0.2.2",
"@backstage/theme": "0.2.14",
"@backstage/types": "0.1.1",
"@backstage/version-bridge": "0.1.1",
"@backstage/plugin-airbrake": "0.1.0",
"@backstage/plugin-allure": "0.1.11",
"@backstage/plugin-analytics-module-ga": "0.1.6",
"@backstage/plugin-apache-airflow": "0.1.3",
"@backstage/plugin-api-docs": "0.6.22",
"@backstage/plugin-app-backend": "0.3.21",
"@backstage/plugin-auth-backend": "0.6.2",
"@backstage/plugin-azure-devops": "0.1.10",
"@backstage/plugin-azure-devops-backend": "0.3.0",
"@backstage/plugin-azure-devops-common": "0.2.0",
"@backstage/plugin-badges": "0.2.19",
"@backstage/plugin-badges-backend": "0.1.15",
"@backstage/plugin-bazaar": "0.1.9",
"@backstage/plugin-bazaar-backend": "0.1.6",
"@backstage/plugin-bitrise": "0.1.22",
"@backstage/plugin-catalog": "0.7.8",
"@backstage/plugin-catalog-backend": "0.20.0",
"@backstage/plugin-catalog-backend-module-ldap": "0.3.9",
"@backstage/plugin-catalog-backend-module-msgraph": "0.2.12",
"@backstage/plugin-catalog-common": "0.1.0",
"@backstage/plugin-catalog-graph": "0.2.6",
"@backstage/plugin-catalog-graphql": "0.3.0",
"@backstage/plugin-catalog-import": "0.7.9",
"@backstage/plugin-catalog-react": "0.6.11",
"@backstage/plugin-circleci": "0.2.34",
"@backstage/plugin-cloudbuild": "0.2.32",
"@backstage/plugin-code-coverage": "0.1.22",
"@backstage/plugin-code-coverage-backend": "0.1.19",
"@backstage/plugin-config-schema": "0.1.18",
"@backstage/plugin-cost-insights": "0.11.17",
"@backstage/plugin-explore": "0.3.25",
"@backstage/plugin-explore-react": "0.0.10",
"@backstage/plugin-firehydrant": "0.1.12",
"@backstage/plugin-fossa": "0.2.27",
"@backstage/plugin-gcp-projects": "0.3.13",
"@backstage/plugin-git-release-manager": "0.3.8",
"@backstage/plugin-github-actions": "0.4.31",
"@backstage/plugin-github-deployments": "0.1.26",
"@backstage/plugin-gitops-profiles": "0.3.13",
"@backstage/plugin-gocd": "0.1.1",
"@backstage/plugin-graphiql": "0.2.27",
"@backstage/plugin-graphql-backend": "0.1.11",
"@backstage/plugin-home": "0.4.10",
"@backstage/plugin-ilert": "0.1.21",
"@backstage/plugin-jenkins": "0.5.17",
"@backstage/plugin-jenkins-backend": "0.1.10",
"@backstage/plugin-kafka": "0.2.25",
"@backstage/plugin-kafka-backend": "0.2.14",
"@backstage/plugin-kubernetes": "0.5.4",
"@backstage/plugin-kubernetes-backend": "0.4.3",
"@backstage/plugin-kubernetes-common": "0.2.1",
"@backstage/plugin-lighthouse": "0.2.34",
"@backstage/plugin-newrelic": "0.3.13",
"@backstage/plugin-newrelic-dashboard": "0.1.3",
"@backstage/plugin-org": "0.3.34",
"@backstage/plugin-pagerduty": "0.3.22",
"@backstage/plugin-permission-backend": "0.3.0",
"@backstage/plugin-permission-common": "0.3.1",
"@backstage/plugin-permission-node": "0.3.0",
"@backstage/plugin-permission-react": "0.2.2",
"@backstage/plugin-proxy-backend": "0.2.15",
"@backstage/plugin-rollbar": "0.3.23",
"@backstage/plugin-rollbar-backend": "0.1.18",
"@backstage/plugin-scaffolder": "0.11.18",
"@backstage/plugin-scaffolder-backend": "0.15.20",
"@backstage/plugin-scaffolder-backend-module-cookiecutter": "0.1.8",
"@backstage/plugin-scaffolder-backend-module-rails": "0.2.3",
"@backstage/plugin-scaffolder-backend-module-yeoman": "0.1.2",
"@backstage/plugin-scaffolder-common": "0.1.2",
"@backstage/plugin-search": "0.5.5",
"@backstage/plugin-search-backend": "0.3.0",
"@backstage/plugin-search-backend-module-elasticsearch": "0.0.7",
"@backstage/plugin-search-backend-module-pg": "0.2.3",
"@backstage/plugin-search-backend-node": "0.4.4",
"@backstage/plugin-sentry": "0.3.33",
"@backstage/plugin-shortcuts": "0.1.19",
"@backstage/plugin-sonarqube": "0.2.12",
"@backstage/plugin-splunk-on-call": "0.3.19",
"@backstage/plugin-tech-insights": "0.1.5",
"@backstage/plugin-tech-insights-backend": "0.1.5",
"@backstage/plugin-tech-insights-backend-module-jsonfc": "0.1.5",
"@backstage/plugin-tech-insights-common": "0.2.1",
"@backstage/plugin-tech-insights-node": "0.1.2",
"@backstage/plugin-tech-radar": "0.5.2",
"@backstage/plugin-techdocs": "0.12.14",
"@backstage/plugin-techdocs-backend": "0.12.3",
"@backstage/plugin-todo": "0.1.18",
"@backstage/plugin-todo-backend": "0.1.18",
"@backstage/plugin-user-settings": "0.3.16",
"@backstage/plugin-xcmetrics": "0.2.15"
},
"changesets": []
}
+5
View File
@@ -0,0 +1,5 @@
---
'@backstage/plugin-techdocs': patch
---
use lighter color for block quotes and horizontal rulers
+5
View File
@@ -0,0 +1,5 @@
---
'@backstage/plugin-api-docs': patch
---
Using an explicitly empty string for the url argument ensures that the swagger UI does not run into undefined errors.
+51
View File
@@ -0,0 +1,51 @@
---
'@backstage/create-app': patch
---
You can now add `SidebarGroup`s to the current `Sidebar`. This will not affect how the current sidebar is displayed, but allows a customization on how the `MobileSidebar` on smaller screens will look like. A `SidebarGroup` will be displayed with the given icon in the `MobileSidebar`.
A `SidebarGroup` can either link to an existing page (e.g. `/search` or `/settings`) or wrap components, which will be displayed in a full-screen overlay menu (e.g. `Menu`).
```diff
<Sidebar>
<SidebarLogo />
+ <SidebarGroup label="Search" icon={<SearchIcon />} to="/search">
<SidebarSearchModal />
+ </SidebarGroup>
<SidebarDivider />
+ <SidebarGroup label="Menu" icon={<MenuIcon />}>
<SidebarItem icon={HomeIcon} to="catalog" text="Home" />
<SidebarItem icon={CreateComponentIcon} to="create" text="Create..." />
<SidebarDivider />
<SidebarScrollWrapper>
<SidebarItem icon={MapIcon} to="tech-radar" text="Tech Radar" />
</SidebarScrollWrapper>
+ </SidebarGroup>
<SidebarSpace />
<SidebarDivider />
+ <SidebarGroup
+ label="Settings"
+ icon={<UserSettingsSignInAvatar />}
+ to="/settings"
+ >
<SidebarSettings />
+ </SidebarGroup>
</Sidebar>
```
Additionally, you can order the groups differently in the `MobileSidebar` than in the usual `Sidebar` simply by giving a group a priority. The groups will be displayed in descending order from left to right.
```diff
<SidebarGroup
label="Settings"
icon={<UserSettingsSignInAvatar />}
to="/settings"
+ priority={1}
>
<SidebarSettings />
</SidebarGroup>
```
If you decide against adding `SidebarGroup`s to your `Sidebar` the `MobileSidebar` will contain one default menu item, which will open a full-screen overlay menu displaying all the content of the current `Sidebar`.
More information on the `SidebarGroup` & the `MobileSidebar` component can be found in the changeset for the `core-components`.