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

id: v1.14.0 title: v1.14.0 description: Backstage Release v1.14.0 These are the release notes for the v1.14.0 release of . A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for their hard work in getting this release developed and done. This release has an important security fix, along with a lot of squashed bugs and exciting additions! Enjoy. Theres been further work made on the OpenAPI tooling! One of the changes is that the commands for this feature are grouped under a `schema openapi` subcommand. This lets us structure things a bit better for the future. The generated file now also has a `.generated.ts` extension, to more easily be able to keep it apart in linting and similar. Theres been some awesome additions made to the Kubernetes plugin, including the ability to show pod logs! To support this, some breaking changes were made in some of its interfaces. Check out for some details of what changed. We are preparing for React 18, and as part of doing that, we are now officially deprecating support for React 16. Nothing will break for you just yet, but if you are still on React 16 your `backstage-cli` commands will start to show helpful warning messages guiding you to bump to version 17 when you can. See for some details about this, and links to the relevant issues. This plugin is focused on integrators rather than end users. It allows you to see useful information about your Backstage installation, such as what operating system and NodeJS version its running on, what Backstage and individual package versions you have, and more! This may serve as a foundation for adding even more ops focused features in the future. Contributed by in Theres been work done under the hood to migrate AWS features over to using v3 of their client

While this should mostly go below the radar and ultimately work the same as it did before, do reach out to us if you encounter any problems that might be related to this migration. Theres actually a minor interface breakage as part of this, where `AwsIamKubernetesAuthTranslator` has some methods removed, but thats one which may not have a lot of use outside of the package. Contributed by , see PRs linked at the bottom of issue For auth providers that use session storage, those sessions are now persisted in the auth backend database, instead of in local memory. This should make session handling work better across scaled auth backend instances. You can now output Markdown from the Software Template runs which can provide more data to the end user after a job has completed in the outputs section of `scaffolder/next` Contributed by in The configuration loading system has been refactored to make it easier to extend the system with additional sources of configuration. See the and the for more details. We found some hotspots in the catalog database operations, and streamlined them. Hopefully this should be noticeable in the form of slightly lower CPU and IOPS usage. A used by the Scaffolder plugin was patched by our automated security processes in . The fixed version of `vm2` was already covered by the required version range of the Scaffolder plugin, so adopters are able to address this vulnerability separately without upgrading Backstage itself, as part of their regular security processes. 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.