Skip to main content


These are the release notes for the v1.6.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.


Moved to swc for transpilation

We’ve replaced sucrase with swc for transpilation in the Backstage CLI. While swc has slightly slower transpilation times, it’s a library backed by a larger community, and allows us to take advantage of React Refresh out of the box. There’s a few things that could possibly break installations of Backstage and compilation, you can read more about it in the changelog

React Router Stable Compatibility

Backstage has for a long time been using React Router version 6.0.0-beta.0. We adopted this unstable version because v6 had some new features that fit really well with Backstage, particularly relative routing. Because we jumped on this early and unstable version, we knew that we would at some point need a breaking migration to the stable version of React Router v6, which is the point we're at now!

The migration is controlled by each app, meaning this release will not force you to migrate straight away, you can do so at your own pace. Check out the migration guide for all you need to know!

Yarn 3 Support

It is now possible to migrate Backstage projects to use Yarn 3. See the migration guide for more information. Migrating to Yarn 3 is optional, and Backstage projects created with @backstage/create-app will still use classic Yarn by default.

New plugin: @backstage/plugin-user-settings-backend

The user-settings plugin now has an associated backend. This allows for the persistence of settings in your database, essentially in the form of a basic per-user key-value JSON store.

As this backend was added, user-settings also gained a UserSettingsStore class that implements the storageApiRef Utility API. If you install the backend as well as this frontend API, your starred entities and other storage-API-based features will no longer just be persisted in your browser’s local storage, but centrally so that all your devices can leverage them.

Contributed by @dschwank in #13570

New plugin: @backstage/plugin-playlist

This plugin can be used to create custom collections of Entities that can be shared throughout Backstage or for private usage.

Contributed by @kuangp in #12870

Security Fixes

Be sure to upgrade to the latest version of @backstage/plugin-scaffolder-backend, as it contains an explicit bump of a transitive dependency where a vulnerability was discovered. If you subscribe to CVE notifications you will already have received this update.

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.