Changelog

Behaviour changes

• We have fixed GraphQL query validation where queries that assigned a null value to a variable with a declared non-nullable type were previously allowed.

  For example:

  query ($user_id: Int!) {
    users(where: {id: {_eq: $user_id}}){
      id name
    }
  }
  

  {
    "user_id": null
  }
  

  Now, queries with this aforementioned condition will be properly invalidated and rejected.

  Since, it is a behavior change, we are introducing a server option to preserve the old behavior when either of the following are set to true:

  • Environment variable: HASURA_GRAPHQL_BACKWARDS_COMPAT_NULL_IN_NONNULLABLE_VARIABLES
  • Flag: --null-in-nonnullable-variables

  The above configuration is optional, and the default value is false i.e, new fixed behavior is applied

Bug fixes and improvements

Server

• Change in PostgreSQL array introspection to improve query performance.
• For MS SQL Server, handle missing type information for columns when querying metadata.
• The pg_dump version has been upgraded to v16, so that it can extract data from PostgreSQL 16 databases.
• Fix websocket connection failure when hide_aggregation_predicates and hide_stream_fields experimental features are enabled.

Console

• Support creation of REST endpoint from a table in new data tab UI.
• Support computed fields in new permissions UI
• Truncate large JSON values in browse rows for data-connector backed databases.
• Fix a validation bug in the GraphQL Data Connector connection form when advanced settings is not open.

Data Connectors

• hasura/graphql-data-connector image now supports all non-root user IDs and groups

Build

• RedHat UBI-based graphql-engine docker images are now available.

  hasura/graphql-engine:v2.36.0-beta.1.ubi
  hasura/graphql-engine:v2.36.0-beta.1.cli-migrations-v2.ubi
  hasura/graphql-engine:v2.36.0-beta.1.cli-migrations-v3.ubi