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

id: v1.1.0 title: v1.1.0 description: Backstage Release v1.1.0 These are the release notes for the v1.1.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 auth and received a few BREAKING changes. You are now required to always return a `token` from the result of a sign-in resolver, and all default sign-in resolvers have been removed. This means that you will have to make a conscious choice to use one of a few predefined resolver functions to be able to use a given auth provider for signing in, or to write your own. Dont worry, its actually rather straightforward to do, and ends up clarifying responsibilities for safe authentication and catalog ownership. There are also a number of deprecations among the exported auth backend types, which you may want to adapt to. For more information, see the relevant about sign-in resolvers, and the / changelogs. The has bumped the `jest` version from `^26.0.1` to `^27.5.1`. You can find the complete list of breaking changes . We strongly recommend having completed the before upgrading to this version, as the package roles are used to automatically determine the testing environment for each package. Note that one of the breaking changes of Jest 27 is that the `jsdom` environment no longer includes `setImmediate` and `clearImmediate`, which means you might need to update some of your frontend packages. Another notable change is that `jest.useFakeTimers` now defaults to the `'modern'` implementation, which also mocks microtasks. The has a BREAKING change, in that cluster suppliers now need to cache their results to allow frequent calls to their methods. This was done to pave the way for custom suppliers that dynamically fetch results from the real authority, instead of hard coding them in config. Thanks ! () The permission related packages received a number of BREAKING changes. Among other things, the names of types were settled to be made more crisp and clear. This will mostly apply to those who write custom permissions. This all goes to the , , and packages, whose changelogs are linked here. Theres a new Stack Overflow plugin with a corresponding ! The now has GitLab support, through the new . Thanks ! () The catalog added a new `AwsS3EntityProvider` as a replacement for the `AwsS3DiscoveryProcessor`. Thanks ! () The permissions-related exports from the catalog backend have some . These are all in alpha still, so this only applies to you if you are developing catalog permissions and import from `@backstage/plugin-catalog-backend/alpha`. 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.