Skip to content

Update Backstage to 1.49.0#211

Open
heyLu wants to merge 10 commits intomainfrom
update
Open

Update Backstage to 1.49.0#211
heyLu wants to merge 10 commits intomainfrom
update

Conversation

@heyLu
Copy link
Copy Markdown
Member

@heyLu heyLu commented Mar 18, 2026

The update itself was easy, but then I decided to do a bunch more maintenance in here:

  • update yarn and node version used in CI
  • fix some yarn peer dependency warnings
  • start migrating to @backstage/ui

heyLu added 4 commits March 18, 2026 14:21
Using `yarn backstage-cli versions:bump` + `yarn dedupe`.
Basically cb5fe58 again, without the version bump `yarn tsc` fails with
mysterious errors like the one from below:

```
$ yarn tsc
plugins/s3-viewer-backend/src/permissions/rules.ts:9:3 - error TS2769: No overload matches this call.
  Overload 1 of 2, '(rule: { name: string; description: string; resourceRef: PermissionResourceRef<BucketDetails, BucketDetailsFilter, "s3-viewer.bucket", "s3-viewer">; paramsSchema?: ZodType<...> | undefined; apply(resource: BucketDetails, params: undefined): boolean; toQuery(params: undefined): PermissionCriteria<...>; }): PermissionRule<...>', gave the following error.
    Type 'ZodObject<{ owners: ZodArray<ZodString>; }, $strip>' is missing the following properties from type 'ZodType<undefined, ZodTypeDef, undefined>': _type, _parse, _getType, _getOrReturnCtx, and 7 more.
  Overload 2 of 2, '(rule: PermissionRule<unknown, unknown, string, undefined>): PermissionRule<unknown, unknown, string, undefined>', gave the following error.
    Type 'ZodObject<{ owners: ZodArray<ZodString>; }, $strip>' is missing the following properties from type 'ZodType<undefined, ZodTypeDef, undefined>': _type, _parse, _getType, _getOrReturnCtx, and 7 more.

9   paramsSchema: z.object({
```

This matches the same change done upstream in backstage/backstage#33399.
@heyLu heyLu self-assigned this Mar 18, 2026
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Mar 18, 2026

⚠️ No Changeset found

Latest commit: 3384e6b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

"stream": "^0.0.2",
"yn": "^4.0.0",
"zod": "^3.25.76"
"zod": "^3.25.76 || ^4.0.0"
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This came up again, same as in cb5fe58, but caused by the corresponding update in Backstage to support 3 & 4 and the zod/v3 import change above.

heyLu added 5 commits March 18, 2026 16:33
These are often pointed out by `yarn`, let's take care of them a bit:

```
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
```
With this, the complaints are now down to the following, which likely
can't be fixed until backstage/backstage#31467
is done and MUI can be fully swapped out for `@backstage/ui`.

```
$ yarn install
➤ YN0000: · Yarn 4.13.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 860ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ @types/react is listed by your project with version 18.3.12 (p1d31cb), which doesn't satisfy what @material-ui/core and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @types/react is listed by your project with version 18.3.12 (p26f131), which doesn't satisfy what @material-ui/core and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @types/react is listed by your project with version 18.3.12 (pceee16), which doesn't satisfy what @material-ui/core and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 18.3.1 (paf9857), which doesn't satisfy what @material-ui/core and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 18.3.1 (pd98da7), which doesn't satisfy what @material-ui/core and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 18.3.1 (pe57dd5), which doesn't satisfy what @material-ui/core (via @backstage/test-utils) and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 18.3.1 (p372b25), which doesn't satisfy what @material-ui/core (via @backstage/test-utils) and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 18.3.1 (pb78d45), which doesn't satisfy what @material-ui/core and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 18.3.1 (pe66cc4), which doesn't satisfy what @material-ui/core and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 18.3.1 (pfa8000), which doesn't satisfy what @material-ui/core and other dependencies request (but they have non-overlapping ranges!).
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 2s 401ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 1s 287ms
➤ YN0000: · Done with warnings in 4s 808ms
```
The demo app still uses the old `Grid`, but our stuff is now using the
`@backstage/ui` one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant