Backstage 1.55.0: Scaffolder Recovery and the Elasticsearch 8 Wall
Sources
Backstage v1.55.0 brings a mix of highly requested stability features and some aggressive dependency breaks that will make SREs sweat.
The Win: Scaffolder Task Recovery
The new task recovery configuration is a massive win. Previously, if a scaffolder task crashed or timed out, the entire process was lost, forcing the user to start from the beginning. The new system enables automatic recovery from the last completed step and persists step outputs. For complex templates (e.g., those involving multi-repo creation and CI setup), this removes a significant point of friction and improves the developer experience.
The Catch: The Elasticsearch 8 Wall
The @backstage/plugin-search-backend-module-elasticsearch has been upgraded to the Elasticsearch 8 client, requiring at least version 8.19. Elasticsearch 7.x clusters are no longer supported. This is a "dependency wall"—a forced upgrade that breaks backward compatibility with legacy search clusters. For organizations with locked-down infrastructure or shared ES clusters, this update is a blocking event that requires a coordinated cluster migration before the Backstage upgrade can occur.
Operational Impact
The transition to normalized responses for search providers (exposing hits, total, and took) simplifies the backend code but will break any custom plugins relying on raw client types. Expect a round of "fix-the-types" commits across your custom plugins.