Skip to content

Release history

Hasura releases

Fast, instant realtime GraphQL APIs on Postgres with fine grained access control, also trigger webhooks on database events.

All releases

9 shown

Config change
v2.49.0 Breaking risk
Breaking upgrade

Relay promotion + Eventing disable + MariaDB fix

Review required
v2.45.4 Breaking risk
Auth Breaking upgrade

Metadata inconsistency on remote schema conflicts

v2.48.16 Bug fix

Fixed hasura_http_response_bytes_total metric to exclude internal error field sizes not sent to clients.

Full changelog

Changelog

This is a patch release for v2.48.

Bug fixes and improvements

Server

  • Fix the hasura_http_response_bytes_total metric so it does not count the size of internal error fields when those fields are not returned to the client.
v2.48.15 Bug fix

Fixed MariaDB update and delete mutations failing with "temp table doesn't exist" error.

Full changelog

Changelog

This is a patch release for v2.48.

Bug fixes and improvements

Data Connectors

  • Fix MariaDB update and delete mutations failing with "temp table doesn't exist" error by adding a dedicated MariaDBMutationTranslator with proper temporary table lifecycle management, following the same pattern as the existing Oracle mutation translator.
v2.48.14 Bug fix

Fixed performance issue in Oracle data connector introspection.

Full changelog

Changelog

This is a patch release for v2.48.

Bug fixes and improvements

Data Connectors

  • Fix performance issue in oracle introspection of super-connector
v2.48.13 Bug fix

Fixed active subscriptions EKG gauge from going negative.

Full changelog

Changelog

This is a patch release for v2.48.

Bug fixes and improvements

Server

  • Set error status and message in OpenTelemetry spans, consistent with reporting in logs. (Enterprise/cloud only)
  • Fix active subscriptions EKG gauge going negative due to unconditional decrement in removeLiveQuery and removeStreamingQuery.
v2.48.12 Breaking risk

Fixed duplicate event triggers firing when moved between tables.

Full changelog

Changelog

This is a patch release for v2.48.

Bug fixes and improvements

Server

  • Fix a performance issue where large gzipped responses were causing long cumulative GC sync phase pauses
  • When an event trigger was moved from one table to another in Hasura metadata, the old trigger on the original table was not removed. This resulted in duplicate triggers firing for the same event.

Data Connector

  • Fix a bug in the super-connector (MySQL) where queries on self-referencing tables fail with Relation not found when the SELECT permission filter navigates through the same self-referencing relationship. The internal relationship graph now preserves both the aliased and original table entries during LATERAL subquery generation. (Enterprise/cloud only)
  • Fix update mutations on nullable columns via data connectors. Previously, attempting to set a column value to null in an update mutation would fail because the row update value was not allowed to be nullable. Nullable values are now correctly handled and translated to SQL NULL. (Enterprise/cloud only)
v2.48.11 Bug fix
⚠ Upgrade required
  • Ubuntu container base image updated to jammy-20260109
  • pgdump upgraded in containers for full PostgreSQL 18 support
Full changelog

Changelog

This is a patch release for v2.48.

Bug fixes and improvements

Server

  • SuperConnector: Fixes error caused by permissions in relationships in mutations, where the SQL temp table name was being improperly threaded through as the source table name.
  • Update ubuntu container base image to jammy-20260109
  • Upgrade pgdump in containers to fully support postgres 18
v2.48.10 Bug fix
⚠ Upgrade required
  • If BigQuery introspection issues arise after upgrade, set HASURA_BIGQUERY_SLOW_INTROSPECTION_FALLBACK=true to use the previous introspection method.
  • Redis pool size defaults increased to 500 for caching and rate‑limiting; adjust via new env vars if needed (Enterprise edition only).
Notable features
  • Configurable Redis connection pool sizes via HASURA_GRAPHQL_CACHING_REDIS_POOL_SIZE and HASURA_GRAPHQL_RATE_LIMIT_REDIS_POOL_SIZE (default increased to 500)
  • Fallback environment variable HASURA_BIGQUERY_SLOW_INTROSPECTION_FALLBACK to revert introspection method
Full changelog

Changelog

This is a patch release for v2.48.

Bug fixes and improvements

Server

  • Improve the performance of BigQuery schema introspection when there are many (e.g. hundreds of) tables in sourced datasets. This should improve performance on startup and during metadata operations, such as changing permissions. In the unexpected event that a BigQuery schema introspection-related bug is observed after upgrading, HASURA_BIGQUERY_SLOW_INTROSPECTION_FALLBACK=true can be set in the environment to revert to the previous introspection method.
  • Added HASURA_GRAPHQL_CACHING_REDIS_POOL_SIZE and HASURA_GRAPHQL_RATE_LIMIT_REDIS_POOL_SIZE options, making the limit of pooled connections to Redis configurable. Set the default to 500 (formerly it was 50). (Enterprise edition only)

Console

  • Fix a bug where deselecting or clearing a column type in the table schema editor causes existing columns to be duplicated in the schema.

Beta — feedback welcome: [email protected]