graphql-engine 2.48.14
Update7 months agoUnverifiedAdded Oct 20, 2026
Changelog This is a patch release for v2.48. Bug fixes and improvements Data Connectors - Fix performance issue in oracle introspection of super-connector
Topics: Data integration, Observability, Performance
More graphql-engine releases
Every graphql-engine releasegraphql-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.
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.
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.
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.
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.
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.
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.
graphql-engine 2.48.10
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.
Also shipped on Mar 25, 2026
Hasura in March 2026Deploying services using a Compose file is in General Availability
Deploying services using a Compose file is in General Availability .
Modal 1.4.0
We've made significant CLI enhancements so that Modal logs can be more accessible to coding agents: The modal app logs and modal container logs commands now have the ability to fetch historical logs using counting (e.g. --tail 1000) or time-based (e.g., --since 4h, --until 2026-03-15, etc.) configuration.
Attribution Alerts
Set alerts scoped to specific teams, services, environments, and more using cost attribution labels We’re excited to announce the general availability of Attribution Alerts in the Cost Management and Billing app!
The Shopify CLI app release `--force` flag is deprecated and will be removed
We are deprecating the --force flag on the shopify app deploy and shopify app release commands. The flag will be removed in a Shopify CLI release in May 2026. Why we're making this change The --force flag skips all confirmation prompts, including for extension deletions that can permanently remove data on installed shops.
New Filters for List Session Replays
What it is: Two new filters are now available on the List Session Replays API endpoint. 'amplitude_id' (integer) returns replays tied to a specific Amplitude user ID. 'replay_id' accepts up to 100 IDs in 'device_id/session_id' format and fetches those sessions directly, bypassing pagination.
Improvements to Distributions
What it is: Frequency charts, histogram charts, session length, and time-to-convert now support normalization, PDF, and CDF views. Normalization scales each series so its bars sum to 1, making groups with different sample sizes directly comparable , for example, U.S.