Releasesby Ibisgraphql-engine 2.48.15
Update6 months agoUnverifiedAdded Oct 20, 2026
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.
Topics: Data integration, Observability
More graphql-engine releases
Every graphql-engine releasegraphql-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
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.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.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.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.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.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.49.1
Changelog This is a patch release for v2.49. Bug fixes and improvements Server - Fix a bug where event triggers could prevent prompt server shutown; now we correctly only pause for actual in-flight processing - Fix a bug where, with multiple sources, in-flight event triggers which were stuck during shutdown may not have been unlocked in the database before...
Also shipped on Apr 1, 2026
Hasura in April 2026AI-Powered Dashboard Generation (Beta)
Generate custom dashboards with an LLM agent.
Revamped query editor experience
We’ve redesigned the query editor to make complex panels easier to build and manage. The new experience provides a unified view of your entire data pipeline, queries, expressions, transformations, and related alerts, with clearer visual feedback and faster access to the settings that matter.
Add Prerequisites to Product Discount Functions
Discount functions now support prerequisites for product discount candidates, allowing you to define the "Buy X" portion of a Buy X, Get Y (BXGY) discount. In a BXGY discount, customers must purchase a specified quantity of one product (Buy X) to receive a discount on another product (Get Y).
ShopifyAdd Tags to Discounts
Starting in API version 2026-04, discounts support tags allowing you to efficiently label, group, and organize your discounts. What's new: The tags field has been added to all discount types Tags can be added, updated, and removed via the Admin API For more information, visit the Admin API documentation
Cart and checkout validation adds billing address and PO number error targets
As of API version 2026-04, you can validate billing addresses and purchase order (PO) numbers in Cart and Checkout Validation Functions. We've added billing address and PO Number to the function input graph and introduced new checkout field targets.
Create unpaid orders from subscription billing attempts
In the API 2026-04 release candidate version, you can now include a new field called paymentProcessingPolicy when creating a billing attempt using the subscriptionBillingAttemptCreate mutation. A billing attempt is an action to charge a customer based on their subscription.