docs/releases/v1.9.0-next.1-changelog.md
de8a975911: Changed to use native AbortController and AbortSignal from Node.js, instead
of the one from node-abort-controller. This is possible now that the minimum
supported Node.js version of the project is 16.
Note that their interfaces are very slightly different, but typically not in a way that matters to consumers. If you see any typescript errors as a direct result from this, they are compatible with each other in the ways that we interact with them, and should be possible to type-cast across without ill effects.
SingleHostDiscovery so that it properly handles single-string backend.listen configurations such as :80.de8a975911: Changed to use native AbortController and AbortSignal from Node.js, instead
of the one from node-abort-controller. This is possible now that the minimum
supported Node.js version of the project is 16.
Note that their interfaces are very slightly different, but typically not in a way that matters to consumers. If you see any typescript errors as a direct result from this, they are compatible with each other in the ways that we interact with them, and should be possible to type-cast across without ill effects.
03843259b4: Api reference documentation improvements
@config annotation to describe related config keysc395abb5b2: The catalog no longer stops after the first processor validateEntityKind
method returns true when validating entity kind shapes. Instead, it continues
through all registered processors that have this method, and requires that at
least one of them returned true.
The old behavior of stopping early made it harder to extend existing core kinds
with additional fields, since the BuiltinKindsEntityProcessor is always
present at the top of the processing chain and ensures that your additional
validation code would never be run.
This is technically a breaking change, although it should not affect anybody under normal circumstances, except if you had problematic validation code that you were unaware that it was not being run. That code may now start to exhibit those problems.
If you need to disable this new behavior, CatalogBuilder as used in your
packages/backend/src/plugins/catalog.ts file now has a
useLegacySingleProcessorValidation() method to go back to the old behavior.
const builder = await CatalogBuilder.create(env);
+builder.useLegacySingleProcessorValidation();
Stitcher process to be more memory efficientsubstr into substring.de8a975911: Changed to use native AbortController and AbortSignal from Node.js, instead
of the one from node-abort-controller. This is possible now that the minimum
supported Node.js version of the project is 16.
Note that their interfaces are very slightly different, but typically not in a way that matters to consumers. If you see any typescript errors as a direct result from this, they are compatible with each other in the ways that we interact with them, and should be possible to type-cast across without ill effects.
Updated dependencies
typescript-json-schema to ^0.55.0.zen-observable to ^0.10.0.zen-observable to ^0.10.0.zen-observable to ^0.10.0.zen-observable to ^0.10.0.MockPluginProvider has been created. It will be handy in the cases when you use
__experimentalConfigure in your plugin. It is experimental and exported through @backstage/test-utils/alpha.zen-observable to ^0.10.0.zen-observable to ^0.10.0.HomePageBazaarInfoCard is now displaying title instead of name. Title is a string that doesn't have to be URL friendly.
The BazaarOverviewCard have the new property fullHeight. Link in BazaarOverviewCardis moved to header in card.title has replaced column name for BazaarProject in databaseAboutCard.zen-observable to ^0.10.0.BitbucketCloudEventRouter.fe93cce743: Added the githubCredentialsProvider property to the GithubLocationAnalyzerOptions to be able to override the GithubCredentialsProvider.
a0fd4af94a: Handle GitHub push events at the GithubEntityProvider by subscribing to the topic github.push.
Implements EventSubscriber to receive events for the topic github.push.
On github.push, the affected repository will be refreshed.
This includes adding new Location entities, refreshing existing ones,
and removing obsolete ones.
Please find more information at https://backstage.io/docs/integrations/github/discovery#installation-with-events-support
Updated dependencies
$refs in all kind of yaml documents, not only OpenAPI. This implicitly adds $ref resolving support for AsyncAPI specs. Thus, the openApiPlaceholderResolver has been renamed to jsonSchemaRefPlaceholderResolver.zen-observable to ^0.10.0.zen-observable to ^0.10.0.costInsights.engineerThreshold to allow users to control the threshold value for the 'negligible' change in costs.0f46ec304c: Add createGithubSignatureValidator(config) which can be used
to create a validator used at an ingress for topic github.
On top, there is a new githubWebhookEventsModule for the new backend plugin API
which auto-registers the HttpPostIngress for topic github incl. the validator.
Please find more information at https://github.com/backstage/backstage/tree/master/plugins/events-backend-module-github/README.md.
Updated dependencies
31fe8f256a: Add createGitlabTokenValidator(config) which can be used
to create a validator used at an ingress for topic gitlab.
On top, there is a new gitlabWebhookEventsModule for the new backend plugin API
which auto-registers the HttpPostIngress for topic gitlab incl. the validator.
Please find more information at https://github.com/backstage/backstage/tree/master/plugins/events-backend-module-gitlab/README.md.
Updated dependencies
4dec6f16be: Added new @backstage/plugin-explore-backend & @backstage/plugin-explore-common packages.
This deprecates the ExploreToolsConfig API (in @backstage/plugin-explore-react) which is replaced by the ExploreApi & ExploreClient. The list of ExploreTool data can now be provided on the backend by either using the supplied StaticExploreToolProvider or by implementing a custom ExploreToolProvider. See the explore-backend README for full details.
NOTE: Existing installations that have customized the ExploreToolConfig will continue to work through the new ExploreClient. However, existing data should be migrated over to new explore-backend plugin as ExploreToolConfig will be removed in the future.
BREAKING CHANGE: If you have previously installed the explore plugin, but not yet customized the ExploreToolConfig API in your packages/app, this will result in an empty list of tools.
Updated dependencies
4dec6f16be: Added new @backstage/plugin-explore-backend & @backstage/plugin-explore-common packages.
This deprecates the ExploreToolsConfig API (in @backstage/plugin-explore-react) which is replaced by the ExploreApi & ExploreClient. The list of ExploreTool data can now be provided on the backend by either using the supplied StaticExploreToolProvider or by implementing a custom ExploreToolProvider. See the explore-backend README for full details.
NOTE: Existing installations that have customized the ExploreToolConfig will continue to work through the new ExploreClient. However, existing data should be migrated over to new explore-backend plugin as ExploreToolConfig will be removed in the future.
BREAKING CHANGE: If you have previously installed the explore plugin, but not yet customized the ExploreToolConfig API in your packages/app, this will result in an empty list of tools.
Updated dependencies
4dec6f16be: Added new @backstage/plugin-explore-backend & @backstage/plugin-explore-common packages.
This deprecates the ExploreToolsConfig API (in @backstage/plugin-explore-react) which is replaced by the ExploreApi & ExploreClient. The list of ExploreTool data can now be provided on the backend by either using the supplied StaticExploreToolProvider or by implementing a custom ExploreToolProvider. See the explore-backend README for full details.
NOTE: Existing installations that have customized the ExploreToolConfig will continue to work through the new ExploreClient. However, existing data should be migrated over to new explore-backend plugin as ExploreToolConfig will be removed in the future.
BREAKING CHANGE: If you have previously installed the explore plugin, but not yet customized the ExploreToolConfig API in your packages/app, this will result in an empty list of tools.
4dec6f16be: Added new @backstage/plugin-explore-backend & @backstage/plugin-explore-common packages.
This deprecates the ExploreToolsConfig API (in @backstage/plugin-explore-react) which is replaced by the ExploreApi & ExploreClient. The list of ExploreTool data can now be provided on the backend by either using the supplied StaticExploreToolProvider or by implementing a custom ExploreToolProvider. See the explore-backend README for full details.
NOTE: Existing installations that have customized the ExploreToolConfig will continue to work through the new ExploreClient. However, existing data should be migrated over to new explore-backend plugin as ExploreToolConfig will be removed in the future.
BREAKING CHANGE: If you have previously installed the explore plugin, but not yet customized the ExploreToolConfig API in your packages/app, this will result in an empty list of tools.
Updated dependencies
kafkajs 2.2.3UserProfileCard and GroupProfileCard to not render links unless the showLinks prop is set. The primary component for rendering links are the EntityLinksCard from plugin-catalog.createRouter method.zen-observable to ^0.10.0.zen-observable to ^0.10.0.de8a975911: Changed to use native AbortController and AbortSignal from Node.js, instead
of the one from node-abort-controller. This is possible now that the minimum
supported Node.js version of the project is 16.
Note that their interfaces are very slightly different, but typically not in a way that matters to consumers. If you see any typescript errors as a direct result from this, they are compatible with each other in the ways that we interact with them, and should be possible to type-cast across without ill effects.
54c5836f7a: Use of TestPipeline.withSubject() is now deprecated. Instead, use the fromCollator, fromDecorator, or fromIndexer static methods to instantiate a test pipeline. You may also use the class' withCollator, withDecorator, and withIndexer instance methods to build test pipelines that consist of multiple test subjects.
Updated dependencies
zen-observable to ^0.10.0.0a61aab172: Bump dependency @azure/identity to next minor
37931c33ce: Upgrade to AWS SDK for Javascript v3
Techdocs support for AWS S3 now requires defining the AWS region to connect to.
If techdocs.publisher.awsS3.region is missing from the config, the AWS environment variable AWS_REGION will be used.
Updated dependencies
zen-observable to ^0.10.0.