fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@graphql-tools/executor-graphql-ws (source)	1.3.6 -> 1.3.7
@graphql-tools/executor-http (source)	1.2.2 -> 1.2.3

---

Release Notes

graphql-hive/gateway (@​graphql-tools/executor-graphql-ws)

v1.3.7

Compare Source

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-hive/gateway (@​graphql-tools/executor-http)

v1.2.3

Compare Source

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 98d477f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://69f5d8a7.graphql-tools.pages.dev