Releases: hasura/graphql-engine
v2.11.13
Changelog
This is a patch release for v2.11
Bug fixes and improvements
Server
- On enabling the
HASURA_GRAPHQL_HTTP_LOG_QUERY_ONLY_ON_ERRORenv var, addqueryfield tohttp-logon failed requests irrespective ofquery-logbeing enabled. - Add
http_log_query_only_on_errorfield to start-up log.
v2.11.12
Changelog
This is a patch release for v2.11
Bug fixes and improvements
Server
- Introduce
HASURA_GRAPHQL_HTTP_LOG_QUERY_ONLY_ON_ERRORenv var and--http-log-query-only-on-errorflag to attachqueryfield tohttp-loglogs only on failed requests.
v2.34.0
Changelog
Highlights
Bug fixes and improvements
Server
-
The
naming_conventionexperimental feature now also covers:- Type and field names of named constraints that appear in
on_conflictupserts. - 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)
- Type and field names of named constraints that appear in
-
Add support for environment variable templating in OpenTelemetry endpoint URLs. (Cloud / Enterprise edition only)
-
Fix a memory leak in EE wherein data would accumulate in memory at each
replace_metadatacall. (Enterprise edition only)
Console
- Console support for adding input validations on PostgreSQL sources is now available in the
DataTab'sPermissionssection. - 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 be enabled from the Console for PostgreSQL, SQL Server, and Big Query from the
Datatab. - 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.
- Resolve an issue of incorrect name auto-suggestion when editing existing RESTified endpoints.
- Fix a bug on Insert/Modify Row where column inputs are not disabled if the column is an identity column (whose values are generated always/generated by default).
v2.11.11
Changelog
This is a patch release for v2.11
Bug fixes and improvements
Server
- Fix GraphQL query validation where queries that assigned a
nullvalue to a variable with a declared non-nullable type were previously allowed. Now, queries with this aforementioned condition will be properly invalidated and rejected.
Build
- Update build packages to get the latest security updates.
v2.33.4
Changelog
This is a patch release for v2.33
Bug fixes and improvements
Data Connectors
- Revert
/schemaGETrequest body, deprecate/schemaGET, addpost_schemacapability and/schemaPOSTwith performance improvements and filter capabilities.
v2.34.0-beta.1
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.
Edit: Post this beta release, it was decided to leave this feature as experimental for the v2.34.0 stable release.
Bug fixes and improvements
Server
-
The
naming_conventionexperimental feature now also covers:- Type and field names of named constraints that appear in
on_conflictupserts. - 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)
- Type and field names of named constraints that appear in
-
Add support for environment variable templating in OpenTelemetry endpoint URLs. (Cloud / Enterprise edition only)
-
Fix a memory leak in EE wherein data would accumulate in memory at each
replace_metadatacall. (Enterprise edition only)
Console
- Console support for adding input validations on PostgreSQL sources is now available in the
DataTab'sPermissionssection. - 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
Datatab. - 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.
v2.33.3
Changelog
This is a patch release for v2.33
Bug fixes and improvements
Server
- Revert unintentional changes to certain GraphQL types and fields when the
graphql-defaultnaming convention is enabled.
v2.33.2
v2.32.2
v2.33.1
Changelog
This is a patch release for v2.33
Bug fixes and improvements
Data Connectors
- Fix Oracle schema introspection for older Oracle versions (v18) (Enterprise edition only)
- Adds a configurable Retry mechanism to query execution in the Data Connector. Currently configured to retry 5 times, with a 1 second delay between each attempt. (Enterprise edition only)