Two weeks later, we are at the RLS release, which brings us to 75% of the way toward the v1 release! With this new release, you can: - Simply use an array in the third parameter for constraints, policies, etc. (The old API is still available but deprecated) - Manage roles - Manage policies - Enable/disable RLS on tables - Enable/disable RLS on views - Customize role management in drizzle.config.ts for push/pull workflows One of the great things we've accomplished in this release is starting to provide specific import paths to database providers and the community, allowing them to bring their helpers into Drizzle. In this release, we've introduced: 1. "drizzle-orm/neon" for @neondatabase, with a set of predefined roles and a wrapper function for policies built by the Neon team to enhance your developer experience. 2. "drizzle-orm/supabase" for @supabase, which includes predefined roles and predefined tables such as "auth.users" and others, allowing you to reference them natively with Drizzle! Huge shoutouts to @rphlmr for helping us test Supabase+Drizzle RLS and for building a great showcase repo: github.com/rphlmr/drizzle… It also includes a great wrapper, "createDrizzle", that can handle all the transactional work with Supabase for you. In upcoming releases, it will be moved to "drizzle-orm/supabase", allowing you to use it natively. Huge shoutouts to @L_Mario564 for closing over 300 stale and fixed issues from the drizzle-orm repo, properly marking all existing issues with appropriate labels and comments, and for cleaning up the drizzle-kit-mirror package and moving all the issues to the main drizzle-orm package Next are RQB v2 and the updated migration flow with rollbacks, which will bring us to 85% and 95%, respectively
