--- id: v1.50.0 title: v1.50.0 description: Backstage Release v1.50.0 --- These are the release notes for the v1.50.0 release of [Backstage](https://backstage.io/). A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done. ## Highlights ### **BREAKING**: Identity token ownership claim removed by default The `auth.omitIdentityTokenOwnershipClaim` setting now defaults to `true`. Backstage user tokens issued by the `auth` backend will no longer contain the `ent` claim with the user's ownership entity refs. This means tokens in large organizations no longer risk hitting HTTP header size limits. To get ownership info for the current user, code should use the `userInfo` core service. The setting can still be set back to `false` if needed, but it will be removed entirely in a future release. ### **BREAKING**: Standard Schema for new frontend system extension config The new frontend system now uses [Standard Schema](https://github.com/standard-schema/standard-schema) for extension configuration. A new `configSchema` option has been added to `createExtension`, `createExtensionBlueprint`, as well as the `override` and `makeWithOverrides` methods on extension definitions and blueprints. This option accepts direct schema values from any Standard Schema compatible library with JSON Schema support, replacing the old `config.schema` callback format which is now deprecated. To use the new `configSchema` option with Zod, you need Zod v4 (`zod@^4.0.0`): ```ts import { z } from 'zod'; ``` Note that neither direct Zod v3 schemas nor the `zod/v4` subpath export from the Zod v3 package are supported by the new `configSchema` option. While the `zod/v4` subpath exposes the Zod v4 API surface, the resulting schema objects do not support the JSON Schema conversion that `configSchema` requires. A full migration to the `zod` v4 package is needed. Direct Zod v3 schemas only work with the deprecated `config.schema` callback format. The deprecated `createSchemaFromZod` helper has been removed from `@backstage/frontend-plugin-api`. See the [1.50 migration documentation](https://backstage.io/docs/frontend-system/architecture/migrations#150) for more information. ### **BREAKING**: Backstage UI updates There are several new additions in Backstage UI, including a new `Badge` component for non-interactive labeling, a `RangeSlider` for numeric range selection, a `CheckboxGroup` component, and a `showPaginationLabel` prop for controlling pagination label visibility in tables. The `TableBodySkeleton` has been exported for use outside the built-in `Table`, and `SearchAutocomplete` now adapts its background based on its parent container. The `useTable` complete mode now supports disabling pagination via `paginationOptions: { type: 'none' }`. Tabs now respect `prefers-reduced-motion` for indicator animations, and form field descriptions are now properly connected to inputs via `aria-describedby` for screen reader accessibility. The `RangeSlider` component was contributed by [@AmbrishRamachandiran](https://github.com/AmbrishRamachandiran) in [#33112](https://github.com/backstage/backstage/pull/33112). There are also several breaking changes to note: - **Header tabs**: The `tabs` prop now uses `HeaderNavTabItem[]` instead of `HeaderTab[]`. Tabs render as a `