v1.27.0-next.2

See docs/releases/v1.27.0-next.2-changelog.md for more information.

v1.26.5

This release fixes an issue where it was not possible to mock and require the original @backstage/core-components package in Jest tests. It also fixes an issue where the scaffolder had inconsistent log output formats, along with support for redacting additional meta fields in both the default logger and scaffolder logger.

v1.27.0-next.1

See docs/releases/v1.27.0-next.1-changelog.md for more information.

v1.26.4

This release fixes several issues related the new authentication system:

• TechDocs will now work as intended when deploying the backend using the old backend system.
• The default SignInPage will now allow guest auth even if it's not able to reach the backend.
• The TechDocs CLI now mocks the correct authentication endpoint, fixing a 404 error when previewing documentation.
• The search collators for the catalog and explore plugins will now properly authenticate requests when deployed with the new backend system.
• The JWKS endpoint used for cross-plugin authentication is now available immediately upon creation, avoiding 503 errors during startup when trying to fetch remote keys.

v1.27.0-next.0

See docs/releases/v1.27.0-next.0-changelog.md for more information.

v1.26.3

This release is the official (for real this time, we missed some plugins) start of the community-plugins repository! 🎉

Out of the back of the discussions in #20266, we aligned with the help of RedHat to move some plugins which are maintained by the community out of this repo, and have a dedicated space. There they will have their own independent workspaces, with their own release cycles not coupled to the Backstage mainline / next release.

With the move comes a new NPM scope, @backstage-community. Upgrading to these packages is as easy as running yarn backstage-cli versions:bump followed by yarn backstage-cli versions:migrate, in which these scripts will update both code references under ./src and package.json references to the old namespace.

If you have already upgraded to v1.26.1 make sure to run yarn backstage-cli versions:bump --skip-migrate and then yarn backstage-cli versions:migrate separately in order to take advantage of the inline code replacements that shipped in this release!

From this release versions:bump will also try to migrate any packages over time for you, without needing to do versions:migrate separately.

Please reach out on Discord, or file an issue, if you're having issues with moving to the new packages.

v1.26.2

This release is the official start of the community-plugins repository! 🎉

Out of the back of the discussions in #20266, we aligned with the help of RedHat to move some plugins which are maintained by the community out of this repo, and have a dedicated space. There they will have their own independent workspaces, with their own release cycles not coupled to the Backstage mainline / next release.

With the move comes a new NPM scope, @backstage-community. Upgrading to these packages is as easy as running yarn backstage-cli versions:bump followed by yarn backstage-cli versions:migrate, in which these scripts will update both code references under ./src and package.json references to the old namespace.

If you have already upgraded to v1.26.1 make sure to run yarn backstage-cli versions:bump --skip-migrate and then yarn backstage-cli versions:migrate separately in order to take advantage of the inline code replacements that shipped in this release!

From this release versions:bump will also try to migrate any packages over time for you, without needing to do versions:migrate separately.

Please reach out on Discord, or file an issue, if you're having issues with moving to the new packages.

v1.26.1

This release deprecates @backstage/plugin-todo and @backstage/plugin-todo-backend has they have now been moved to the @backstage-community/* namespace over in the community-plugins repository.

You should be able to do yarn backstage-cli versions:bump if you're already on v1.26.0+ of Backstage.
Otherwise, you can do do yarn backstage-cli versions:bump followed by yarn backstage-cli versions:migrate to switch over to the new packages, if you're on versions <v1.26.0

v1.26.0

See docs/releases/v1.26.0-changelog.md for more information.

v1.26.0-next.1

See docs/releases/v1.26.0-next.1-changelog.md for more information.