docs/releases/v1.13.0-next.3-changelog.md
@backstage/cli-node package, which provides utilities for use across Backstage CLIs.AuthConnector interface now supports specifying a set of scopes when
refreshing a session. The DefaultAuthConnector implementation passes the
scope query parameter to the auth-backend plugin appropriately. The
RefreshingAuthSessionManager passes any scopes in its GetSessionRequest
appropriately.01cd4e25754: BREAKING: Removing Tabs component from core-components as it is neither used in the core Backstage app nor in the monorepo plugins. If you are using this component in your instance please consider replacing it with the Material UI Tabs component like the following:
- <Tabs
- tabs={[{
- icon: <AccessAlarmIcon />,
- content: <div>Label</div>,
- }]}
- />
+ <Tabs>
+ <Tab
+ label = "Label"
+ icon = { <AccessAlarmIcon /> }
+ />
+ </Tabs>
schema:openapi:generate to generate the Typescript file that @backstage/backend-openapi-utils needs for typing and schema:openapi:verify to verify that this file exists and matches your src/schema/openapi.yaml file.src/schema/openapi.yaml and uses ApiRouter type from @backstage/backend-openapi-utils to handle automatic types from the OpenAPI spec file.a49fb39df5a: Attempt to load entity owner names in the EntityOwnerPicker through the by-refs endpoint. If spec.profile.displayName or metadata.title are populated, we now attempt to show those before showing the humanizeEntityRef'd version.
BREAKING: EntityOwnerFilter now uses the full entity ref instead of the humanizeEntityRef. If you rely on EntityOwnerFilter.values or the queryParameters.owners of useEntityList, you will need to adjust your code like the following.
const { queryParameters: { owners } } = useEntityList();
// or
const { filter: { owners } } = useEntityList();
// Instead of,
if (owners.some(ref => ref === humanizeEntityRef(myEntity))) ...
// You'll need to use,
if (owners.some(ref => ref === stringifyEntityRef(myEntity))) ...
setSelectedOptions method. This was preventing updating list items when a query string was already present in the URL when loading the page.754be7c5106: refactor kubernetes error detection to make way for proposed solutions
BREAKING: DetectedError now appears once per Kubernetes resource per error instead of for all resources which have that error, namespace and name fields are now in sourceRef object message is now a string instead of a string[]. ErrorDetectableKind has been removed.
KubernetesBackendClient now requires a kubernetesAuthProvidersApi value to be provided. KubernetesApi interface now has a proxy method requirement.7a89555e73d: Lighthouse backend plugin can now use an authenticated catalog backend API.
tokenManager to the lighthouse createScheduler.Routers in backend packages. Developers can use the ApiRouter from this package in their packages to support a typed experience based on their OpenAPI specs. The ApiRouter supports request bodies, response bodies, query parameters and path parameters, as well as full path-based context of the above. This means no more guessing on an endpoint like req.post('/not-my-route', (req, res)=>{res.send(req.body.badparam)}). Typescript would catch /not-my-route, req.body.badparam, res.send(req.body.badparam).@backstage/cli-node package.@swc/helpers to ^0.5.0.475abd1dc3f: The microsoft (i.e. Azure) auth provider now supports negotiating tokens for
Azure resources besides Microsoft Graph (e.g. AKS, Virtual Machines, Machine
Learning Services, etc.). When the /frame/handler endpoint is called with an
authorization code for a non-Microsoft Graph scope, the user profile will not be
fetched. Similarly no user profile or photo data will be fetched by the backend
if the /refresh endpoint is called with the scope query parameter strictly
containing scopes for resources besides Microsoft Graph.
Furthermore, the offline_access scope will be requested by default, even when
it is not mentioned in the argument to getAccessToken. This means that any
Azure access token can be automatically refreshed, even if the user has not
signed in via Azure.
6a900951336: Add common identify resolvers for oidc auth provider.
a0ef1ec7349: Export Azure Easy Auth provider so it can actually be used.
Updated dependencies
xml2js from 0.4.23 to 0.5.03538d9ad2c4: Export DefaultEventBroker to allow decoupling of the catalog and events backends in the example-backend.
Please look at plugins/events-backend/README.md for the currently advised way to set up the event backend and catalog providers.
Updated dependencies
CatalogKindExploreContent component so that it is easy to show any component kinds in their own tab in the explore page.@rjsf/core-v5 to npm:@rjsf/[email protected].app.baseUrl.fetchApi instead of raw fetch in order to pass auth header if necessary.