docs/releases/v1.18.0-changelog.md
readDurationFromConfig function@types/node dependency9606ba0939e6: Deep visibility now also applies to values that are not covered by the configuration schema.
For example, given the following configuration schema:
// plugins/a/config.schema.ts
export interface Config {
/** @deepVisibility frontend */
a?: unknown;
}
// plugins/a/config.schema.ts
export interface Config {
a?: {
b?: string;
};
}
All values under a are now visible to the frontend, while previously only a and a/b would've been visible.
@types/node dependencyOAuth2Session type represents the underlying data. The expiresAt and backstageIdentity are now both optional, since that's what they are in practice. This is not considered a breaking change since it was effectively a bug in the modelling of the state that this type represents, and the type was not used in any other external contract.OAuth class which is used by all OAuth providers will now consider both the session expiration of both the Backstage identity as well as the upstream identity provider, and refresh the session with either of them is about to expire.@types/node dependencyexpiresAt field that may now be part of a BackstageIdentityResponse.@types/node dependency5f1a92b9f19f: Added AzureDevOpsCredentialsProvider to support multiple Azure DevOps organizations and deprecated AzureIntegrationConfig.credential and AzureIntegrationConfig.token in favour of AzureIntegrationConfig.credentials. You can now use specific credentials for different Azure DevOps (Server) organizations by specifying the organizations field on a credential:
integrations:
azure:
- host: dev.azure.com
credentials:
- organizations:
- my-org
- my-other-org
clientId: ${AZURE_CLIENT_ID}
clientSecret: ${AZURE_CLIENT_SECRET}
tenantId: ${AZURE_TENANT_ID}
- organizations:
- yet-another-org
personalAccessToken: ${PERSONAL_ACCESS_TOKEN}
See the Azure integration documentation for more information.
71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
@backstage/plugin-auth-backend-module-gitlab-provider module.authPlugin export for the new backend system. The plugin does not include any built-in auth providers, they must instead be added by installing additional modules, for example authModuleGoogleProvider from @backstage/plugin-auth-backend-module-google-provider.@backstage/plugin-auth-node instead.disableDefaultProviderFactories to createRouter.auth.identityTokenAlgorithm.@backstage/plugin-auth-backend that adds a GCP IAP auth provider.71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
@backstage/plugin-auth-backend that adds a GitHub auth provider.71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
@backstage/plugin-auth-backend that adds a GitLab auth provider.71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
@backstage/plugin-auth-backend that adds a Google auth provider.71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
@backstage/plugin-auth-backend that adds a oauth2 auth provider.8513cd7d00e3: Introduced a new system for building auth providers for @backstage/plugin-auth-backend, which both increases the amount of code re-use across providers, and also works better with the new backend system.
Many existing types have been moved from @backstage/plugin-auth-backend in order to avoid a direct dependency on the plugin from modules.
Auth provider integrations are now primarily implemented through a pattern of creating "authenticators", which are in turn specific to each kind of integrations. Initially there are two types: createOAuthAuthenticator and createProxyAuthenticator. These come paired with functions that let you create the corresponding route handlers, createOAuthRouteHandlers and createProxyAuthRouteHandlers, as well as provider factories, createOAuthProviderFactory and createProxyAuthProviderFactory. This new authenticator pattern allows the sign-in logic to be separated from the auth integration logic, allowing it to be completely re-used across all providers of the same kind.
The new provider factories also implement a new declarative way to configure sign-in resolvers, rather than configuration through code. Sign-in resolvers can now be configured through the resolvers configuration key, where the first resolver that provides an identity will be used, for example:
auth:
providers:
google:
development:
clientId: ...
clientSecret: ...
signIn:
resolvers:
- resolver: emailMatchingUserEntityAnnotation
- resolver: emailLocalPartMatchingUserEntityName
These configurable resolvers are created with a new createSignInResolverFactory function, which creates a sign-in resolver factory, optionally with an options schema that will be used both when configuring the sign-in resolver through configuration and code.
The internal helpers from @backstage/plugin-auth-backend that were used to implement auth providers using passport strategies have now also been made available as public API, through PassportHelpers and PassportOAuthAuthenticatorHelper.
BackstageIdentityResponse interface now has an optional expiresInSeconds field that can be used to signal session expiration. The prepareBackstageIdentityResponse utility will now also read the expiration from the provided token, and include it in the response.71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
@types/node dependency71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
backstage.io/techdocs-entity this ref allows you to reference another entity for its TechDocs. This allows you have a single TechDoc for all items in a system, for example you might have a frontend and a backend in the same repo. This would allow you to have TechDocs build under a System entity while referencing the system e.g.: backstage.io/techdocs-entity: system:default/example that will show the systems docs in both the TechDocs button and the TechDocs tab without needing to do duplicate builds and filling the TechDocs page with garbage.Has<kind>Cards.EntitySwitch was preventing the display of entity errors.catalog.processingInterval key.dev.azure.com/project-repo in AnnotateScmSlugEntityProcessor to find the project and repo information for the repos that contains dev.azure.com in the url149361e81622: Fix to the limit parameter on entity queries.
1fd2109739c1: Changed the processing loop task pipeline implementation from recursive to iterative
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
0f8a97777489: Update OpenAPI schema to relax the encoding validation of all request parameters.
0198aa596fd9: Fixed a link to the frontend Backstage plugin that had pointed to itself.
2d32d8a611e3: Fixed validation of the fullTextFilterFields query parameter.
acffa17027b6: Added some examples to the catalog OpenAPI definition
45947d3b2759: Fixes an issue where order was not a recognized parameter for the /entities endpoint.
41d1b2d628ea: Fix OpenAPI schema for the facets endpoint
618257f3e413: Fix issue with catalogFileName not being a required property for /analyze-location
cfc3ca6ce060: Changes needed to support MySQL
814feeed7343: Update to handle invalid luxon values
Updated dependencies
catalogModuleGithubOrgEntityProvider for the new backend system71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
3d63e60f3c36: Internal restructure to avoid circular imports
96353bb7cb4a: Properly support custom userTransformer returning undefined in GithubMultiOrgEntityProvider
3c44761b9191: Allow github user and team transforms to return any Entity
Updated dependencies
3d73bafd85c9: Fix Gitlab.com user ingestion by scoping GitlabOrgDiscoveryEntityProvider to a group.
BREAKING The group parameter is now required Gitlab.com Org Data integrations and the backend will fail to start without this option configured.
catalog:
providers:
gitlab:
yourProviderId:
host: gitlab.com
orgEnabled: true
+ group: org/teams
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
ScaffolderEntitiesProcessor and catalogModuleTemplateKind.71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
PreparePullRequestFormProps, because of an update to react-hook-form.71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
DevTools plugin71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
0ad36158d980: Integrators can now bring their own auth strategies through the use of the addAuthStrategy method on KubernetesBuilder.
BREAKING on the slight chance you were using the setAuthTranslatorMap method on KubernetesBuilder, it has been removed along with the entire KubernetesAuthTranslator interface. This notion has been replaced with the more focused concept of an AuthenticationStrategy. Converting a translator to a strategy should not be especially difficult.
ccf00accb408: Add AWS Annotations to Kubernetes Cluster Resource
72390ab2670d: Handle Proxy WS upgrade manually for WS handshakes
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
024b2b66a332: Fixed a bug where requests to the proxy endpoint would fail for clusters with caFile configured
a8a614ba0d07: Minor package.json update.
47ea122590f5: fix "undefined" kind for custom resources
Updated dependencies
71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
createRouterFromConfig or using the plugin for the new backend system the linguist.useSourceLocation configuration is now optional.@types/react to be a regular dependency71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
permissionModuleAllowAllPolicy71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
OwnedEntityPicker by converting deprecated ui:options input to catalogFilter.@types/node dependency@rjsf/utils to 5.13.0.
Updated dependency @rjsf/core-v5 to npm:@rjsf/[email protected].
Updated dependency @rjsf/material-ui-v5 to npm:@rjsf/[email protected].
Updated dependency @rjsf/validator-ajv8 to 5.13.0.b5f239b50bcf: Improved the parseEntityRef Scaffolder filter by introducing the ability for users to provide default kind and/or namespace values. The filter now takes
2 arguments, similarly to the original parseEntityRef.
d5313ede3529: DEPRECATION: Deprecated ScaffolderEntitiesProcessor, which should now instead be imported from @backstage/plugin-catalog-backend-module-scaffolder-entity-model.
catalogModuleTemplateKind was also moved to that package and renamed to catalogModuleScaffolderEntityModel, without any deprecation since it was an alpha export.
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
a4989552d828: Add examples for publish:github and publish:gitlab scaffolder actions.
ded27b83ead2: Add examples for publish:bitbucket scaffolder actions.
5f1a92b9f19f: Use DefaultAzureDevOpsCredentialsProvider to retrieve credentials for Azure DevOps.
fb57a4694fc6: Fixed the plugin and module ID of the alpha catalogModuleTemplateKind export.
f3c0b95e3ef1: Add examples for github:actions:dispatch scaffolder actions.
cfc3ca6ce060: Changes needed to support MySQL
814feeed7343: Update to handle invalid luxon values
Updated dependencies
b78f570f44d3: The SearchPage component can now be configured via app-config.yaml with default query parameters to define how it behaves when it is first loaded or reset. Check out the following example:
search:
query:
pageLimit: 50
Acceptable values for pageLimit are 10, 25, 50 or 100.
@types/node dependencyb78f570f44d3: The SearchPage component can now be configured via app-config.yaml with default query parameters to define how it behaves when it is first loaded or reset. Check out the following example:
search:
query:
pageLimit: 50
Acceptable values for pageLimit are 10, 25, 50 or 100.
backstage.io/techdocs-entity this ref allows you to reference another entity for its TechDocs. This allows you have a single TechDoc for all items in a system, for example you might have a frontend and a backend in the same repo. This would allow you to have TechDocs build under a System entity while referencing the system e.g.: backstage.io/techdocs-entity: system:default/example that will show the systems docs in both the TechDocs button and the TechDocs tab without needing to do duplicate builds and filling the TechDocs page with garbage.@types/node dependencytechdocs.publisher.azureBlobStorage.connectionString app-config setting, which can be leveraged for improved Azurite support.60af8017dd84: Expand techdocs.publisher.type with googleGcs,awsS3,azureBlobStorage and openStackSwift
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
a8a614ba0d07: Minor package.json update.
Updated dependencies
@types/node dependencytechdocs.publisher.azureBlobStorage.connectionString app-config setting, which can be leveraged for improved Azurite support.71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
71114ac50e02: BREAKING: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
@types/node dependency'cli' packages are ignored. However, the "backstage" field is still required in package.json.backend.add(import('my-plugin')).@backstage/backend-app-api that would result in Cannot read properties of undefined (reading 'redacter').DefaultAzureDevOpsCredentialsProvider to retrieve credentials for Azure DevOps.readDurationFromConfig from the config packageServiceFactoryTester.startTestBackend({ features: [import('my-plugin')] }).mockService to also include mocked variants, for example mockServices.lifecycle.mock(). The returned mocked implementation will have a factory property which is a service factory for itself. You can also pass a partial implementation of the service to the mock function to use a mock implementation of specific methods.--inspect and --inspect-brk command. You can now set the ip and port of the inspect and inspectBrk by adding for example --inspect=0.0.0.0:9229new command.repo fix command that fixes auto-fixable problems in all packages. Initially the command fixes package export declarations, as well as marks all non-bundled frontend packages as side-effect free. Marking packages as free of side-effects can drastically reduce the Webpack bundle size..tsx files.@types/node dependencyrun-script-webpack-plugin to ^0.2.0.version:bump it will now log duplicates instead of throwing an errordev/index entry point for backend plugins and modules."sideEffects": false to package.json in frontend package templates. This can be added to existing packages using the new yarn fix command.package fix command that was used to automatically add dependencies to package.json, but has since been replaced by the no-undeclared-imports rule from @backstage/eslint-plugin.StructuredMetadataTable to crash in case metadata contained null values.<AutoLogout> component which introduces an optional automatic logout mechanism on user inactivityclassnames update@types/node dependencyrc-progress to 3.5.1.05508a9757d2: Updated the backend template to no longer create duplicate connection pools to plugins that use the task scheduler.
To apply this change in your own repository, perform the following small update:
// in packages/backend/src/index.ts
- const taskScheduler = TaskScheduler.fromConfig(config);
+ const taskScheduler = TaskScheduler.fromConfig(config, { databaseManager });
a4c08241ad92: Switched the template to use TypeScript 5.2 by default.
f8c8e8de37b6: Bumped create-app version.
fc1a38bc5723: Bumped create-app version.
4606e005df5d: Added a fix scripts that calls the new backstage-cli repo fix command.
To apply this change to an existing app, make the following change to your root package.json:
"test": "backstage-cli repo test",
"test:all": "backstage-cli repo test --coverage",
+ "fix": "backstage-cli repo fix",
"lint": "backstage-cli repo lint --since origin/master",
612594022245: Add a notification when yarn install is taking a long time.
8db70ecbb325: Updated Dockerfile to include apt-get update when installing the SQLite dependency
8cec7664e146: Removed @types/node dependency
Updated dependencies
@types/node dependency@types/react to be a regular dependency@types/node dependency@types/node dependencygenerate-catalog-info command now uses the first listed CODEOWNER as Component owner when initially
creating the catalog-info.yaml file. It continues to allow any one listed CODEOWNER when updating
entity metadata.generate-catalog-info command that could cause metadata.description values to be overwritten by package.json description values only because unrelated attributes were being changed.generate-catalog-info command that could cause the --dry-run flag to indicate changes to files when no changes would actually be made if the command were run without the flag.--ci flag to the generate-catalog-info command. This flag behaves similarly to the same flag on api-reports: if catalog-info.yaml files would have been added or modified, then the process exits with status code 1, and instructions are printed.7032c214f3b4: Add pod exec terminal to Container Card
406b786a2a2c: Mark package as being free of side effects, allowing more optimized Webpack builds.
8cec7664e146: Removed @types/node dependency
b5fbddc15dca: Add a new MockTranslationApi as an /alpha export.
9ceb6195275a: Add support for React Testing Library 13+, and thus React 18.
We're exposing an additional option to the render* methods to enable the legacyRoot flow.
Updated dependencies
@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/node dependency@types/node dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/node dependency@types/react to be a regular dependency@types/react to be a regular dependency@types/node dependency71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
cfc3ca6ce060: Changes needed to support MySQL
Updated dependencies
@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/react to be a regular dependency@types/node dependency71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
94f96508491d: Improve consistency of results from the AzureDevOpsEntityProvider.
5f1a92b9f19f: Use DefaultAzureDevOpsCredentialsProvider to retrieve credentials for Azure DevOps.
044b4f2fb1e3: Remove duplications from Azure search before committing the new locations to the catalog.
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
201f07c27f1e: Fix GKE endpoint parsing
Endpoint is an IP, not url. It is always https on default (443) port ref: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#Cluster
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
EntityAutocompletePicker component.@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/node dependency3f1367b956c6: Added support for LCOV coverage reports
df005d9932fb: Add text body parser for LCOV reports
91ccb56fb418: Replace express-xml-bodyparser with body-parser-xml.
express-xml-bodyparser was last updated 8 years ago
and currently depends on a version of xml2js which
contains a vulnerability.
This change will swap it out in favor of body-parser-xml
which is more maintained and depends on a more recent xml2js
version without the vulnerability.
33e606a797ef: Include auth token when fetching entity
d409ed988aed: Correct the line hits calculation for Cobertura reports
cfc3ca6ce060: Changes needed to support MySQL
Updated dependencies
@types/react to be a regular dependency@types/node dependencyrc-progress to 3.5.1.@types/react to be a regular dependency@types/node dependency@types/node dependency@types/pluralize to ^0.0.30.DevTools plugin@types/node dependencyDevTools plugin@types/react to be a regular dependency@types/node dependency@types/node dependency@types/react to be a regular dependency@types/node dependency71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
@types/node dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/node dependency@types/react to be a regular dependency/alpha.@types/node dependency@types/react to be a regular dependency@types/node dependency@types/node dependency@rjsf/utils to 5.13.0.
Updated dependency @rjsf/core-v5 to npm:@rjsf/[email protected].
Updated dependency @rjsf/material-ui-v5 to npm:@rjsf/[email protected].
Updated dependency @rjsf/validator-ajv8 to 5.13.0.@types/react to be a regular dependency@types/node dependency@rjsf/utils to 5.13.0.
Updated dependency @rjsf/core-v5 to npm:@rjsf/[email protected].
Updated dependency @rjsf/material-ui-v5 to npm:@rjsf/[email protected].
Updated dependency @rjsf/validator-ajv8 to 5.13.0.@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependencyauth field in the body of requests to the retrieveObjectsByServiceId endpoint. Now any JSON object is allowed, which should make it easier for integrators to write their own custom auth strategies for Kubernetes.TextEncoder in order not to break tests.@types/node dependencyauth field in the body of requests to the retrieveObjectsByServiceId endpoint. Now any JSON object is allowed, which should make it easier for integrators to write their own custom auth strategies for Kubernetes.@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/node dependency@types/react to be a regular dependency@types/node dependency71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
a8a614ba0d07: Minor package.json update.
84ad6fccd4d5: Moved permissionModuleAllowAllPolicy to @backstage/plugin-permission-backend-module-allow-all-policy
Updated dependencies
package.json update.@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@rjsf/utils to 5.13.0.
Updated dependency @rjsf/core-v5 to npm:@rjsf/[email protected].
Updated dependency @rjsf/material-ui-v5 to npm:@rjsf/[email protected].
Updated dependency @rjsf/validator-ajv8 to 5.13.0.use-immer to ^0.9.0.71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
4ccf9204bc95: Added indexerBatchSize option to be able to control the size of the batches being indexed. Also added a debug log entry to list out all the entities in the batch
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
71114ac50e02: The export for the new backend system has been moved to be the default export.
For example, if you are currently importing the plugin using the following pattern:
import { examplePlugin } from '@backstage/plugin-example-backend';
backend.add(examplePlugin);
It should be migrated to this:
backend.add(import('@backstage/plugin-example-backend'));
Updated dependencies
@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependency@types/react to be a regular dependency@types/node dependencyrc-progress to 3.5.1.@types/react to be a regular dependency@types/node dependency@types/node dependency@types/node dependency@types/node dependency@types/react to be a regular dependency@types/node dependencyRadarTimeline text formatting.@types/node dependency@types/react to be a regular dependency@types/node dependency@types/node dependency@types/react to be a regular dependency@types/node dependencyvault.io/secrets-enginevault.io/secrets-engine@types/react to be a regular dependency@types/node dependency