Data and AI releases

This month1,990Companies171

1,990 this month · 171 companies

graphql-engine 2.48.10

Update9 months agoUnverifiedAdded Oct 20, 2026

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.

Topics: SQL, Security, Observability, Performance

Hasura's release notes

More graphql-engine releases

Every graphql-engine release
Updateunverified

graphql-engine 2.48.11

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.

Updateunverified

graphql-engine 2.48.12

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.

Updateunverified

graphql-engine 2.48.13

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.

Updateunverified

graphql-engine 2.48.14

Changelog This is a patch release for v2.48. Bug fixes and improvements Data Connectors - Fix performance issue in oracle introspection of super-connector

Updateunverified

graphql-engine 2.48.15

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.

Updateunverified

graphql-engine 2.48.16

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.

Updateunverified

graphql-engine 2.45.4

Changelog This is a patch release for v2.45. Upgrade notes Some compatibility notes 1. Previously, when remote schema types conflicted with action types, the conflict was silently handled (the remote schema was just excluded). Now it's marked as inconsistent_metadata.

Updateunverified

graphql-engine 2.49.0

Changelog Bug fixes and improvements Server - feat: promote Relay API to stable /v1/relay and deprecate /v/1beta1/relay endpoint. - feat: add the --enable-relay (HASURA_GRAPHQL_ENABLE_RELAY) flag to enable/disable Relay API. You can disable Relay to reduce memory usage if it isn't required for your applications.

Also shipped on Jan 15, 2026

Hasura in January 2026
Deprecationunverified

Datagrid deprecation

The datagrid visualization is deprecated after spending roughly three years in an experimental state. While existing panels that use datagrid will continue to function, it will no longer be available for creating new panels.

Updateunverified

Container Images (release 260115)

- quay.io/deepgram/self-hosted-api:release-260115 Equivalent image to: quay.io/deepgram/self-hosted-api:1.176.0 quay.io/deepgram/self-hosted-engine:release-260115 Equivalent image to: quay.io/deepgram/self-hosted-engine:3.107.0-1 Minimum required NVIDIA driver version: >=570.172.08 quay.io/deepgram/self-hosted-license-proxy:release-260115 Equivalent image...

Updateunverified

January 2026 Self-Hosted Release: Update Recommendation

In Deepgram's January 2026 self-hosted release (release-260115), we added new functionality to improve TTS response times from our API and Engine containers. Due to this product change, the January 2026 self-hosted release is not backwards-compatible with previous releases when used to serve TTS traffic.