This release includes 1 breaking change for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+8 more
Affected surfaces
ReleasePort's take
Light signalThe Relay API is promoted to stable at `/v1/relay` while deprecating the beta endpoint, and a new `--enable-relay` flag (and env var) lets users toggle it; additionally, a flag/env var now disables eventing in OSS builds.
Why it matters: Stable Relay API (`/v1/relay`) replaces `/v1beta1/relay`; use the new `--enable-relay`/`HASURA_GRAPHQL_ENABLE_RELAY` default‑true toggle to control it, and optionally disable eventing via `HASURA_GRAPHQL_DISABLE_EVENTING` or `--disable-eventing`.
Summary
AI summaryUpdates Server, feat, and Data Connector across a mixed release.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Medium |
Promote Relay API to stable `/v1/relay` and deprecate `/v1beta1/relay` endpoint. Promote Relay API to stable `/v1/relay` and deprecate `/v1beta1/relay` endpoint. Source: llm_adapter@2026-05-28 Confidence: high |
— |
| Feature | Medium |
Add `--enable-relay` (`HASURA_GRAPHQL_ENABLE_RELAY`) flag to enable/disable Relay API, default true. Add `--enable-relay` (`HASURA_GRAPHQL_ENABLE_RELAY`) flag to enable/disable Relay API, default true. Source: llm_adapter@2026-05-28 Confidence: high |
— |
| Feature | Medium |
Add `HASURA_GRAPHQL_DISABLE_EVENTING` env var and `--disable-eventing` CLI flag to disable eventing subsystem in OSS/single‑tenant builds. Add `HASURA_GRAPHQL_DISABLE_EVENTING` env var and `--disable-eventing` CLI flag to disable eventing subsystem in OSS/single‑tenant builds. Source: llm_adapter@2026-05-28 Confidence: high |
— |
| Bugfix | Medium |
Fix MariaDB update/delete mutations failing with "Table 'temp_table_xxx' doesn't exist" by pinning temp‑table lifecycle to a single JDBC connection. Fix MariaDB update/delete mutations failing with "Table 'temp_table_xxx' doesn't exist" by pinning temp‑table lifecycle to a single JDBC connection. Source: llm_adapter@2026-05-28 Confidence: high |
— |
Full changelog
Changelog
This is a patch release for v2.49.
Bug fixes and improvements
Server
- feat: promote Relay API to stable
/v1/relayand deprecate/v/1beta1/relayendpoint. - feat: add the
--enable-relay(HASURA_GRAPHQL_ENABLE_RELAY) flag to enable/disable Relay API. Defaults to 'true' for backward compatibility. You can disable Relay to reduce memory usage if it isn't required for your applications. - enhancement: improvements to schema memory usage.
- feat: added
HASURA_GRAPHQL_DISABLE_EVENTINGenv var (and--disable-eventingCLI flag) to disable the entire eventing subsystem — event triggers, scheduled events, the cron event generator, and async actions — on the OSS / single-tenant build. Previously only multi-tenant cloud had this control. Thecli-migrationsv2 and v3 entrypoints now set this flag on their temporary HGE instance so migration jobs no longer compete with eventing pollers for database resources.
Data Connector
- fix: MariaDB `update`/`delete` mutations still failing with `Table 'temp_table_xxx' doesn't exist` on v2.48.15. The previous fix (#11473) ran the temp-table CREATE outside the transaction, which made the CREATE and the mutation body race over pooled connections; MariaDB temp tables are session-scoped, so when the mutation body got a different pooled connection the temp table was invisible. The full CREATE / mutation / DROP lifecycle now runs pinned to one JDBC connection. (Enterprise/cloud only)
Breaking Changes
- Deprecation of `/v1beta1/relay` endpoint (will be removed in a future release)
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Hasura
Fast, instant realtime GraphQL APIs on Postgres with fine grained access control, also trigger webhooks on database events.
Related context
Related tools
Beta — feedback welcome: [email protected]