Hasura released version v2.49.0 of its GraphQL Engine, bringing several notable changes for both on‑premise and cloud users.
Relay API becomes stable
The Relay endpoint is now promoted to a stable path /v1/relay and the previous /v1beta1/relay endpoint is deprecated. A new flag, --enable-relay (environment variable HASURA_GRAPHQL_ENABLE_RELAY), lets you turn the Relay API on or off. The default setting is true for Community and Enterprise deployments (to preserve backward compatibility) and false for Hasura Cloud, where it must be enabled manually via project settings.
Eventing subsystem can be disabled
A fresh environment variable HASURA_GRAPHQL_DISABLE_EVENTING and CLI flag --disable-eventing give you the ability to disable the entire eventing stack—including event triggers, scheduled events, the cron generator, and async actions—in OSS/single‑tenant builds. This mirrors a control that was previously exclusive to multi‑tenant cloud deployments. The cli-migrations v2 and v3 entrypoints automatically set this flag on their temporary HGE instance, preventing migration jobs from competing with eventing pollers for database resources.
Schema memory usage improvements
Internal enhancements reduce the memory footprint of the GraphQL schema, which can be beneficial for large schemas or constrained environments.
MariaDB mutation fix (Enterprise/Cloud only)
The Data Connector now correctly handles update and delete mutations on MariaDB. The fix ensures that temporary tables used during the mutation lifecycle are created, used, and dropped on the same JDBC connection, eliminating the “Table ‘temp_table_xxx' doesn't exist” error that occurred when a different pooled connection was used.
These updates make Hasura more flexible for developers who need fine‑grained control over memory consumption and background processes, while also improving reliability for MariaDB users.