Note

We need to wait until the bugs are worked out of Zenstack v3. There is a lot of potential here but the Issues list is long and is still growing daily. I ran into 3 new bugs in the initial attempt to upgrade and the work-arounds were difficult to maintain.

Issue blocking TestPlanIt from upgrading to Zenstack v3:

• zenstackhq/zenstack#2538
• zenstackhq/zenstack#2612

Why we're upgrading

ZenStack v2 is no longer actively maintained. The team has shifted focus to v3 and won't be tracking Prisma version updates on v2. v3 replaces Prisma's runtime with a pure TypeScript ORM built on Kysely, offering better performance, simpler deployment (no Rust/WASM), and a typed query builder for complex queries.

What needs to be done

• Review breaking changes documentation
• Update ZenStack packages to v3 (@zenstackhq/cli@next, @zenstackhq/orm@next)
• Rename/migrate schema files as needed
• Update any code using deprecated v2 APIs (e.g., withPolicy → enhance)
• Test all CRUD operations and access policies
• Verify TanStack Query hooks still function correctly
• Test against staging database before production deployment

No data migration required — database schema is compatible.