Skip to content

fix(deps): update dependency @graphql-tools/executor-http to v2 #10399

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix(deps): update dependency @graphql-tools/executor-http to v2 #10399

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 9, 2025

This PR contains the following updates:

Package Change Age Confidence
@graphql-tools/executor-http (source) ^1.0.0 -> ^2.0.0 age confidence

Release Notes

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

v2.1.1

Compare Source

Patch Changes

v2.1.0

Compare Source

Minor Changes
  • #​1017 b59a266 Thanks @​ardatan! - endpoint can now also be a factory function that returns the endpoint based on the ExecutionRequest. This allows creating dynamic endpoints, depending on environment variables or other runtime values.
Patch Changes

v2.0.3

Compare Source

Patch Changes

v2.0.2

Compare Source

Patch Changes

v2.0.1

Compare Source

Patch Changes

v2.0.0

Compare Source

Major Changes

  • #​997 4cf75cb Thanks @​ardatan! - - BREAKING: HTTP Executor no longer takes serviceName as an option.

    • Both HTTP executor and @graphql-mesh/transport-http-callback no longer handle DOWNSTREAM_SERVICE_ERROR error code with serviceName.
    • Gateway runtime handles subgraph errors on its own with DOWNSTREAM_SERVICE_ERROR error code and serviceName as a property. This behavior can be configured with subgraphErrors option of the createGatewayRuntime function or CLI config.
    subgraphError: {
   errorCode: 'DOWNSTREAM_SERVICE_ERROR', // or `false` to remove this code completely
   subgraphNameProp: 'serviceName' // or `false` to remove this prop completely
}
Patch Changes

v1.3.3

Compare Source

Patch Changes

v1.3.2

Compare Source

Patch Changes

v1.3.1

Compare Source

Patch Changes

v1.3.0

Compare Source

Minor Changes
  • #​792 9c2f323 Thanks @​ardatan! - Ensure subgraph name is present in the upstream error extensions when HTTP Executor throws
Patch Changes

v1.2.8

Compare Source

Patch Changes

v1.2.7

Compare Source

Patch Changes

v1.2.6

Compare Source

Patch Changes

v1.2.5

Compare Source

Patch Changes

  • #​420 14152f7 Thanks @​ardatan! - - In case of schema reload, throw SCHEMA_RELOAD error while recreating the transports and executors

    • In case of shut down, throw SHUTTING_DOWN error while cleaning the transports and executors up

    Previously, these errors are only thrown for subscriptions not it is thrown in other type of operations as well.
    And previously the thrown errors during these two cleanup and restart process were cryptic, now the mentioned two errors above are thrown with more clear messages

v1.2.4

Compare Source

Patch Changes

v1.2.3

Compare Source

Patch Changes

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

  • #​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]:

v1.2.2

Compare Source

Patch Changes

v1.2.1

Compare Source

Patch Changes

v1.2.0

Compare Source

Minor Changes

  • #​313 367b359 Thanks @​ardatan! - Automatic Persisted Queries support for upstream requests

    For HTTP Executor;

    buildHTTPExecutor({
  // ...
  apq: true,
});

    For Gateway Configuration;

    export const gatewayConfig = defineConfig({
  transportEntries: {
    '*': {
      options: {
        apq: true,
      },
    },
  },
});

v1.1.14

Compare Source

Patch Changes

v1.1.13

Compare Source

Patch Changes

v1.1.12

Compare Source

Patch Changes

v1.1.11

Compare Source

Patch Changes

v1.1.10

Compare Source

Patch Changes

v1.1.9

Compare Source

Patch Changes

v1.1.8

Compare Source

Patch Changes

v1.1.7

Compare Source

Patch Changes

v1.1.6

Compare Source

Patch Changes

  • f9dd3d6
    Thanks @​ardatan! - Details in the extensions when an unexpected
    error occurs;

    {
  "request": {
    "url": "https://api.example.com/graphql",
    "method": "POST",
    "body": {
      "query": "query { hello }"
    }
  },
  "response": {
    "status": 500,
    "statusText": "Internal Server Error",
    "headers": {
      "content-type": "application/json"
    },
    "body": {
      "errors": [
        {
          "message": "Internal Server Error"
        }
      ]
    }
  }
}

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

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

@renovate renovate bot added the dependencies label Aug 9, 2025
@renovate renovate bot requested a review from ardatan August 9, 2025 16:39
@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Aug 9, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: 42fdcb3

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 GitHub Actions
Copy link
Contributor

github-actions bot commented Aug 9, 2025

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package Version Info
@graphql-codegen/cli 5.0.6-alpha-20250809164118-72e6ae32908b02ffda4a8a4f12a35e1ba23e5e80 npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript-operations 4.6.1-alpha-20250809164118-72e6ae32908b02ffda4a8a4f12a35e1ba23e5e80 npm ↗︎ unpkg ↗︎
@graphql-codegen/typescript-resolvers 4.5.1-alpha-20250809164118-72e6ae32908b02ffda4a8a4f12a35e1ba23e5e80 npm ↗︎ unpkg ↗︎
@graphql-codegen/client-preset 4.8.1-alpha-20250809164118-72e6ae32908b02ffda4a8a4f12a35e1ba23e5e80 npm ↗︎ unpkg ↗︎
@graphql-codegen/graphql-modules-preset 4.0.17-alpha-20250809164118-72e6ae32908b02ffda4a8a4f12a35e1ba23e5e80 npm ↗︎ unpkg ↗︎

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Aug 9, 2025 •
edited
Loading

💻 Website Preview

The latest changes are available as preview in: https://pr-10399.graphql-code-generator.pages.dev

@renovate renovate bot force-pushed the renovate/major-graphql-tools branch from 72e6ae3 to 42fdcb3 Compare August 10, 2025 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ardatan ardatan Awaiting requested review from ardatan

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants