Conversation
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
commented
Mar 18, 2026
| "stream": "^0.0.2", | ||
| "yn": "^4.0.0", | ||
| "zod": "^3.25.76" | ||
| "zod": "^3.25.76 || ^4.0.0" |
Member
Author
There was a problem hiding this comment.
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.
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.
Contributor
|
Hi @heyLu - Any updates on this? We just tried to go from 1.48 to 1.53 and this plugin causes the entire app to blow up, pretty sure it started even going to 1.49 - but hard to scale back. I haven't investigated too far just finally (after a long while) figured out which plugin was causing it. Seemed to be more related to the backend side too. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The update itself was easy, but then I decided to do a bunch more maintenance in here:
yarnandnodeversion used in CIyarnpeer dependency warnings@backstage/ui