Migrating to Hasura Auth v2.45.3
Version v2.45.3 introduces 1 breaking change. This guide details how to update your code.
Released: 7/28/2025
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
run_sql API (Postgres)Connection Details page (Console)Nested Inherited Roles Permission Logic (Server)Breaking Changes
●Issue #1
Permissions propagation through nested inherited roles is now strictly enforced for both queries and mutations. If your application relied on previously bypassed session variable requirements for mutations involving deeply nested inherited roles, those mutations might now fail or require explicit session variables (like X-Hasura-User-Id) to pass permission checks.
Migration Steps
- 1If using nested inherited roles in mutations, ensure that necessary session variables (which might have been implicitly bypassed before) are explicitly provided in the mutation context to satisfy the now strictly enforced permission constraints.
Release Summary
This patch release fixes critical security issues related to nested inherited role permission propagation and resolves a bug in the Console's database editing interface. It also introduces an option to run SQL outside transactions via the server API.
Need More Details?
View the full release notes and all changes for Hasura Auth v2.45.3.
View Full Changelog