docs/releases/v1.44.0-changelog.md
Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.44.0
9b81a90: BREAKING - Removing the deprecated types and interfaces, there's no replacement for these types, and hopefully not currently used as they offer no value with the plugin being on the new backend system and no way to consume them.
Affected types: CreateWorkerOptions, CurrentClaimedTask, DatabaseTaskStore, DatabaseTaskStoreOptions, TaskManager, TaskStore, TaskStoreCreateTaskOptions, TaskStoreCreateTaskResult, TaskStoreEmitOptions, TaskStoreListEventsOptions, TaskStoreRecoverTaskOptions, TaskStoreShutDownTaskOptions, TaskWorker and TemplateActionRegistry.
f222a2e: Fixed distributed actions not being visible in the scaffolder template actions.
Depending on the plugin startup order, some of the distributed actions were not being registered correctly, causing them to be invisible in the scaffolder template actions list.
Updated dependencies
2d3e2b2: implement support for direct url for AzureBlobStorageUrlReader search function
8b91238: Adds support for configuring server-level HTTP options through the
app-config.yaml file under the backend.server key. Supported options
include headersTimeout, keepAliveTimeout, requestTimeout, timeout,
maxHeadersCount, and maxRequestsPerSocket.
These are passed directly to the underlying Node.js HTTP server. If omitted, Node.js defaults are used.
8495b18: Add a new externalTokenHandlersServiceRef to allow custom external token validations
extensions option from renderInTestApp. If you need to pass extensions to the test app, use the new renderTestApp utility instead.mkdocs watch feature.865bce8: BREAKING: Removed the built-in CssBaseline from UnifiedThemeProvider. If your Backstage instance looks broken after this update, you likely forgot to add our new Backstage UI global CSS. To do that, please import @backstage/ui/css/styles.css in packages/app/src/index.tsx:
import '@backstage/ui/css/styles.css';
This change also removes the noCssBaseline prop, which became redundant.
UnifiedThemeProvider now coordinates theme attributes on the document body in case multiple theme providers are rendered.PasswordField component. As part of this change, the password and search types have been removed from TextField.virtualized, maxWidth and maxHeight props to Menu, MenuListBox, MenuAutocomplete and MenuAutocompleteListBox to allow for virtalization of long lists inside menus.<Box />, <Container />, <Flex />, and <Grid /> components, ensuring they are correctly applied to the rendered elements.b8a381e: Remove explicit dependency on isomorphic-form-data.
This explicit dependency was added to address an issue in the
dependency swagger-ui-react. That issue has since been resolved,
and isomorphic-form-data no longer needs to be declared.
Additionally, this changeset updates the swagger-ui-react dependency to version 5.19.0 or higher, which includes
compatibility with the latest versions of
the OpenAPI specification.
/mui-to-bui that converts an existing MUI v5 theme into Backstage UI (BUI) CSS variables, with live preview and copy/download.--bui-bg variable9b81a90: BREAKING - Marking optional fields as required in the TaskBroker, these can be fixed with a no-op () => void if you don't want to implement the functions.
cancel, recoverTasks and retry are the required methods on the TaskBroker interface.NOTE: If you're affected by this breaking change, please reach out to us in an issue as we're thinking about completely removing the TaskBroker extension point soon and would like to hear your use cases for the upcoming re-architecture of the scaffolder-backend plugin.
c8aa210: BREAKING ALPHA: We've moved the scaffolderActionsExtensionPoint from /alpha to the main export.
// before
import { scaffolderActionsExtensionPoint } from '@backstage/plugin-scaffolder-node/alpha';
// after
import { scaffolderActionsExtensionPoint } from '@backstage/plugin-scaffolder-node';
6e2bda7: DEPRECATION: We're going to be working on refactoring a lot of the internals of the Scaffolder backend plugin, and with that comes a lot of deprecations and removals for public types that are making these things hard.
If you're using these types, please reach out to us either on Discord or a GitHub issue with your use cases.
SerializedTask, SerializedTaskEvent, TaskBroker, TaskContext, TaskBrokerDispatchOptions, TaskBrokerDispatchResult, TaskCompletionState, TaskEventType, TaskFilter, TaskFilters, TaskStatus are the types that have now been marked as deprecated, and will be removed in a future release.Updated dependencies
f2cf564: Removed the script transform cache from the default Jest configuration. The script cache provided a moderate performance boost, but it is incompatible with Jest 30.
33faad2: Allow using custom manifest location in the yarn plugin and version bump.
The Backstage yarn plugin and version bump allows two new environment variables to configure custom manifest location:
BACKSTAGE_VERSIONS_BASE_URL: The base URL for fetching the Backstage version
manifest. Defaults to https://versions.backstage.io/v1/releases/VERSION/manifest.json.
Useful for running the plugin in environment without direct access to the internet,
for example by using a mirror of the versions API or a proxy.
Note that the environment variable is just the host name, and the path is appended by
the plugin. If you are using the yarn plugin, bump version command will also try
to fetch the new version of the yarn plugin from the same base URL (defaults to
https://versions.backstage.io/v1/releases/RELEASE/yarn-plugin)BACKSTAGE_MANIFEST_FILE: Path to a local manifest file. If set, the plugin
will not attempt to fetch the manifest from the network. Useful for running
the plugin in environment without internet access and without mirror of the
versions API.6ebc1ea: Fixed module federation config by only setting import: false on shared libraries for remote.
ab96bb7: Added a new --entrypoint option to the package start command, which allows you to specify a custom entry directory/file for development applications. This is particularly useful when maintaining separate dev apps for different versions of your plugin (e.g., stable and alpha).
Example usage:
Consider the following plugin dev folder structure:
dev/
index.tsx
alpha/
index.ts
yarn package start command uses the dev/ folder as the entry point and executes dev/index.tsx file;yarn package start --entrypoint dev/alpha will instead use dev/alpha/ as the entry point and execute dev/alpha/index.ts file.024645e: Remove unused @octokit modules from cli package
d14ef24: Added automatic detection and support for the Backstage Yarn plugin when generating new packages with yarn new. When the plugin is installed, new packages will automatically use backstage:^ ranges for @backstage/* dependencies.
Updated dependencies
renderEdge prop to <DependencyGraph /> component in @backstage/core-components to allow custom rendering of graph edges.svg size not adapting to the container sizebetter-sqlite3 to the latest version5e98e61: Minor doc updates
a1dae71: Allow frontend plugin to import from another frontend plugin with same plugin id.
This prevents the ESLint rule from incorrectly flagging these imports in the new frontend system where plugin override requires cross-plugin imports.
coreExtensionData.title, especially useful for creating extensible layout with tabbed pages, but available for use for other cases too.NotFound page to not render correctly when a Page was mounted at /.pagelen parameter to configure the pagelength property of the BitbucketCloudEntityProvider searchCode pagination to resolve bug pertaining to duplicate results being returned.9890488: Internal refactor to remove remnants of the old backend system
6493c98: Log before provider-orphaning eviction happens
2aaf01a: Fix for duplicate search results in entity-facets API call
e489661: Moved catalog processor and provider disabling and priorities under own config objects.
This is due to issue with some existing providers, such as GitHub, using array syntax for the provider configuration.
The new config format is not backwards compatible, so users will need to update their config files. The new format is as follows:
catalog:
providerOptions:
providerA:
disabled: false
providerB:
disabled: true
processorOptions:
processorA:
disabled: false
priority: 10
processorB:
disabled: true
77516c5: Added new catalog:validate-entity action to actions registry.
This action can be used to validate entities against the software catalog.
This is useful for validating catalog-info.yaml file changes locally using the
Backstage MCP server.
Updated dependencies
pagelen parameter to configure the pagelength property of the BitbucketCloudEntityProvider searchCode pagination to resolve bug pertaining to duplicate results being returned.GitlabDiscoveryEntityProvider where entity fetching could fail for projects with special characters or that had been renamed or moved.renderEdge prop to <DependencyGraph /> component in @backstage/core-components to allow custom rendering of graph edges.svg size not adapting to the container sizematerial-ui-popup-state to latest available version.clearAll logic to properly handle deletable flagnodemailer from 6.9.16 to 7.0.7initialRelationAggregation and showAggregateMembersToggle options to EntityMembersListCard as well to EntityOwnershipCardtemplatingExtensions option to RouterProps.contextMenu to allow global control across scaffolder pagesui:disabled in OwnedEntityPicker to allow disabling itscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportscaffolderActionsExtensionPoint to be the main exportapp-root-element:signals/signals-display which was not doing anything useful