Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: v1.7.0.md

id: v1.7.0 title: v1.7.0 description: Backstage Release v1.7.0 These are the release notes for the v1.7.0 release of . 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. The analysis performed during catalog imports (i.e. when supplying the URL of a repository rather than an individual YAML file in the Create flow) is now powered by the backend rather than frontend code. This means that the catalog backend needs to be supplied with a location analyzer for this use case to continue to function. If you want to make use of this feature, check out the installation instructions in . Contributed by in When defining permission rules, it's now necessary to provide a that specifies the parameters the rule expects. This has been added to help better describe the parameters in the response of the metadata endpoint and to validate the parameters before a rule is executed. The signatures of the rule methods (`apply` and `toQuery`) have changed slightly as well. You can read more about this in and . Both `jest`, `jest-runtime`, and `jest-environment-jsdom` as used by the Backstage CLI were bumped to version 29. This is up from version 27, so check out both the and (later ) migration guides, since your existing tests may be affected. Particular changes that were encountered in the main Backstage repository are: The updated snapshot format. `jest.useFakeTimers('legacy')` is now `jest.useFakeTimers({ legacyFakeTimers: true })`. Error objects collected by `withLogCollector` from `@backstage/test-utils` are now objects with a `detail` property rather than a string. Newly created Backstage repositories now use the stable version 6 of `react-router`, just like the main repository does. Migrating to the stable version of `react-router` is optional for the time being; Backstage has support for both versions. But if you want to do the same for your existing repository, please follow . Support for the beta version will be removed in a later release. The Backstage CLI now has built-in support for `mocks` and `testUtils` directories in your code. These can be used for mocks and shared utilities in tests. The bazaar-backend `createRouter` function now requires that the `identityApi` is passed to the router. This has been deprecated and split into `@backstage/plugin-catalog-backend-module-bitbucket-cloud` and `@backstage/plugin-catalog-backend-module-bitbucket-server`, for BitBucket Cloud and BitBucket Server respectively. Please update your dependencies accordingly, depending on which product you use. The original package will be removed in a future release. Contributed by in This release does not contain any security fixes. 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 . Below you can find a list of links and references to help you learn about and start using this new release. , , and Backstage's for discussions and support Backstage , , and Sign up for our if you want to be informed about what is happening in the world of Backstage.