docs/releases/v1.32.0-next.0-changelog.md
Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.32.0-next.0
6129076: BREAKING: Removed the following deprecated commands:
create: Use backstage-cli new insteadcreate-plugin: Use backstage-cli new insteadplugin:diff: Use backstage-cli fix insteadtest: Use backstage-cli repo test or backstage-cli package test insteadversions:check: Use yarn dedupe or yarn-deduplicate insteadclean: Use backstage-cli package clean insteadIn addition, the experimental install and onboard commands have been removed since they have not received any updates since their introduction and we're expecting usage to be low. If you where relying on these commands, please let us know by opening an issue towards the main Backstage repository.
exports object before publishing. This is to help with identifying the declarative integration points for plugins without needing to fetch or run the plugins first.LEGACY_BACKEND_START flag is now deprecated.bfd4bec: BREAKING PRODUCERS: The IconComponent no longer accepts fontSize="default". This has effectively been removed from Material-UI since its last two major versions, and has not worked properly for them in a long time.
This change should not have an effect on neither users of MUI4 nor MUI5/6, since the updated interface should still let you send the respective SvgIcon types into interfaces where relevant (e.g. as app icons).
createApp and CreateAppFeatureLoader from @backstage/frontend-app-api, use the same createApp and CreateAppFeatureLoader import from @backstage/frontend-defaults instead.4a5ba19: Removed deprecated namespace option from createExtension and createExtensionBlueprint, including .make and .makeWithOverides, it's no longer necessary and will use the pluginId instead.
Removed deprecated createExtensionOverrides this should be replaced with createFrontendModule instead.
Removed deprecated BackstagePlugin type, use FrontendPlugin type instead from this same package.
bfd4bec: BREAKING PRODUCERS: The IconComponent no longer accepts fontSize="default". This has effectively been removed from Material-UI since its last two major versions, and has not worked properly for them in a long time.
This change should not have an effect on neither users of MUI4 nor MUI5/6, since the updated interface should still let you send the respective SvgIcon types into interfaces where relevant (e.g. as app icons).
873e424: Internal refactor of usage of opaque types.
323aae8: It is now possible to override the blueprint parameters when overriding an extension created from a blueprint:
const myExtension = MyBlueprint.make({
params: {
myParam: 'myDefault',
},
});
const myOverride = myExtension.override({
params: {
myParam: 'myOverride',
},
});
const myFactoryOverride = myExtension.override({
factory(origFactory) {
return origFactory({
params: {
myParam: 'myOverride',
},
});
},
});
The provided parameters will be merged with the original parameters of the extension.
Updated dependencies
api-report.md to report.api.mdFormFieldBlueprint to create field extensions in the Scaffolder plugin734c2d4: Add fetch:template:file scaffolder action to download a single file and template the contents. Example usage:
- id: fetch-file
name: Fetch File
action: fetch:template:file
input:
url: https://github.com/backstage/software-templates/blob/main/scaffolder-templates/create-react-app/skeleton/catalog-info.yaml
targetPath: './target/catalog-info.yaml'
values:
component_id: My Component
owner: Test
094eaa3: Remove references to in-repo backend-common
11e0752: Make it possible to manually retry the scaffolder template from the step it failed
Updated dependencies
FormFieldBlueprint to create field extensions in the Scaffolder pluginexternalLink to icon defaultsbitbucket-server-auth default API to set its environment based on the auth.environment config option instead of being hardcoded to development.094eaa3: Remove references to in-repo backend-common
04af116: The backend will no longer exit immediately if any plugin or modules fails to initialize. Instead, the backend will wait for all plugins and modules to either start up successfully or throw, and then shut down the backend if there were any initialization errors.
This fixes an issue where backend initialization errors in adjacent plugins during database schema migration could cause the database migrations to be stuck in a locked state.
Updated dependencies
BackstagePlugin type and move to FrontendPluginLink component now accepts externalLinkIcon prop.yarnrc.yml in the template.094eaa3: Remove references to in-repo backend-common
5c728ee: The events backend now has its own built-in event bus for distributing events across multiple backend instances. It exposes a new HTTP API under /bus/v1/ for publishing and reading events from the bus, as well as its own storage and notification mechanism for events.
The backing event store for the bus only supports scaled deployment if PostgreSQL is used as the DBMS. If SQLite or MySQL is used, the event bus will fall back to an in-memory store that does not support multiple backend instances.
The default EventsService implementation from @backstage/plugin-events-node has also been updated to use the new events bus.
Updated dependencies
EventsService now uses the new event bus for distributing events across multiple backend instances if the events backend plugin is installed.gitlab:group:ensureExists action to instead use oauth client.emptyState input optional on entity-content:techdocs extension so that
the default empty state extension works correctly.