●Change8

v2.49.0

📦 hasura-authView on GitHub →
✨ 4 features🐛 1 fixes⚡ 1 deprecations🔧 6 symbols

Summary

This 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.

Migration Steps

  1. If you rely on the `/v/1beta1/relay` endpoint, update your clients to use the stable `/v1/relay` endpoint.
  2. If running Hasura Cloud, you may need to manually enable the Relay API in project settings if you require it, as the default is now `false`.

✨ New Features

  • Promoted Relay API to stable `/v1/relay` endpoint.
  • Added the `--enable-relay` (or `HASURA_GRAPHQL_ENABLE_RELAY`) flag to enable/disable the Relay API, defaulting to `true` in Community/Enterprise and `false` in Cloud.
  • Added `HASURA_GRAPHQL_DISABLE_EVENTING` environment variable (and `--disable-eventing` CLI flag) to disable the entire eventing subsystem (event triggers, scheduled events, cron event generator, async actions) on OSS/single-tenant builds.
  • The `cli-migrations` v2 and v3 entrypoints now set the disable-eventing flag on temporary HGE instances.

🐛 Bug Fixes

  • Fixed MariaDB update/delete mutations failing with 'Table 'temp_table_xxx' doesn't exist' by ensuring the CREATE, mutation, and DROP lifecycle for temporary tables runs pinned to a single JDBC connection.

Affected Symbols

/v1/relay/v/1beta1/relay--enable-relayHASURA_GRAPHQL_ENABLE_RELAYHASURA_GRAPHQL_DISABLE_EVENTING--disable-eventing

⚡ Deprecations

  • The `/v/1beta1/relay` endpoint is deprecated in favor of the stable `/v1/relay` endpoint.