docs/releases/v1.11.0-next.1-changelog.md
AboutCard description sectionCatalogSearchResultListItem component is now a search result extension. This means that when rendered as a child of components that render search extensions, the result, rank, and highlight properties are optional. See the documentation for more details.ToolSearchResultListItem component is now a search result extension. This means that when rendered as a child of components that render search extensions, the result, rank, and highlight properties are optional. See the documentation for more details.scaffolderCatalogModule to catalogModuleTemplateKind in order to follow the new recommended naming patterns of backend system items. This is technically a breaking change but in an alpha export, so take care to change your imports if you have already migrated to the new backend system.esbuild to ^0.17.0.SearchModal component to use SearchResult extensions.SearchResult, SearchResultList and SearchResultGroup components to use extensions and default their props to optionally accept a query, when the query is not passed, the component tries to get it from the search context.4024b37449: TechInsightsApi interface now has getFactSchemas() method. TechInsightsClient now implements method getFactSchemas().
BREAKING FactSchema type moved from @backstage/plugin-tech-insights-node into @backstage/plugin-tech-insights-common
These changes are required if you were importing this type directly.
- import { FactSchema } from '@backstage/plugin-tech-insights-node';
+ import { FactSchema } from '@backstage/plugin-tech-insights-common';
TechDocsSearchResultListItem component is now a search result extension. This means that when rendered as a child of components that render search extensions, the result, rank, and highlight properties are optional. See the documentation for more details.@kubernetes/client-node to 0.18.1.register methods passed to createBackendPlugin and createBackendModule
now have dedicated BackendPluginRegistrationPoints and
BackendModuleRegistrationPoints arguments, respectively. This lets us make it
clear on a type level that it's not possible to pass in extension points as
dependencies to plugins (should only ever be done for modules). This has no
practical effect on code that was already well behaved.backstage-cli repo test command now sets a default Jest --workerIdleMemoryLimit of 1GB. If needed to ensure that tests are not run in band, --maxWorkers=2 is set as well. This is the recommended workaround for dealing with Jest workers leaking memory and eventually hitting the heap limit.esbuild to ^0.17.0.substrSearchPage template to use SearchResult extensions.substr@material-ui/core version ^4.12.2 like all other in-repo packagessubstrsubstrsearch.original_value column may leave some of the entities not updated. Add a migration script to trigger a reprocessing of the entities.2890f47517: This will add the ability to use Azure DevOps with multi project with a single value which is a new feature as previously this had to be done manually for each project that you wanted to add.
Right now you would have to fill in multiple values in the config to use multiple projects:
yourFirstProviderId: # identifies your dataset / provider independent of config changes
organization: myorg
project: 'firstProject' # this will match the firstProject project
repository: '*' # this will match all repos
path: /catalog-info.yaml
yourSecondProviderId: # identifies your dataset / provider independent of config changes
organization: myorg
project: 'secondProject' # this will match the secondProject project
repository: '*' # this will match all repos
path: /catalog-info.yaml
With this change you can actually have all projects available where your PAT determines which you have access to, so that includes multiple projects:
yourFirstProviderId: # identifies your dataset / provider independent of config changes
organization: myorg
project: '*' # this will match all projects where your PAT has access to
repository: '*' # this will match all repos
path: /catalog-info.yaml
85b04f659a: Internal refactor to not use deprecated substr
Updated dependencies
substrsubstrsubstrEventSubscriber from addIncrementalEntityProvider to hook up to EventsBackend@material-ui/core version ^4.12.2 like all other in-repo packagessubstr@material-ui/core version ^4.12.2 like all other in-repo packages@material-ui/core version ^4.12.2 like all other in-repo packagessubstrWelcomeTitle to not be the right size when passed to the title property of the <Header> component. A Storybook entry was also added for the WelcomeTitle@kubernetes/client-node to 0.18.1.@kubernetes/client-node to 0.18.1.@kubernetes/client-node to 0.18.1.@material-ui/core version ^4.12.2 like all other in-repo packages@material-ui/core version ^4.12.2 like all other in-repo packagessubstrscaffolder/next: bump react-jsonschema-form libraries to v5-stable@rjsf version 5 dependencies to beta.18scaffolder/next: bump react-jsonschema-form libraries to v5-stable@rjsf version 5 dependencies to beta.18substr4024b37449: TechInsightsApi interface now has getFactSchemas() method. TechInsightsClient now implements method getFactSchemas().
BREAKING FactSchema type moved from @backstage/plugin-tech-insights-node into @backstage/plugin-tech-insights-common
These changes are required if you were importing this type directly.
- import { FactSchema } from '@backstage/plugin-tech-insights-node';
+ import { FactSchema } from '@backstage/plugin-tech-insights-common';
Updated dependencies
4024b37449: TechInsightsApi interface now has getFactSchemas() method. TechInsightsClient now implements method getFactSchemas().
BREAKING FactSchema type moved from @backstage/plugin-tech-insights-node into @backstage/plugin-tech-insights-common
These changes are required if you were importing this type directly.
- import { FactSchema } from '@backstage/plugin-tech-insights-node';
+ import { FactSchema } from '@backstage/plugin-tech-insights-common';
Updated dependencies
4024b37449: TechInsightsApi interface now has getFactSchemas() method. TechInsightsClient now implements method getFactSchemas().
BREAKING FactSchema type moved from @backstage/plugin-tech-insights-node into @backstage/plugin-tech-insights-common
These changes are required if you were importing this type directly.
- import { FactSchema } from '@backstage/plugin-tech-insights-node';
+ import { FactSchema } from '@backstage/plugin-tech-insights-common';
Updated dependencies
@material-ui/core version ^4.12.2 like all other in-repo packages@material-ui/core version ^4.12.2 like all other in-repo packages