December 26, 2024

@graphql-tools/executor-common@0.0.1

Patch Changes

• #381 55eb1b4 Thanks @ardatan! - This is a bugfix with some internal changes, no user action is needed. This bugfix and improvement is done to improve the stability of some components of the gateway;

  Like HMAC Upstream Signature plugin, different components of the gateway were using different ways of serializing the execution request.
  Some of them were ignoring variables if it is empty, some of not, this was causing the signature generation to be different for the same query.
  For example, it was working as expected in Proxy mode, but not working as expected in Federation Gateway mode.

  With this change, now we have a shared helper to serialize the upstream execution request with a memoized print function for query AST etc to have a consistent serialization so consistent signature generation for HMAC.

  For example instead of using print, you should use defaultPrintFn that memoizes print operation and also used the string version of it parsed before by Envelop/Yoga.

  -import { print } from 'graphql';
  -const query = print(parsedQuery);
  +import { defaultPrintFn } from '@graphql-tools/executor-common';
  +const query = defaultPrintFn(parsedQuery);

  Or instead of creating objects from ExecutionRequest, use serializeExecutionRequest helper.

  -const serializedRequest = {
  -  query: print(executionRequest.document),
  -  variables: executionRequest.variables,
  -  operationName: executionRequest.operationName,
  -  extensions: executionRequest.extensions,
  -};
  +import { serializeExecutionRequest } from '@graphql-tools/executor-common';
  +const serializedRequest = serializeExecutionRequest(executionRequest);

@graphql-tools/executor-graphql-ws@1.3.7

Patch Changes

• #381 55eb1b4 Thanks @ardatan! - dependencies updates:

  • Added dependency @graphql-tools/executor-common@workspace:^ ↗︎ (to dependencies)

• #381 55eb1b4 Thanks @ardatan! - This is a bugfix with some internal changes, no user action is needed. This bugfix and improvement is done to improve the stability of some components of the gateway;

  Like HMAC Upstream Signature plugin, different components of the gateway were using different ways of serializing the execution request.
  Some of them were ignoring variables if it is empty, some of not, this was causing the signature generation to be different for the same query.
  For example, it was working as expected in Proxy mode, but not working as expected in Federation Gateway mode.

  With this change, now we have a shared helper to serialize the upstream execution request with a memoized print function for query AST etc to have a consistent serialization so consistent signature generation for HMAC.

  For example instead of using print, you should use defaultPrintFn that memoizes print operation and also used the string version of it parsed before by Envelop/Yoga.

  -import { print } from 'graphql';
  -const query = print(parsedQuery);
  +import { defaultPrintFn } from '@graphql-tools/executor-common';
  +const query = defaultPrintFn(parsedQuery);

  Or instead of creating objects from ExecutionRequest, use serializeExecutionRequest helper.

  -const serializedRequest = {
  -  query: print(executionRequest.document),
  -  variables: executionRequest.variables,
  -  operationName: executionRequest.operationName,
  -  extensions: executionRequest.extensions,
  -};
  +import { serializeExecutionRequest } from '@graphql-tools/executor-common';
  +const serializedRequest = serializeExecutionRequest(executionRequest);

• Updated dependencies [55eb1b4]:

  • @graphql-tools/executor-common@0.0.1

@graphql-tools/executor-http@1.2.3

Patch Changes

• #381 55eb1b4 Thanks @ardatan! - dependencies updates:

  • Added dependency @graphql-tools/executor-common@workspace:^ ↗︎ (to dependencies)

• #381 55eb1b4 Thanks @ardatan! - This is a bugfix with some internal changes, no user action is needed. This bugfix and improvement is done to improve the stability of some components of the gateway;

  Like HMAC Upstream Signature plugin, different components of the gateway were using different ways of serializing the execution request.
  Some of them were ignoring variables if it is empty, some of not, this was causing the signature generation to be different for the same query.
  For example, it was working as expected in Proxy mode, but not working as expected in Federation Gateway mode.

  With this change, now we have a shared helper to serialize the upstream execution request with a memoized print function for query AST etc to have a consistent serialization so consistent signature generation for HMAC.

  For example instead of using print, you should use defaultPrintFn that memoizes print operation and also used the string version of it parsed before by Envelop/Yoga.

  -import { print } from 'graphql';
  -const query = print(parsedQuery);
  +import { defaultPrintFn } from '@graphql-tools/executor-common';
  +const query = defaultPrintFn(parsedQuery);

  Or instead of creating objects from ExecutionRequest, use serializeExecutionRequest helper.

  -const serializedRequest = {
  -  query: print(executionRequest.document),
  -  variables: executionRequest.variables,
  -  operationName: executionRequest.operationName,
  -  extensions: executionRequest.extensions,
  -};
  +import { serializeExecutionRequest } from '@graphql-tools/executor-common';
  +const serializedRequest = serializeExecutionRequest(executionRequest);

• Updated dependencies [55eb1b4]:

  • @graphql-tools/executor-common@0.0.1

@graphql-tools/federation@3.0.5

Patch Changes

• Updated dependencies [55eb1b4, 55eb1b4]:
  • @graphql-tools/executor-http@1.2.3

@graphql-mesh/fusion-runtime@0.10.25

Patch Changes

• Updated dependencies [55eb1b4, 55eb1b4]:
  • @graphql-mesh/transport-common@0.7.25
  • @graphql-tools/federation@3.0.5

@graphql-hive/gateway@1.7.4

Patch Changes

• Updated dependencies [55eb1b4, 55eb1b4, 55eb1b4]:
  • @graphql-mesh/hmac-upstream-signature@1.2.19
  • @graphql-mesh/transport-http-callback@0.5.16
  • @graphql-mesh/transport-http@0.6.29
  • @graphql-mesh/transport-ws@0.4.14
  • @graphql-hive/gateway-runtime@1.4.4
  • @graphql-mesh/plugin-opentelemetry@1.3.32
  • @graphql-mesh/plugin-prometheus@1.3.20

@graphql-mesh/hmac-upstream-signature@1.2.19

Patch Changes

• #381 55eb1b4 Thanks @ardatan! - dependencies updates:

  • Added dependency @graphql-tools/executor-common@workspace:^ ↗︎ (to dependencies)
  • Removed dependency @graphql-mesh/transport-common@workspace:^ ↗︎ (from dependencies)

• #381 55eb1b4 Thanks @ardatan! - This is a bugfix with some internal changes, no user action is needed. This bugfix and improvement is done to improve the stability of some components of the gateway;

  Like HMAC Upstream Signature plugin, different components of the gateway were using different ways of serializing the execution request.
  Some of them were ignoring variables if it is empty, some of not, this was causing the signature generation to be different for the same query.
  For example, it was working as expected in Proxy mode, but not working as expected in Federation Gateway mode.

  With this change, now we have a shared helper to serialize the upstream execution request with a memoized print function for query AST etc to have a consistent serialization so consistent signature generation for HMAC.

  For example instead of using print, you should use defaultPrintFn that memoizes print operation and also used the string version of it parsed before by Envelop/Yoga.

  -import { print } from 'graphql';
  -const query = print(parsedQuery);
  +import { defaultPrintFn } from '@graphql-tools/executor-common';
  +const query = defaultPrintFn(parsedQuery);

  Or instead of creating objects from ExecutionRequest, use serializeExecutionRequest helper.

  -const serializedRequest = {
  -  query: print(executionRequest.document),
  -  variables: executionRequest.variables,
  -  operationName: executionRequest.operationName,
  -  extensions: executionRequest.extensions,
  -};
  +import { serializeExecutionRequest } from '@graphql-tools/executor-common';
  +const serializedRequest = serializeExecutionRequest(executionRequest);

• Updated dependencies [55eb1b4]:

  • @graphql-tools/executor-common@0.0.1

@graphql-mesh/plugin-opentelemetry@1.3.32

Patch Changes

• Updated dependencies [55eb1b4, 55eb1b4]:
  • @graphql-mesh/transport-common@0.7.25
  • @graphql-hive/gateway-runtime@1.4.4

@graphql-mesh/plugin-prometheus@1.3.20

Patch Changes

• Updated dependencies []:
  • @graphql-hive/gateway-runtime@1.4.4

@graphql-hive/gateway-runtime@1.4.4

Patch Changes

• Updated dependencies [55eb1b4, 55eb1b4, 55eb1b4, 55eb1b4]:
  • @graphql-mesh/hmac-upstream-signature@1.2.19
  • @graphql-mesh/transport-common@0.7.25
  • @graphql-tools/executor-http@1.2.3
  • @graphql-mesh/fusion-runtime@0.10.25
  • @graphql-tools/federation@3.0.5

@graphql-mesh/transport-common@0.7.25

Patch Changes

• #381 55eb1b4 Thanks @ardatan! - dependencies updates:

  • Added dependency @graphql-tools/executor-common@workspace:^ ↗︎ (to dependencies)

• #381 55eb1b4 Thanks @ardatan! - This is a bugfix with some internal changes, no user action is needed. This bugfix and improvement is done to improve the stability of some components of the gateway;

  Like HMAC Upstream Signature plugin, different components of the gateway were using different ways of serializing the execution request.
  Some of them were ignoring variables if it is empty, some of not, this was causing the signature generation to be different for the same query.
  For example, it was working as expected in Proxy mode, but not working as expected in Federation Gateway mode.

  With this change, now we have a shared helper to serialize the upstream execution request with a memoized print function for query AST etc to have a consistent serialization so consistent signature generation for HMAC.

  For example instead of using print, you should use defaultPrintFn that memoizes print operation and also used the string version of it parsed before by Envelop/Yoga.

  -import { print } from 'graphql';
  -const query = print(parsedQuery);
  +import { defaultPrintFn } from '@graphql-tools/executor-common';
  +const query = defaultPrintFn(parsedQuery);

  Or instead of creating objects from ExecutionRequest, use serializeExecutionRequest helper.

  -const serializedRequest = {
  -  query: print(executionRequest.document),
  -  variables: executionRequest.variables,
  -  operationName: executionRequest.operationName,
  -  extensions: executionRequest.extensions,
  -};
  +import { serializeExecutionRequest } from '@graphql-tools/executor-common';
  +const serializedRequest = serializeExecutionRequest(executionRequest);

• Updated dependencies [55eb1b4]:

  • @graphql-tools/executor-common@0.0.1

@graphql-mesh/transport-http@0.6.29

Patch Changes

• #381 55eb1b4 Thanks @ardatan! - This is a bugfix with some internal changes, no user action is needed. This bugfix and improvement is done to improve the stability of some components of the gateway;

  Like HMAC Upstream Signature plugin, different components of the gateway were using different ways of serializing the execution request.
  Some of them were ignoring variables if it is empty, some of not, this was causing the signature generation to be different for the same query.
  For example, it was working as expected in Proxy mode, but not working as expected in Federation Gateway mode.

  With this change, now we have a shared helper to serialize the upstream execution request with a memoized print function for query AST etc to have a consistent serialization so consistent signature generation for HMAC.

  For example instead of using print, you should use defaultPrintFn that memoizes print operation and also used the string version of it parsed before by Envelop/Yoga.

  -import { print } from 'graphql';
  -const query = print(parsedQuery);
  +import { defaultPrintFn } from '@graphql-tools/executor-common';
  +const query = defaultPrintFn(parsedQuery);

  Or instead of creating objects from ExecutionRequest, use serializeExecutionRequest helper.

  -const serializedRequest = {
  -  query: print(executionRequest.document),
  -  variables: executionRequest.variables,
  -  operationName: executionRequest.operationName,
  -  extensions: executionRequest.extensions,
  -};
  +import { serializeExecutionRequest } from '@graphql-tools/executor-common';
  +const serializedRequest = serializeExecutionRequest(executionRequest);

• Updated dependencies [55eb1b4, 55eb1b4, 55eb1b4]:

  • @graphql-mesh/transport-common@0.7.25
  • @graphql-tools/executor-http@1.2.3

@graphql-mesh/transport-http-callback@0.5.16

Patch Changes

• #381 55eb1b4 Thanks @ardatan! - dependencies updates:

  • Added dependency @graphql-tools/executor-common@workspace:^ ↗︎ (to dependencies)

• Updated dependencies [55eb1b4, 55eb1b4]:

  • @graphql-mesh/transport-common@0.7.25
  • @graphql-tools/executor-common@0.0.1

@graphql-mesh/transport-ws@0.4.14

Patch Changes

• #381 55eb1b4 Thanks @ardatan! - This is a bugfix with some internal changes, no user action is needed. This bugfix and improvement is done to improve the stability of some components of the gateway;

  Like HMAC Upstream Signature plugin, different components of the gateway were using different ways of serializing the execution request.
  Some of them were ignoring variables if it is empty, some of not, this was causing the signature generation to be different for the same query.
  For example, it was working as expected in Proxy mode, but not working as expected in Federation Gateway mode.

  With this change, now we have a shared helper to serialize the upstream execution request with a memoized print function for query AST etc to have a consistent serialization so consistent signature generation for HMAC.

  For example instead of using print, you should use defaultPrintFn that memoizes print operation and also used the string version of it parsed before by Envelop/Yoga.

  -import { print } from 'graphql';
  -const query = print(parsedQuery);
  +import { defaultPrintFn } from '@graphql-tools/executor-common';
  +const query = defaultPrintFn(parsedQuery);

  Or instead of creating objects from ExecutionRequest, use serializeExecutionRequest helper.

  -const serializedRequest = {
  -  query: print(executionRequest.document),
  -  variables: executionRequest.variables,
  -  operationName: executionRequest.operationName,
  -  extensions: executionRequest.extensions,
  -};
  +import { serializeExecutionRequest } from '@graphql-tools/executor-common';
  +const serializedRequest = serializeExecutionRequest(executionRequest);

• Updated dependencies [55eb1b4, 55eb1b4, 55eb1b4]:

  • @graphql-mesh/transport-common@0.7.25
  • @graphql-tools/executor-graphql-ws@1.3.7