Hey, @akarmes! Welcome 
You’re seeing that warning because Vercel wants the packageManager field defined in your root package.json, so make sure you have something like "packageManager": "pnpm@10.22.0". If that still causes issues, try pinning to an earlier pnpm v10 release. v10 is still pretty new, and some versions are a bit finicky in Vercel’s build environment.
It can also help to regenerate your lockfile: delete pnpm-lock.yaml and node_modules, then run a fresh pnpm install locally so the lockfile matches the version you’re declaring.
If you need things working right away, sticking with pnpm v9 is the safer option for now. v10’s new features (including trustPolicy) are nice, but if they’re blocking deploys, v9 tends to be more stable on Vercel at the moment.