docs/releases/v1.29.0-next.0-changelog.md
Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.29.0-next.0
d3c39fc: Allow for the disabling of external routes through config, which was rendered impossible after the introduction of default targets.
app:
routes:
bindings:
# This has the effect of removing the button for registering new
# catalog entities in the scaffolder template list view
scaffolder.registerComponent: false
token for bitbucketCloud integrationEntityPicker as done earlier with MultiEntityPicker to fix performance issues with large data sets. VirtualizedListbox extracted into reusable component.MultiEntityPicker. Fixes performance issues with large data sets.bitbucketCloud autocomplete in RepoUrlPickerRepoUrlPicker would still require the owner field for azurecatalogFilter array on OwnedEntityPickerautocomplete extension point to provide additional autocomplete handlersesbuild to ^0.21.0.bitbucketCloud autocomplete in RepoUrlPickerMiddlewareFactory deprecation wrappingmockServices.winston and yn from the template of backend plugins;
msw to version 2.3.1 in the template of backend plugins;
starting with v1 and switching later to v2 is tedious and not straight forward; it's easier to start with v2;plugin-common in backstage-cli. Now, when executing backstage-cli new to create a new plugin-common package, the output message accurately reflects the action by displaying Creating common plugin package... instead of the previous, less accurate Creating backend plugin....esbuild to ^0.21.0.package.json should be of a unique name to avoid typescript resolution issues<Select> component with empty string as placeholder gave an errord3c39fc: Allow for the disabling of external routes through config, which was rendered impossible after the introduction of default targets.
app:
routes:
bindings:
# This has the effect of removing the button for registering new
# catalog entities in the scaffolder template list view
scaffolder.registerComponent: false
Updated dependencies
autocomplete handler to provide autocomplete options for RepoUrlPickercatalog.providers.gitlab.<your-org>.restrictUsersToGroup. Setting this to true will make Backstage only import users from the group defined in the group key, instead of all users in the organisation (self-hosted) or of the root group (SaaS). It will default to false, keeping the original implementation intact, when not explicitly set.97caf55: Creates a new module to make logging catalog errors simple. This module subscribes to catalog events and logs them.
See Backstage documentation for details on how to install and configure the plugin.
Updated dependencies
c307ef4: Added relationType property to EntityMembersListCard component that allows for display users related to a group via some other relationship aside from memberOf.
Also, as a side effect, the relationsType property has been deprecated in favor of a more accurately named relationAggregation property.
Updated dependencies
RepoUrlPicker would still require the owner field for azureautocomplete handler to provide autocomplete options for RepoUrlPickertargetBranch now fetch the default branch from Bitbucket repository.
This prevents from errors when no targetBranch is provided and the default repository branch is different from master, for example: main.RepoUrlPicker would still require the owner field for azureautocomplete extension point to provide additional autocomplete handlers