Managing upgrades with pnpm and handling unmet peer dependency warnings

How do you guys manage upgrades to effect in your projects? I'm using pnpm, and whenever I upgrade

effect

effect

and family, I get a ton of "unmet peer" dependency warnings. Here's one simple example:

packages/apiimpl-data-save
└─┬ @effect/platform 0.55.1
  └── ✕ unmet peer @effect/schema@^0.67.14: found 0.66.14

packages/apiimpl-data-save
└─┬ @effect/platform 0.55.1
  └── ✕ unmet peer @effect/schema@^0.67.14: found 0.66.14

I could add

@effect/schema

@effect/schema

as a peer dependency explicitly, but the list of deps I'd need to add seems to be pretty deep! What's the best approach?

How do you guys manage upgrades to effect in your projects? I'm using pnpm, and whenever I upgrade

effect

effect

and family, I get a ton of "unmet peer" dependency warnings. Here's one simple example:

packages/apiimpl-data-save
└─┬ @effect/platform 0.55.1
  └── ✕ unmet peer @effect/schema@^0.67.14: found 0.66.14

packages/apiimpl-data-save
└─┬ @effect/platform 0.55.1
  └── ✕ unmet peer @effect/schema@^0.67.14: found 0.66.14

I could add

@effect/schema

@effect/schema

as a peer dependency explicitly, but the list of deps I'd need to add seems to be pretty deep! What's the best approach?