Skip to main content

v1.57.0

These are the release notes for the v1.57.0 release of Backstage.

A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done.

Highlights​

Front-end system 1.0​

The front-end system reaches its 1.0 milestone in this release! The public APIs of @backstage/frontend-plugin-api, @backstage/frontend-app-api, @backstage/frontend-test-utils, and @backstage/frontend-dev-utils are now stable under the package versioning policy.

The extension-based architecture lets app owners install and configure plugins, customize how features fit together, and share those customizations through frontend modules. This release brings router-independent navigation, lazy Utility API implementations, translated page titles, and a consolidated set of core Utility APIs, alongside the removal of deprecated APIs.

If you are migrating an app, start with the app migration guide. Plugin authors can follow the plugin migration guide. Apps and plugins already using the front-end system should review the breaking changes below and the 1.57 frontend migration notes.

This milestone focuses on stabilizing the front-end plugin API and its surrounding architecture. Work on documentation, examples, and features continues, and adopters can expect further updates in those areas.

BREAKING: Router-independent frontend navigation​

The front-end system now owns the browser history, while each page can choose its own routing library. Three new adapter packages support React Router v6, React Router v7, and TanStack Router, including pages that host sub-pages using a different library. Existing pages retain implicit React Router v6 compatibility. Framework navigation APIs such as useAppNavigate, useAppLocation, and RouterLink let plugins navigate without depending on a page's router. Router and component-library integrations use the stable @backstage/frontend-plugin-api/routing entry point, while app history is available through coreApis.appHistory in the main entry point.

RouterBlueprint, the app/root router input, and convertLegacyAppOptions({ components: { Router } }) are no longer supported. Remove overrides that only install a BrowserRouter, move global providers to AppRootWrapperBlueprint, and render page adapters inside lazily loaded page components. Framework navigation destinations must start with / and exclude the deployment basename; use a page adapter for path-relative navigation. useRouteRefParams now returns only the parameters declared by its route ref, without an undeclared splat parameter. Apps using the old front-end system keep their existing routing setup.

Backstage UI routing is configured automatically in Backstage apps. Standalone apps must provide a useNavigation hook to BUIProvider if they previously relied on automatic React Router integration. routerOptions now only accepts replace and state, and links using javascript:, data:, or vbscript: become inert. See the routing migration notes and page router guide for setup and migration examples.

BREAKING: Deprecated frontend APIs removed​

This release removes several deprecated APIs from the front-end system and introduces further deprecations. Update custom extensions and API implementations when upgrading:

  • Use DialogApi.open with your own dialog presentation instead of show or showModal, and IconsApi.icon instead of getIcon. Upgrade @backstage/plugin-app alongside @backstage/frontend-plugin-api; the API references are now core.dialog.v2 and core.icons.v2.
  • Replace imports from @backstage/frontend-plugin-api/alpha with imports from the main entry point. The /alpha entry point has been removed; its exports retain the same behavior and identity at their new location.
  • Use IconElement instead of the removed IconComponent type. IconBundleBlueprint now requires elements such as icons: { user: <MyIcon /> } rather than components. For Material UI icons, use <MyIcon fontSize="inherit" />. Icons passed through convertLegacyAppOptions are converted automatically, and auth provider icons continue to accept components.
  • Use prepareSpecializedApp(options).finalize() instead of createSpecializedApp. Apps with sign-in or asynchronous session preparation must render the bootstrap app and subscribe through onFinalized(). Use advanced.sessionState to reuse a finalized session, and ApiBlueprint extensions to register custom APIs.
  • Custom navigation components now receive navItems instead of the flat items collection. Use navItems.rest(), item.href, and item.title, and render item.icon as a React element.
  • Import AnalyticsImplementation, AnalyticsImplementationBlueprint, and AnalyticsImplementationFactory from @backstage/plugin-app-react, and ExtensionFactoryMiddleware from @backstage/frontend-app-api.
  • Replace withApis with a function component using useApi. Use FrontendPlugin.pluginId, PageLayoutTab, and CreateFrontendPluginOptions instead of the removed id, PageTab, and PluginOptions aliases.
  • Replace ExtensionAttachTo with Extension<unknown>['attachTo'], and ProgressProps with its existing shape, {}.
  • Remove the ignored anchorOrigin option from built-in alert display configuration and toast display props.
  • AnyApiRef and AnyApiFactory are deprecated in favor of ApiRef and ApiFactory without type arguments. The deprecated aliases remain available for compatibility.

Plugins passed as a FrontendFeature must now provide pluginId. Rebuild plugins that predate this property against a current framework version.

The legacy withApis and icon component APIs remain available from @backstage/core-plugin-api for apps using the old front-end system, although withApis is deprecated there too.

Core Utility APIs​

The front-end system now groups its core Utility API references in coreApis, imported from @backstage/frontend-plugin-api. Access APIs through calls such as useApi(coreApis.config), useApi(coreApis.identity), and useApi(coreApis.toast).

Individual references with namespace equivalents, such as configApiRef, are deprecated. Both forms refer to the same API reference, so existing factories and implementations remain compatible during migration. Provider-specific authentication references remain separate. See consuming Utility APIs for usage examples and migration guidance.

BREAKING: Lazy Utility API implementations​

Utility API factories can now load implementations on demand through dynamic imports. Declare the API value as a promise, for example ApiRef<Promise<WorkApi>>. The useApi hook from @backstage/frontend-plugin-api unwraps the promise, suspends while it is pending, and throws rejection reasons to an error boundary:

const workApiRef = createApiRef<Promise<WorkApi>>().with({
id: 'plugin.example.work',
});
const workApi = useApi(workApiRef); // WorkApi

The hook's return type is now Awaited<T>. Consumers that intentionally used a promise returned by useApi must switch to useApiHolder().get(ref). Changing an existing API ref to a promise changes its public contract, so update its consumers and custom factories together. Holders and factory dependencies continue to receive the declared API value unchanged. The legacy useApi hook from @backstage/core-plugin-api continues returning promises directly.

Page extension boundaries provide Suspense and error handling; consumers outside those boundaries must provide their own. TestApiProvider and other mock API overrides accept synchronous mocks even for promise-valued APIs, so tests can keep synchronous assertions when rendering is otherwise synchronous. Promise-valued mocks are also supported, with renderInTestApp supplying an empty Suspense fallback while they resolve. Tests that relied on an ancestor boundary's loading UI may need updated assertions. See the Utility API documentation for lazy factories and migration guidance.

BREAKING: Stricter frontend tests and isolated API defaults​

renderInTestApp, renderTestApp, and createExtensionTester now throw for all errors reported while creating the test app or extension tree, including errors that a real app only logs as warnings. Fix invalid test setups, or allow an intentional error through the isExpectedError option. API overrides belong in the test app's apis option; a conflicting factory supplied through extensions is rejected. Contributed by @dyatko in #36333.

Test apps also use defaults designed for isolation: storage is kept in memory per app, toasts and errors are collected without displaying them, and alerts are no longer replayed to late subscribers. Tests that depend on browser storage, visible notifications, or global error handling need an explicit API implementation. Expanded mockApis helpers provide typed mocks and functional fakes for core APIs. Removed standalone mock types can be replaced with types derived from these helpers, such as ReturnType<typeof mockApis.analytics>.

Both render helpers now return an apis holder with access to the same Utility API instances used by components, including test overrides. For navigation tests, use apis.get(coreApis.appHistory) to access the app history. Page matching uses framework routing; wrap test elements in a page adapter when they need routing-library context. See the navigation testing guide.

BREAKING: Supported Node.js, TypeScript, and React versions​

The supported Node.js versions are now 24 and 26. Update engines.node in your root package.json to ^24.15.0 || ^26.13.0, and check the versions used in your CI workflows and Docker images. Versions of avsc before 5.7.8 can break tests on Node.js 26, and node-gyp 12.3.0 cannot download headers through a proxy on that version; run yarn up -R avsc or yarn up -R node-gyp if your lockfile contains the affected versions.

The CLI now compiles for ES2024 and requires TypeScript 5.9 or later. Backstage does not include polyfills, so frontend code using ES2024 APIs such as Object.groupBy needs Chrome or Edge 119, Firefox 121, or Safari 17.4 or later. Contributed by @sebdanielsson in #36512 and #36509.

Most frontend packages now require React 18. The old front-end system core packages retain React 17 in their own peer dependency ranges, but their dependencies include packages that require React 18, so apps using the old system also need to plan the upgrade. See the React 18 migration guide and frontend migration notes.

BREAKING: JSON request log timestamps​

Production JSON logs now include a timestamp field on every line. Root HTTP router request logs no longer include a date field or repeat the date at the start of the message. Update log pipelines and dashboards that read either of those values to use timestamp. Custom JSON logger formats should combine format.timestamp() with format.json() to preserve the field.

Contributed by @nboaldin in #36783.

BREAKING: OAuth client registration and PKCE​

The deprecated experimental Dynamic Client Registration (DCR) support has been removed from the auth backend. Use Client ID Metadata Documents (CIMD), or pre-register clients through auth.staticClients, and remove auth.experimentalDynamicClientRegistration from your configuration. The database migration deletes DCR clients and their authorization and offline sessions, invalidating their authorization codes and refresh tokens. Users must sign in again through a CIMD or pre-registered client; already-issued user tokens remain valid until they expire. See the DCR migration guide.

Pre-registered clients support a fixed client ID, an optional secret, and exact redirect URIs, allowing integrations that do not support CIMD to authenticate. Clients with a secret must authenticate for both code exchanges and refreshes. Removing a client from the configuration rejects its outstanding authorization codes and refresh tokens. See pre-registered clients.

All clients of the auth backend's OAuth service, including existing CIMD clients and pre-registered clients with a secret, now require Proof Key for Code Exchange (PKCE) with the S256 challenge method. The plain method is no longer accepted or advertised. Update clients that use plain to generate SHA-256 challenges. Pre-registered client support and PKCE changes contributed by @drodil in #36567.

BREAKING: Webhook authentication required by default​

The GitHub, GitLab, and Azure DevOps events modules now reject requests to their webhook endpoints with HTTP 403 when no webhook secret is configured. Configure secrets under events.modules.github, events.modules.gitlab, and events.modules.azureDevOps before upgrading; GitHub also supports secrets configured per GitHub App. This applies to the modules' own endpoints; routes configured only through events.http.topics still have no validator attached.

For development setups that deliberately accept unauthenticated events, each module provides an explicit dangerouslyAllowUnauthenticatedEvents: true option. Custom users of createGitlabTokenValidator must also supply its new logger argument. See the configuration sections for the GitHub, GitLab, and Azure DevOps modules.

BREAKING: LDAP attribute selection and parallel reads​

LDAP organization ingestion now requests only the attributes used by configured mappings, instead of ['*', '+']. This affects both the entity provider and LdapOrgReaderProcessor. Custom transformers that read additional attributes must list them in users.options.attributes or groups.options.attributes, or explicitly use ['*', '+'] to request all attributes. An explicitly configured list is used as-is and must include every attribute needed by mappings, vendor configuration, and transformers.

The entity provider also reads users and groups in parallel by default, opening two connections and binds per refresh. Set disableParallelReads: true on the provider to retain sequential reads when directory connection limits require it. Connections are closed after each refresh.

Contributed by @04kash in #35319.

BREAKING: Google Cloud task recovery permissions​

The Scaffolder Google Cloud module now stores each task recovery snapshot as a separate object, avoiding storage rate limits when template steps finish in quick succession. Grant the backend's Google Cloud credentials storage.objects.list on the task recovery bucket before upgrading, in addition to the existing object permissions. Recovery continues to support snapshots saved by older versions.

Contributed by @acierto in #36466.

BREAKING PRODUCERS: Authenticated WebSocket routes​

The backend HTTP router services now provide addWebSocketHandler for registering WebSocket upgrade routes. Routes require token authentication by default, and browser clients can pass bearer tokens through the WebSocket protocol header. Cookie authentication is not supported. Custom implementations of HttpRouterService and RootHttpRouterService must implement the new method; the backend test utilities support it too.

The Signals backend uses this API, fixing first connections that previously required an HTTP request before the WebSocket could connect. Existing server upgrade listeners can coexist during migration, but plugins that handle upgrades only through Express, such as the Kubernetes proxy, must migrate to the router API when the framework's server-level listener is active. Otherwise, unmatched upgrades receive a 404 response when it is the only server-level listener. See the HTTP router service documentation.

BREAKING PRODUCERS: Translated frontend titles​

Page and sub-page blueprints, along with EntityContentBlueprint, now accept typed translation message selections as titles. Select a message by calling its translation ref, for example myTranslationRef('page.title'). Navigation, page headers, tabs, and breadcrumbs render the translated title. Selections must not require formatting values, and resolved translations take precedence over configured static titles in every language.

TranslationRef values are now callable functions and must be treated as opaque values rather than cloned or checked for plain-object shape. Custom TranslationApi implementations must provide t in every translation snapshot, including while ready is false, using available messages and language fallbacks. Titles wait for the initial selected language and retain resolved values during later loads or failures, preserving page state. See the internationalization guide.

Experimental Zensical engine for TechDocs​

The new @backstage/plugin-techdocs-backend-module-zensical module adds Zensical as an experimental TechDocs engine. Select it per entity with backstage.io/techdocs-engine: zensical, or set techdocs.generator.defaultEngine: zensical. MkDocs remains the default. See the Zensical engine guide for setup and configuration.

The TechDocs CLI supports Zensical in serve, serve:raw, and generate, including live reload in the preview app. Docker images are now selected per engine, and MkDocs previews use spotify/techdocs:v1.2.8 rather than latest. The --mkdocs-port, --mkdocs-config-file-name, and --mkdocs-parameter-* flags are deprecated in favor of --engine-port, --config-file-name, and --parameter-*. An alpha entry point in @backstage/plugin-techdocs-node provides building blocks for additional engines.

Contributed by @byan1197 in #36159.

Conditional parameter steps in Software Templates​

Software Templates can now show or hide whole parameter steps based on earlier answers using a when condition, such as ${{ parameters.cloudProvider === 'AWS' }}. The frontend wizard and backend validation evaluate the same conditions, and values from hidden steps are excluded from the task parameters. Fields referenced by conditions should be validated by an earlier unconditional step. See conditional parameter steps.

Apps using the front-end system can filter the template list based on identity, catalog data, or other viewer-specific state through ScaffolderTemplateFilterBlueprint. This extension is not available in the old front-end system. Contributed by @Dasmat13 in #36096.

Bitbucket Cloud discovery credential update​

The Bitbucket Cloud entity provider now uses the workspace code search API following retirement of the previous endpoint on November 15, 2026. Workspace code search requires a credential that identifies a user, such as an Atlassian account email as username with an API token, and both read:repository:bitbucket and read:workspace:bitbucket scopes. App passwords, legacy OAuth consumers, API keys, and API tokens missing the workspace scope are rejected by that API.

When code search is unavailable or rejects the configured credentials, discovery falls back to checking catalog files through the source API. Adding read:workspace:bitbucket to an API token restores workspace code search. BitbucketCloudClient.searchCode is deprecated in favor of searchWorkspaceCode.

Contributed by @cruftyoldsysadmin in #36766, with fallback support by @eisen0419 in #36845.

Catalog query performance and upgrade guidance​

Catalog queries on PostgreSQL are faster when conditional permission policies produce $any or $not filters, or match fields against long lists of values such as ownership claims. Facet and total count queries also benefit. Contributed in part by @drodil in #36518.

Malformed predicates that combine $all, $any, or $not with other keys in the same object, or pass non-array operands to $all or $any, now receive a 400 response instead of silently ignoring parts of the filter. Entity lookups through entities/by-refs now match case-insensitively, consistent with the entity reference contract. Contributed by @chicobento in #36744.

The catalog database upgrade also adds publication bookkeeping and builds an index concurrently on PostgreSQL. The index build scans the catalog table and can exceed deployment startup deadlines on large installations. Review upgrading large installations for instructions on preparing the column and index before deploying.

Authentication and session reliability​

Background OAuth refreshes no longer prompt users to sign in again after transient network failures. Contributed by @csuich2 in #35003. Refresh requests are also coordinated across tabs in browsers with the Web Locks API, avoiding competing refreshes with providers that rotate refresh tokens. Contributed by @hudsonb in #36615.

Sign-in resolvers now issue canonical, deduplicated entity references in user token claims, and auth logout correctly revokes the CLI refresh token. A service-authenticated POST /v1/offline-sessions/revoke endpoint lets backends revoke all of a user's offline sessions when auth.experimentalRefreshToken.enabled is set. Cursor clients are allowed to use CIMD by default, contributed by @pjohannis in #36568.

OAuth access and ID tokens issued by the auth backend now respect auth.backstageTokenExpiration instead of always expiring after one hour. Contributed by @Retr0-XD in #35325.

Azure DevOps certificate authentication​

Azure DevOps integrations can authenticate an App Registration with a certificate instead of a client secret. Configure the ClientCertificate credential kind with clientId, tenantId, and either clientCertificate containing the PEM certificate and private key, or clientCertificatePath.

Contributed by @davidkarlsen in #36225.

The Azure DevOps URL reader now warns at startup when a personal access token is configured for Azure DevOps Services. Global personal access tokens retire on January 27, 2027, and organization-scoped tokens are deprecated in favor of Microsoft Entra ID credentials. See the retirement announcement when planning the migration.

Backstage UI updates​

Alongside the routing changes described above, useTable no longer shows an empty page with a NaN range when pagination is enabled after mounting. Contributed by @GabDug in #35881. See the BUI changelog for the full list of updates.

Header tabs stay in a single scrolling row when they do not fit, instead of causing the entire page to scroll horizontally. Overflow fades, pointer scroll buttons, and automatic scrolling keep the active tab visible. Contributed by @carlerikjohan in #36177.

The catalog entity-not-found display now uses Backstage UI, contributed by @Abhijnya002 in #36777. The catalog import pull request preview card has also migrated, contributed by @rickylandino in #36835.

Legacy frontend component deprecations​

Many @backstage/core-components exports now have deprecation notices pointing to Backstage UI replacements or compositions. These include page shells, headers, tabs, links, cards, selectors, avatars, alert displays, and icon wrappers. Existing exports and behavior remain available. Follow each component's migration notice when adapting props, document titles, routing, and layout; these are not all direct import replacements.

Use page and sub-page extensions with PageLayout for framework-managed pages, compose @backstage/ui for standalone layouts, and use coreApis.icons for app-customizable icons.

Error type guards across package copies​

@backstage/errors now provides static type guards such as AuthenticationError.is(value) and ResponseError.is(value) to narrow unknown errors across package copies by checking their name and basic shape:

import { ResponseError } from '@backstage/errors';

if (ResponseError.is(error)) {
console.log(error.statusCode);
}

Use isErrorWithName(value, name) to implement name-based guards for custom errors.

Additional fixes and improvements​

  • API reference IDs now use the plugin ID format for each dot-separated component, accepting mixed case and numeric dash groups such as plugin.example-2.todos.
  • Test rendering helpers preserve their test extensions when a plugin named test is included in features.
  • Backend startup results include optional beginAt timestamps for plugin and module initialization, separating initialization time from time spent waiting for dependencies. Contributed by @hudsonb in #36326.
  • coreServices and mockServices are now frozen objects. Existing calls and types remain available, but runtime mutation and spying on the mock service helpers themselves are no longer supported; the mocks they create are unaffected.
  • The Valkey cache store now separates keys by plugin. Existing cache values are rebuilt under new keys, and old entries without a time to live need manual cleanup. Contributed by @pavstev in #36584.
  • App backend startup uses less memory and database traffic when checking cached assets. Contributed by @hudsonb in #36458.
  • MarkdownContent loads its renderer on first use, reducing the app startup bundle. Tests that immediately assert on rendered Markdown may need asynchronous queries.
  • Apps no longer remount when deferred root elements are added during finalization, and swappable components preserve mounted state when their props change.
  • Dismissed toasts no longer reappear when the toast display remounts, such as after a theme change. Contributed by @abdul-karim-mia in #36813.
  • Dynamic frontend plugins can export a FrontendFeatureLoader. Contributed by @hopehadfield in #35687.
  • Dynamic backend plugins can resolve shared packages with the isolated pnpm linker. Contributed by @sebdanielsson in #36229.
  • TechDocs releases storage connections when browsers disconnect early, including a fix for S3 connection pool exhaustion. Contributed in part by @lvthillo in #36468.
  • The TechDocs table of contents stays aligned with the documentation on wide screens. Contributed by @bhargavikvmpl-2001 in #36216.
  • Software Templates supports GitLab branch autocompletion in RepoBranchPicker. Contributed by @ebarault in #36086.
  • The new github:repo:rulesets:create action lets Software Templates create GitHub repository rulesets, including rules and bypass actors in the GitHub REST API format. Contributed by @rbstp in #36776.
  • Scaffolder task controls retain their chosen visibility after completion, log redaction preserves public values, and custom task permission rules are honored. Contributed by @ebarault in #36472, #36477, and #36210.
  • BUI template forms have clearer array item headings, more accessible item controls, and working enum multi-select fields. Contributed by @ebarault in #36469, and @Dasmat13 in #36423 and #36331.
  • GitLab publish actions check individual files if listing the repository tree fails, avoiding incorrect file-creation attempts. Contributed by @leneti in #36486.
  • Confluence attachment download failures now fail the task rather than leaving it hanging, and downloaded files are closed correctly. Contributed by @rowmanempire in #36745.
  • Broadcast notifications preserve their read and saved states independently. Contributed by @FayezBast in #36535.
  • DevTools displays backend errors and loading progress for scheduled tasks. Contributed by @Dasmat13 in #36533.
  • GitHub organization providers can request public emails when authenticating with a GitHub App using fetchEmailForGithubApps. Enable it only after checking that your GitHub instance supports the query. Contributed by @vinzscam in #36736.
  • AWS Kubernetes clusters can use configured account credentials directly through kubernetes.io/aws-account-id. The S3 URL reader also avoids assuming an account's already-assumed role a second time. Contributed in part by @hudsonb in #35963.
  • Incremental ingestion tolerates repeated entity references within a page or event, avoiding PostgreSQL upsert failures. Catalog placeholder processing also waits for all reads to settle before reporting an error.
  • PostgreSQL unique constraint violations are detected correctly when database error messages are localized, allowing catalog ingestion to fall back to individual updates for duplicate entity references. Contributed by @harshitsharmaaaa in #36921.
  • PostgreSQL search indexing skips full-text vector computation for unchanged documents. Contributed by @Sriram-Nambiar in #36473.
  • Search autocomplete with multiple selection no longer clears typed text after each keystroke. Contributed by @dfl-aeb in #35967.
  • The World Clock home widget now uses Backstage UI. Contributed by @jzhn in #36781.
  • CLI commands preserve their exit codes, and package startup supports repeated --import and --require flags. Flag support contributed by @dotboris in #36647.
  • The CLI handles JavaScript ES modules in packages without a type field correctly. Contributed by @vibbix in #36604.
  • Package scaffolding preserves existing CODEOWNERS content, reuses newer compatible dependency ranges, and fixes corrupted nested filenames on Windows. The Windows fix was contributed by @HLoc26 in #35242.
  • New apps apply their selected light or dark theme before loading, avoiding an initial light background for dark themes. Contributed by @carlerikjohan in #36162.
  • Event request validators receive parsed query parameters and can specify a response content type when rejecting a request. Contributed by @stanislav-c in #36488.
  • Generated API reference pages no longer overwrite declarations whose names collide by case or declaration kind.
  • resolvePackagePath accepts file URL strings such as import.meta.url, and backend plugins resolve their database migrations relative to their own package without requiring package-name resolution.
  • registerMswTestHooks also fails tests on unhandled requests when used with MSW 3.
  • OpenAPI client and server generation commands exit with a non-zero status when generation fails, allowing CI to detect failures. Watch mode keeps watching after errors. Contributed by @aksharprabhudesai in #36854.
  • The GitHub URL reader releases connections after failed requests with large error bodies, avoiding connection and memory leaks during outages. Contributed by @dddimcha in #36830.
  • @backstage/cli-module-package-manager-yarn makes its Yarn dependencies optional peers to avoid an upstream installation failure. Until fixed upstream, users of pm verify-patches must add @yarnpkg/cli, @yarnpkg/core, and @yarnpkg/plugin-patch as root development dependencies, along with the resolution "@yarnpkg/core/got": "npm:^11.8.6".

Security Fixes​

The following packages have received security fixes:

  • @backstage/backend-defaults
  • @backstage/plugin-auth-backend
  • @backstage/plugin-catalog-backend
  • @backstage/plugin-catalog-backend-module-gitlab
  • @backstage/plugin-events-backend-module-azure
  • @backstage/plugin-events-backend-module-github
  • @backstage/plugin-events-backend-module-gitlab
  • @backstage/plugin-scaffolder-backend
  • @backstage/plugin-scaffolder-react
  • @backstage/plugin-techdocs-backend
  • @backstage/plugin-techdocs-backend-module-zensical
  • @backstage/plugin-techdocs-node
  • @techdocs/cli

Contributors​

Big shoutout to all of the amazing folks who contributed to this release: @04kash, @abdul-karim-mia, @Abhijnya002, @acierto, @aksharprabhudesai, @alizard0, @apgmartin, @asyntai, @beatleboy501, @bhargavikvmpl-2001, @bjornramberg, @byan1197, @carlerikjohan, @chicobento, @cruftyoldsysadmin, @csuich2, @Dasmat13, @davidkarlsen, @dddimcha, @dfl-aeb, @djanickova, @dotboris, @drewswiredin, @drodil, @dyatko, @ebarault, @eisen0419, @FayezBast, @GabDug, @harshitsharmaaaa, @HLoc26, @hopehadfield, @hudsonb, @hyeongjun07, @jzhn, @Kartikupadhyay44, @leneti, @lvthillo, @nboaldin, @neoreddog, @NithinU2802, @nitin15j, @pavstev, @pjohannis, @rbstp, @Retr0-XD, @rickylandino, @rowmanempire, @SatvikMishra08, @sebdanielsson, @serahkiburu, @Sriram-Nambiar, @stanislav-c, @vibbix, @vinzscam, @vlbaluk, @webstackdev

Upgrade path​

We recommend that you keep your Backstage project up to date with this latest release. For more guidance on how to upgrade, check out the documentation for keeping Backstage updated.

Below you can find a list of links and references to help you learn about and start using this new release.

Sign up for our newsletter if you want to be informed about what is happening in the world of Backstage.