Releasesby Ibisgraphql-engine 2.50.3
Update6 weeks agoUnverifiedAdded Oct 20, 2026
Changelog This is a patch release for v2.50. Bug fixes and improvements Server - Fix an issue that caused memory from the schema present at engine startup to be retained after the metadata is updated, for instance with replace_metadata. Formerly this could manifest in as much as a doubling of memory usage.
Topics: Observability
More graphql-engine releases
Every graphql-engine releasegraphql-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.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.49.5
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).
graphql-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.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.
Also shipped on Sep 9, 2026
Hasura in September 2026Configurable retention for system tables is in Beta
Account admins can now set an account-wide retention period from 30 to 3,650 days for supported system tables. See Configure system table data retention .
External secrets in Unity Catalog (Beta)
External secrets connect a Unity Catalog schema to AWS Secrets Manager. The secrets appear in Unity Catalog as read-only securable objects that you govern with Unity Catalog privileges. Databricks reads their values from AWS Secrets Manager on demand. See External secrets in Unity Catalog .
Celigo connector (Beta)
The Celigo connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector ingests audit log events, such as create, update, and delete operations on resources, from Celigo (integrator.io) into Databricks. Authentication uses a Celigo integrator.io API token.
Anysphere Organization connector (Beta)
The Anysphere Organization connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector uses the Anysphere (Cursor) Organization Admin API to ingest organization members, groups, and group members into Databricks as daily snapshots.
Anaplan connector (Beta)
The Anaplan connector is now available in Lakeflow Connect in Beta . Workspace admins can control access to this feature from the Previews page. The connector ingests audit trail events and user account records from your Anaplan tenant into Databricks. Authentication uses an Anaplan CA certificate and its paired private key. See Anaplan connector .
Openflow gen 1 deployment creation retired
You can no longer create new first generation (gen 1) Openflow deployments (BYOC or Snowflake). All new deployments are second generation (gen 2), created with CREATE OPENFLOW DEPLOYMENT or the Openflow UI. Existing gen 1 deployments continue to work unchanged, and you can still create new gen 1 runtimes on an existing gen 1 deployment.