ContextQMD
Back to Backstage

Release v1.53.0-next.1

docs/releases/v1.53.0-next.1-changelog.md

1.53.0-next.17.8 KB
Original Source

Release v1.53.0-next.1

Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.53.0-next.1

@backstage/[email protected]

Minor Changes

  • c8a06d5: Added new frontend module that provides database-backed user settings storage. When installed, it overrides the default browser local storage with the user settings backend, enabling settings to persist across devices and sessions.

Patch Changes

@backstage/[email protected]

Minor Changes

  • 567bc4c: BREAKING: Removed the deprecated Server-Sent Events (SSE) MCP transport. MCP clients must use the Streamable HTTP endpoint at /api/mcp-actions/v1 or a configured named-server endpoint.

@backstage/[email protected]

Patch Changes

  • d62c384: Fixed a bug where scheduled tasks that were initially registered with a manual trigger and later re-registered with a duration or cron cadence would never be scheduled to run.
  • Updated dependencies

@backstage/[email protected]

Patch Changes

  • 61d4881: The shared ESLint configuration now reports unused imports in config.d.ts configuration schema files. These declaration files are not covered by the TypeScript compiler's unused-variable checks, which previously allowed a stray import to slip through. Such an import can resolve during local development but break configuration schema loading for consumers of the published package, so it is now caught at lint time.
  • Updated dependencies

@backstage/[email protected]

Patch Changes

  • 3cce70f: Increase generated frontend static asset filename hashes to 12 characters to reduce the chance of collisions across long-lived cached builds.
  • Updated dependencies

@backstage/[email protected]

Patch Changes

  • 005458a: Added support for comma-separated values in the BACKSTAGE_ENV environment variable, allowing multiple environment-specific configuration files to be loaded and stacked at startup. For example, setting BACKSTAGE_ENV=e2e-test,production will load app-config.e2e-test.yaml and app-config.production.yaml in addition to the base app-config.yaml, with later environments taking priority. Local override files (.local.yaml) are always loaded after all non-local files.

@backstage/[email protected]

Patch Changes

  • fc4cae1: Added the user settings backend plugin to the create-app templates, enabling database-backed user settings persistence for newly created Backstage apps out of the box. The frontend storage API is also wired up to use backend-persisted storage instead of browser local storage, via the new @backstage/plugin-app-module-user-settings module.
  • 3acdf87: Pinned @types/node to 22.20.0 in the seed lockfile to prevent yarn from resolving the * wildcard (from @jest/environment-jsdom-abstract) to @types/[email protected], which breaks tsc:full due to incompatible EventEmitter types in tarn.

@backstage/[email protected]

Patch Changes

  • 6ea6d31: Internal refactor of the specialized app sign-in runtime to initialize it once instead of reassigning it.
  • Updated dependencies

@backstage/[email protected]

Patch Changes

  • a5b2811: Adds useBreadcrumbEntries hook, BreadcrumbEntry component, and BreadcrumbsRegistryProvider for managing breadcrumb trails across the component tree for plugins using new frontend system. Completes wiring so that new frontend system plugin Pages and SubPages get automatic-population of PluginHeader breadcrumbs.

    • The app plugin's PageLayout registers a root breadcrumb for each plugin page and passes the breadcrumb trail to PluginHeader
    • PageBlueprint automatically wraps each sub-page route element with BreadcrumbEntry, so sub-pages contribute to the PluginHeader breadcrumb trail without extra wiring.
    • Plugin authors who need breadcrumbs for internal routes within a sub-page can wrap their route content with BreadcrumbEntry manually.
      • plugin-scaffolder internal routes have been wrapped as an example

@backstage/[email protected]

Patch Changes

  • 2341682: Make PluginHeader > Breadcrumbs separator align with rest of text

    Affected components: PluginHeader

@backstage/[email protected]

Patch Changes

  • a5b2811: Adds useBreadcrumbEntries hook, BreadcrumbEntry component, and BreadcrumbsRegistryProvider for managing breadcrumb trails across the component tree for plugins using new frontend system. Completes wiring so that new frontend system plugin Pages and SubPages get automatic-population of PluginHeader breadcrumbs.

    • The app plugin's PageLayout registers a root breadcrumb for each plugin page and passes the breadcrumb trail to PluginHeader
    • PageBlueprint automatically wraps each sub-page route element with BreadcrumbEntry, so sub-pages contribute to the PluginHeader breadcrumb trail without extra wiring.
    • Plugin authors who need breadcrumbs for internal routes within a sub-page can wrap their route content with BreadcrumbEntry manually.
      • plugin-scaffolder internal routes have been wrapped as an example

  • Updated dependencies

@backstage/[email protected]

Patch Changes

  • 9d23b9e: Added HTTP POST webhook ingress endpoint for Azure DevOps events, matching the pattern established by the GitHub events module. The ingress endpoint is only registered when events.modules.azureDevOps.webhookSecret is configured; without it, no route is exposed. Incoming requests are validated against the x-ado-webhook-secret custom header using timing-safe comparison.

@backstage/[email protected]

Patch Changes

  • 2ed90cd: Fixed the published configuration schema so that it no longer references a file that is excluded from the package. This previously caused configuration schema extraction to fail in apps that depend on this plugin.

@backstage/[email protected]

Patch Changes

  • a5b2811: Adds useBreadcrumbEntries hook, BreadcrumbEntry component, and BreadcrumbsRegistryProvider for managing breadcrumb trails across the component tree for plugins using new frontend system. Completes wiring so that new frontend system plugin Pages and SubPages get automatic-population of PluginHeader breadcrumbs.

    • The app plugin's PageLayout registers a root breadcrumb for each plugin page and passes the breadcrumb trail to PluginHeader
    • PageBlueprint automatically wraps each sub-page route element with BreadcrumbEntry, so sub-pages contribute to the PluginHeader breadcrumb trail without extra wiring.
    • Plugin authors who need breadcrumbs for internal routes within a sub-page can wrap their route content with BreadcrumbEntry manually.
      • plugin-scaffolder internal routes have been wrapped as an example

  • Updated dependencies

[email protected]

Patch Changes

[email protected]

Patch Changes