Prisma just released a new version 5.16.0, and this probably came with some changes to their internal types that Zenstack relied upon. When running zenstack with prisma@5.16.0, I run into this bug:
Right now, the solution is just to stick to the previous version of Prisma (v5.15.1) which is completely fine. Just wanted to let the devs of this amazing library in-the-know that it's would break for anyone trying to spin up a new project with latest versions.
Environment (please complete the following information):
Description and expected behavior
Prisma just released a new version
5.16.0
, and this probably came with some changes to their internal types that Zenstack relied upon. When running zenstack with prisma@5.16.0, I run into this bug:Right now, the solution is just to stick to the previous version of Prisma (v5.15.1) which is completely fine. Just wanted to let the devs of this amazing library in-the-know that it's would break for anyone trying to spin up a new project with latest versions.
Environment (please complete the following information):