Backstage v1.50.0-next.1 is now available, bringing incremental improvements to the CNCF’s de facto developer portal standard. Released March 31, 2026, this preview release focuses on UI consistency, entity modeling fixes, and preparations for the broader 1.50 stable release.
New Props and Component Improvements
Table Pagination Labels
The TablePagination component now accepts a showPaginationLabel prop, giving developers more control over pagination visibility in data-intensive plugins. Prior to this release, pagination labels were always visible, which could clutter dense tables. Now teams can customize the UI based on their specific needs.
PageLayout titleLink Prop
Page layouts now support a titleLink prop on PageLayoutProps, allowing plugin headers to link back to root pages. This improves navigation in deep plugin hierarchies where users frequently need to return to parent sections. The enhancement addresses a common UX friction point in complex Backstage instances.
Entity Relation Cards Fix
The entity relation cards component now properly displays multiple entities when a relationship type has many entries. Previously, only one entity was shown in certain edge cases, which was a significant limitation for organizations with complex entity graphs. This fix resolves a long-standing issue where related resources were effectively hidden from users.
BUI Migration Continues
Backstage’s UI component migration from Material-UI to Backstage UI (BUI) continues with TechDocs. TechDocs alpha plugin pages now use the BUI header system, with fixed relative href resolution in BUI link components. The migration removes unnecessary dependencies from create-app templates, improving initial installation times.
The BUI migration reduces bundle sizes and aligns components with the broader Backstage design system, but requires attention when upgrading custom plugins that depend on Material-UI specific styling or component behaviors. Teams should audit their custom plugins for dependencies on deprecated Material-UI patterns.
Security and Auth Fixes
OIDC authentication sees a targeted fix: loopback redirect URI matching now allows any port. This resolves issues with dynamic port allocation during local development flows, where OAuth providers would reject callbacks to random development ports. The change improves developer experience without compromising security.
Upgrade Path to v1.50
For existing Backstage adopters, upgrading involves three key considerations. First, update dependencies using the backstage-cli versions command. Second, review Link component usage in custom plugins, as BUI link components now handle resolution differently with explicit absolute paths required. Third, test entity relations thoroughly, as the fix may uncover previously hidden entities in your catalog.
The Road to 1.50 Stable
The Backstage versioning strategy maintains a two-track release pattern. Stable releases receive monthly patch releases with bug fixes and security patches. Next releases provide weekly previews of upcoming major features. Organizations with mission-critical portals should remain on stable releases, while teams building new functionality or testing upcoming features should use the release next flag for early access.
Backstage has reached a maturity point where the core value proposition, a single place for all your software, is now table stakes. The evolution in v1.50 reflects a focus on polish, accessibility, and the developer experience of platform teams themselves. Rather than major new features, this release rounds rough edges and addresses community feedback accumulated through production usage.
Sources
- Backstage v1.50.0-next.1 Release Notes (GitHub, Mar 31, 2026)
- Backstage v1.49.0 Release Documentation