docs/releases/v1.40.0-next.0-changelog.md
Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.40.0-next.0
coreServices.actionsRegistry and coreServices.actions to allow registration of distributed actions from plugins, and the ability to invoke these actionsActionsService and ActionsRegistryServicepackage-docs command.backstage-repo-tools schema openapi generate without the --watch flag.package-docs command.backstage.io/techdocs-entity-path annotation which allows deep linking into another entities TechDocs in conjunction with backstage.io/techdocs-entity.info.packageJson option to the plugin instance for the new frontend system.backstage.io/techdocs-entity-path annotation which allows deep linking into another entities TechDocs in conjunction with backstage.io/techdocs-entity.info.packageJson option to the plugin instance for the new frontend system.backstage.io/techdocs-entity-path annotation which allows deep linking into another entities TechDocs in conjunction with backstage.io/techdocs-entity.ActionsService and ActionsRegistryService that allow registration of actions for a particular plugin.plugin.info() method in specialized apps with a default resolved for package.json and catalog-info.yaml. The default resolution logic can be overridden via the pluginInfoResolver option to createSpecializedApp, and plugin-specific overrides can be applied via the new app.pluginOverrides key in static configuration.pluginInfoResolver option for createApp.9e3868f: Added a new optional info option to createFrontendPlugin that lets you provide a loaders for different sources of metadata information about the plugin.
There are two available loaders. The first one is info.packageJson, which can be used to point to a package.json file for the plugin. This is recommended for any plugin that is defined within its own package, especially all plugins that are published to a package registry. Typical usage looks like this:
export default createFrontendPlugin({
pluginId: '...',
info: {
packageJson: () => import('../package.json'),
},
});
The second loader is info.manifest, which can be used to point to an opaque plugin manifest. This MUST ONLY be used by plugins that are intended for use within a single organization. Plugins that are published to an open package registry should NOT use this loader. The loader is useful for adding additional internal metadata associated with the plugin, and it is up to the Backstage app to decide how these manifests are parsed and used. The default manifest parser in an app created with createApp from @backstage/frontend-defaults is able to parse the default catalog-info.yaml format and built-in fields such as spec.owner.
Typical usage looks like this:
export default createFrontendPlugin({
pluginId: '...',
info: {
manifest: () => import('../catalog-info.yaml'),
},
});
6f48f71: Added a new useAppNode hook, which can be used to get a reference to the AppNode from by the closest ExtensionBoundary.
info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.refresh_state_references.id to be a big intinfo.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.info.packageJson option to the plugin instance for the new frontend system.backstage.io/techdocs-entity-path annotation which allows deep linking into another entities TechDocs in conjunction with backstage.io/techdocs-entity.info.packageJson option to the plugin instance for the new frontend system.