hasura/graphql-engine v2.34.0-beta.1

on GitHub

Changelog

Highlights

naming-convention GA

The naming-convention feature for PostgreSQL sources, previously in the experimental phase, is now generally available and fully enabled. Users can still specify HASURA_GRAPHQL_EXPERIMENTAL_FEATURES=naming_convention, although it is no longer necessary as it will have no impact and will eventually be removed.

Bug fixes and improvements

Server

• The naming_convention experimental feature now also covers:

  • Type and field names of named constraints that appear in on_conflict upserts.
  • Type names of all Postgres scalar types.
  • Type and input field names of function arguments.

  Since these changes are breaking by nature, their use is gated by a feature flag, which can be enabled by setting the environment variable HASURA_FF_NAMING_CONVENTION_SEP_2023=True.

  (partially fixes: #8929)

• Add support for environment variable templating in OpenTelemetry endpoint URLs. (Cloud / Enterprise edition only)

• Fix a memory leak wherein data would accumulate in memory at each replace_metadata call. (Enterprise edition only)

Console

• Console support for adding input validations on PostgreSQL sources is now available in the Data Tab's Permissions section.
• Fixed a UI bug which would duplicate column form values when attempting to clear the column type. (fix #9863)
• Added Console support for remote relationship permissions to PostgreSQL data sources.
• Resolved an issue of incorrect URL autosuggestion when editing existing RESTified endpoints.
• Clicking on any role on a schema change card now updates the page's URL, improving navigation and allowing sharing of specific schema change details.
• Visiting a schema registry URL automatically opens the corresponding schema change card at the top of the page, streamlining access to specific schema change information.
• Apollo Federation support can enabled from the Console for PostgreSQL, SQL Server, and Big Query from the Data tab.
• Fixes an issue where an error notification would appear even upon successfully creating a remote relationship.
• Improve performance of the permissions UI for large data-connector based databases.