Hasura Auth
Backend & InfraBlazing fast, instant realtime GraphQL APIs on all your data with fine grained access control, also trigger webhooks on database events.
Release History
View all versions →v2.50.13 fixes2 featuresThis patch release for v2.50 introduces opt-in logging redaction for various triggers and handlers, and improves the behavior of the @cached directive when the Redis store is unavailable. It also fixes a critical SSO login issue in the Console and addresses security vulnerabilities in the data connector.
v2.50.0Breaking6 fixes4 featuresThis patch release for v2.50 includes critical security fixes for the mssql backend and CLI dependencies, alongside improvements to async actions and event trigger validation. It also addresses compatibility issues with FIPS-enabled hosts and restores previous naming conventions as the default.
v2.45.8Breaking5 fixes1 featureThis patch release addresses critical security vulnerabilities in the super-connector and frontend dependencies, alongside important bug fixes for the MSSQL backend and Postgres SSL connections on FIPS-enabled hosts.
v2.49.52 fixes2 featuresThis patch release for v2.49 includes server-side improvements like the addition of `x-request-id` header in error responses and new jsonb path filter operators. It also addresses bug fixes in the console and CLI, and updates dependencies to remediate security vulnerabilities.
v2.45.61 fixThis is a patch release for v2.45. It includes a bug fix by upgrading openssl in the ubuntu base image to address CVE-2026-45447.
v2.49.4Breaking1 fix5 featuresThis patch release introduces idempotency for server migrations, adds queue size limiting and monitoring for WebSockets, and introduces stricter JWT validation options. It also removes support for the deprecated X-Hasura-Access-Key header.
v2.49.32 fixes1 featureThis patch release for v2.49 introduces a new configuration option to selectively disable event processing pollers and includes security updates across the Server, Data Connector, and Build components.
v2.45.58 fixesThis is a patch release for v2.45, primarily addressing a high-severity security vulnerability and fixing several bugs related to data connectors, event triggers, and JSON parsing robustness.
v2.49.23 fixes2 featuresThis patch release addresses a high-severity security vulnerability and introduces granular transaction control for SQL migrations via the CLI. It also adjusts how malformed JSON containing control characters is handled to maintain compatibility for some legacy clients.
v2.49.13 fixesThis is a patch release for v2.49, focusing on server stability by fixing event trigger shutdown issues and mitigating DoS vectors.
v2.49.01 fix4 featuresThis patch release stabilizes the Relay API to /v1/relay and introduces granular control over enabling Relay and disabling the entire eventing subsystem via new configuration flags.
v2.45.4Breaking25 fixes3 featuresThis patch release (v2.45) introduces several bug fixes across server components, data connectors, and the Console, alongside minor performance improvements and configuration options for Redis pooling. Notably, it now errors on previously silent remote schema/action type conflicts.
v2.48.161 fixThis is a patch release for v2.48, primarily addressing a bug in server metric reporting.
v2.48.151 fixThis is a patch release for v2.48, primarily addressing a bug in MariaDB data connector mutations.
v2.48.141 fixThis is a patch release for v2.48, primarily addressing a performance issue in Oracle introspection.
v2.48.132 fixesThis is a patch release for v2.48, primarily addressing server-side consistency in OpenTelemetry reporting and fixing a bug related to EKG gauge behavior for active subscriptions.
v2.48.124 fixesThis is a patch release focused on fixing performance issues in the server and resolving several critical bugs related to event triggers and data connector operations, particularly concerning self-referencing tables and nullable updates.
v2.48.113 fixesThis is a patch release for v2.48, primarily focusing on server-side bug fixes and container base image/tool upgrades.
v2.48.102 fixes2 featuresThis patch release for v2.48 includes performance improvements for BigQuery schema introspection and fixes a bug in the Console's table schema editor. New configuration options for Redis connection pooling were also added for Enterprise users.
v2.48.93 fixesThis patch release for v2.48 includes several bug fixes across the Server and Console components, notably improving connection handling and resolving permission saving issues.
v2.48.6Breaking2 fixesThis patch release for v2.48 includes support for Postgres 17, fixes schema mixing issues in remote joins, and improves streaming subscription reliability on non-unique columns for supported databases.
v2.48.52 fixesThis is a patch release (v2.48) focused on improving security by sanitizing logs and enhancing JWK compatibility.
v2.48.43 fixesThis is a patch release (v2.48) focusing on fixing issues related to OpenAPI specification generation, subscription handling, and JWK parsing, with an enterprise-specific configuration update for JDBC authentication.
v2.48.32 fixesThis is a patch release for v2.48, primarily containing bug fixes and improvements related to server-side data handling and BigQuery integration.
v2.48.23 fixesThis is a patch release (v2.48) focusing on bug fixes and improvements across the Server and Console components, particularly around schema description handling and remote schema modification.
Common Errors
FatalError1 reportA "FatalError" in Hasura Auth often stems from configuration mismatches or unmet dependencies during server startup, especially when experimental features are enabled. Clear your Hasura Auth metadata, ensuring the database connection string is valid, and double-check that experimental feature flags are correctly spelled and supported by your Hasura Auth version. If using experimental features, ensure all required dependencies are installed and correctly configured.
InternalServerError1 reportThe "InternalServerError" in hasura-auth often arises from unexpected responses (like empty or non-JSON) from external APIs it relies on for authentication or user management. To fix this, implement robust error handling, specifically checking for and gracefully handling 204 No Content responses or invalid JSON from upstream services by either returning a valid default response or retrying with exponential backoff. Additionally, add logging to capture the exact problematic response for debugging.
Related Backend & Infra Packages
Production-Grade Container Scheduling and Management
Node.js JavaScript runtime ✨🐢🚀✨
Promise based HTTP client for the browser and node.js
A modern runtime for JavaScript and TypeScript.
Deliver web apps with confidence 🚀
Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
Subscribe to Updates
Get notified when new versions are released