Data and AI releases

This month1,990Companies171

1,990 this month · 171 companies

graphql-engine 2.45.6

Update3 months agoUnverifiedAdded Oct 20, 2026

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

Topics: Security, Observability

Hasura's release notes

More graphql-engine releases

Every graphql-engine release
Updateunverified

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.

Updateunverified

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).

Updateunverified

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.

Updateunverified

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.

Updateunverified

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.

Updateunverified

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.

Updateunverified

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.

Updateunverified

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 Jul 10, 2026

Hasura in July 2026
Preview

Online Feature Store (Public Preview)

Online Feature Store is now available in public preview. Serve the latest feature values with low-latency online retrieval backed by Snowflake Postgres for real-time ML applications such as fraud detection, recommendations, and personalization.

Preview

Secrets in Unity Catalog (Public Preview)

You can now store, govern, and access secrets as securable objects in Unity Catalog. A Unity Catalog secret uses the three-level namespace ( catalog.schema.secret ) and is governed by Unity Catalog privileges, so you can apply the same access controls and auditing that you use for other data assets. See Secrets in Unity Catalog .

Preview

Agentic autofix for code scanning alerts in public preview

Agentic autofix is now in public preview for all code scanning alerts. It remediates alerts generated by CodeQL and third-party scanning tools by working across your codebase the way a developer would, it explores relevant files, proposes a fix, and reruns the original analysis to confirm the fix closes the alert before opening a pull request for your...