Backstage v1.55.0 Overhauls Scaffolder Workspaces and Hardens Catalog Relations

The CNCF Backstage project has released v1.55.0, delivering a collection of breaking architecture changes, permission hardening, and cleanup across the Software Catalog and Scaffolder subsystems. The update completely eliminates the catalog.enableRelationsCompatibility layer and legacy target field in favor of targetRef, while removing legacy processors like CodeOwnersProcessor and AnnotateScmSlugEntityProcessor. Crucially for Scaffolder workflows, workspace serialization for task recovery now demands explicit external workspace provider modules (such as GCP storage modules or a database-backed development module). Additionally, inline template dry runs now actively enforce templateDryRunPermission policies. This release is critical for internal developer platform (IDP) maintainers because it fundamentally alters how task resilience and state storage are managed at scale. Previously, task workspace snapshots were bundled with legacy database storage, often creating storage bloat and performance bottlenecks in high-throughput environments. By mandating dedicated external workspace modules for production and enforcing stricter Scaffolder permission boundaries, the project ensures that internal self-service capabilities cannot bypass tenant isolation policies or exhaust cluster database capacity. The shift fits into a broader industry drive toward enterprise-grade platform engineering governance. As internal developer portals transition from experimental developer directories into mission-critical orchestration layers, operational loose ends—such as unbounded ephemeral workspace storage and permissive dry-run endpoints—must be eliminated. The modularization of Scaffolder backend storage mirrors the CNCF ecosystem's wider decoupling of stateful task engines from stateless API gateways, matching the expectations of large-scale Kubernetes deployments. For platform engineers and SREs adopting v1.55.0, the upgrade requires direct configuration updates. Teams relying on Software Template dry runs must explicitly grant scaffolder.template.dry-run in their custom permission policies to avoid breaking developer workflows. Furthermore, platform administrators must provision and register a supported external workspace module before deploying the backend, as the Scaffolder will now reject uninstalled workspace providers. Custom plugins that still parse relation entities must also be audited to ensure compliance with targetRef.