graphql-engine 2.49.5
Update3 months agoUnverifiedAdded Oct 20, 2026
Changelog This is a patch release for v2.49. > [!Warning] > If your metadata enables the naming convention graphql-default, the metadata could be inconsistent because the naming convention Sep 2023 is enabled by default. Please upgrade to v2.50.0 to fix that issue. Bug fixes and improvements Server - Upgrade Ubuntu base images to 24.04).
Topics: Security, Data integration, Observability, Developer tools
More graphql-engine releases
Every graphql-engine releasegraphql-engine 2.45.6
Changelog This is a patch release for v2.45. Bug fixes and improvements - packaging: upgrade openssl in ubuntu base image to fix openssl CVE-2026-45447
graphql-engine 2.49.4
Changelog This is a patch release for v2.49. Bug fixes and improvements Server - Made catalog and PG source migrations idempotent by adding IF NOT EXISTS to all ADD COLUMN statements, preventing re-application failures when a migration was applied to the database but its version was not recorded.
graphql-engine 2.50.0
Changelog Bug fixes and improvements Server - IMPORTANT: fix a bug in the mssql backend that could in certain cases allow an authenticated user to observe data they were not authorized for. All MS SQL Server users are encouraged to upgrade. More details to be released. - Add cascade option to the remove_remote_schema API.
graphql-engine 2.45.8
Changelog This is a patch release for v2.45. Bug fixes and improvements Server - IMPORTANT: fix a bug in the mssql backend that could in certain cases allow an authenticated user to observe data they were not authorized for. All MS SQL Server users are encouraged to upgrade. More details to be released.
graphql-engine 2.50.1
Changelog This is a patch release for v2.50. Bug fixes and improvements Server - Added three opt-in flags (all default false) that redact the request body, session variables and webhook response body from the respective delivery logs (Event Triggers, Scheduled/Cron Triggers, and Action handlers). Redacted fields are emitted as JSON null.
graphql-engine 2.49.3
Changelog This is a patch release for v2.49. Bug fixes and improvements Server - Added HASURA_GRAPHQL_DISABLE_EVENT_PROCESSING env var (and --disable-event-processing CLI flag) to stop the eventing background pollers , event triggers, scheduled events, the cron event generator, and async actions , without disabling the rest of the eventing subsystem.
graphql-engine 2.45.5
Changelog This is a patch release for v2.45. Bug fixes and improvements Server - Fix a high-severity security issue: https://github.com/hasura/graphql-engine/security/advisories/GHSA-r27x-gc74-qmxh . Users are strongly encouraged to upgrade.
graphql-engine 2.49.2
Changelog This is a patch release for v2.49. Bug fixes and improvements Server - Fix a high-severity security issue: https://github.com/hasura/graphql-engine/security/advisories/GHSA-r27x-gc74-qmxh . Users are strongly encouraged to upgrade.
Also shipped on Jul 21, 2026
Hasura in July 2026CoCo Desktop - General availability
CoCo Desktop is now generally available. CoCo Desktop is a native Mac and Windows desktop application that brings CoCo’s full agentic capabilities into an IDE-like surface, with a file editor, integrated terminal, agentic AI loop, agentic browser, agentic notebook, and deep Snowflake awareness.
Consuming Delta Shares in Horizon Catalog (General availability)
Snowflake builds for interoperability. Horizon Catalog is the metadata hub for your entire data estate, giving every team a single, unified window into every data asset regardless of where it lives or what format it uses. Today we expand that commitment. Consuming Delta Shares as a Catalog Linked Database in Horizon Catalog is now generally available.
Tag-based data protection policies (Public Preview)
Tag-based policy support is now available in public preview for aggregation policies, row access policies, projection policies, and join policies. This feature allows you to assign data protection policies to tags, automatically protecting any objects that have the tag assigned to them.
Warehouse-level statement timeouts (Beta)
You can now set a statement timeout on a single SQL warehouse so that different warehouses can apply different timeouts to their queries. Set the timeout with the statement_timeout field in the Create or Update warehouse APIs. This feature is in Beta and is API-only. See Warehouse-level timeout .
Reddit Ads connector is now available in Beta
The managed Reddit Ads connector in Lakeflow Connect is now available in Beta. You can use the connector to ingest advertising campaign data and performance metrics from Reddit Ads into Databricks. See Reddit Ads connector .
Context-based ingress control for workspaces public access is now generally available
Context-based ingress control for workspaces public access is now generally available. Control who can reach your workspace endpoints using allow and deny rules that allow you to combine identities, network sources, and request types. See Context-based ingress control .