paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 33 Packages Projects Releases Wiki Activity

docs: improve v1.50 release notes for Standard Schema section

Browse Source 
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
Made-with: Cursor
This commit is contained in:
Patrik Oldsberg
2026-04-16 10:30:23 +02:00
parent d57f36e2b8
commit 2ffddef1dd
1 changed files with 16 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/releases/v1.50.0.md
+16 -2
View File
@@ -16,9 +16,23 @@ The `auth.omitIdentityTokenOwnershipClaim` setting now defaults to `true`. Backs
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 replaces `createSchemaFromZod`
### **BREAKING**: Standard Schema for new frontend system extension config
The deprecated `createSchemaFromZod` helper has been removed from `@backstage/frontend-plugin-api`. A new `configSchema` option for `createExtension` and `createExtensionBlueprint` accepts direct schema values from any [Standard Schema](https://github.com/standard-schema/standard-schema) compatible library with JSON Schema support, such as zod v4 or the `zod/v4` subpath from zod v3. Note that direct zod v3 schemas are not supported by the new option — use `import { z } from 'zod/v4'` from the zod v3 package, or upgrade to zod v4.
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 or the `zod/v4` subpath export from the Zod v3 package. The `zod/v4` subpath requires a minimum Zod version of **3.25.0** — make sure to update your Zod dependency if needed:
```ts
// Either use Zod v4 directly:
import { z } from 'zod';
// Or the v4 subpath from the Zod v3 package (requires zod@^3.25.0):
import { z } from 'zod/v4';
```
Note that direct Zod v3 schemas are **not** supported by the new `configSchema` option — they 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.