Skip to content

Releases: graphql-hive/gateway

January 02, 2025

02 Jan 13:17
@theguild-bot theguild-bot
release-1735823860801
ace87b0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
January 02, 2025

@graphql-hive/gateway-abort-signal-any@0.0.3

Patch Changes

@graphql-tools/batch-delegate@9.0.27

Patch Changes

  • #396 da65b2d Thanks @ardatan! - Memoize the key arguments correctly;

    With the following schema and resolvers, userById should batch all the requests to usersByIds;

    {
      typeDefs: /* GraphQL */ `
        type User {
          id: ID!
          email: String!
        }
        type Query {
          userById(id: ID!): User
          usersByIds(ids: [ID!]): [User]
        }
      `,
      resolvers: {
        Query: {
          usersByIds: (_root, args) => {
            return args.ids.map((id: string) => users.find((user) => user.id === id));
          },
          userById: (root, args, context, info) => {
            return batchDelegateToSchema({
              schema: userSubschema,
              fieldName: 'usersByIds',
              key: args.id,
              rootValue: root,
              context,
              info,
            })
          },
        },
      },
    }

    This query should batch all the requests to usersByIds:

    {
  userById(id: "1") {
    id
    email
  }
  userById(id: "2") {
    id
    email
  }
}

    The delegation request should be;

    {
  usersByIds(ids: ["1", "2"]) {
    id
    email
  }
}

@graphql-tools/executor-http@1.2.4

Patch Changes

  • Updated dependencies [c60a8f4]:
    • @graphql-hive/gateway-abort-signal-any@0.0.3

@graphql-tools/federation@3.0.7

Patch Changes

  • #387 3571399 Thanks @ardatan! - In case of shared root field on Mutation, it was batched incorrectly across subgraphs. But instead only one mutation should be called as mutations should not be parallel

  • Updated dependencies []:

    • @graphql-tools/executor-http@1.2.4
    • @graphql-tools/stitch@9.4.13

@graphql-mesh/fusion-runtime@0.10.27

Patch Changes

  • Updated dependencies [3571399]:
    • @graphql-tools/federation@3.0.7
    • @graphql-mesh/transport-common@0.7.26
    • @graphql-tools/stitch@9.4.13

@graphql-hive/gateway@1.7.6

Patch Changes

  • Updated dependencies []:
    • @graphql-hive/gateway-runtime@1.4.6
    • @graphql-mesh/transport-http@0.6.30
    • @graphql-mesh/plugin-opentelemetry@1.3.34
    • @graphql-mesh/plugin-prometheus@1.3.22
    • @graphql-mesh/transport-http-callback@0.5.17
    • @graphql-mesh/transport-ws@0.4.15
    • @graphql-mesh/hmac-upstream-signature@1.2.19

@graphql-mesh/plugin-opentelemetry@1.3.34

Patch Changes

  • Updated dependencies []:
    • @graphql-hive/gateway-runtime@1.4.6
    • @graphql-mesh/transport-common@0.7.26

@graphql-mesh/plugin-prometheus@1.3.22

Patch Changes

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

@graphql-hive/gateway-runtime@1.4.6

Patch Changes

  • Updated dependencies [c60a8f4, 3571399, da65b2d]:
    • @graphql-hive/gateway-abort-signal-any@0.0.3
    • @graphql-tools/federation@3.0.7
    • @graphql-tools/batch-delegate@9.0.27
    • @graphql-tools/executor-http@1.2.4
    • @graphql-mesh/transport-common@0.7.26
    • @graphql-mesh/fusion-runtime@0.10.27
    • @graphql-tools/stitch@9.4.13
    • @graphql-mesh/hmac-upstream-signature@1.2.19

@graphql-tools/stitch@9.4.13

Patch Changes

  • Updated dependencies [da65b2d]:
    • @graphql-tools/batch-delegate@9.0.27

@graphql-mesh/transport-common@0.7.26

Patch Changes

  • Updated dependencies [c60a8f4]:
    • @graphql-hive/gateway-abort-signal-any@0.0.3

@graphql-mesh/transport-http@0.6.30

Patch Changes

  • Updated dependencies []:
    • @graphql-tools/executor-http@1.2.4
    • @graphql-mesh/transport-common@0.7.26

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

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/transport-common@0.7.26

@graphql-mesh/transport-ws@0.4.15

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/transport-common@0.7.26
Assets 2
Loading

hive-gateway@1.7.6

02 Jan 13:20
@theguild-bot theguild-bot
hive-gateway@1.7.6
ace87b0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
hive-gateway@1.7.6

Pre-built binaries of the Hive Gateway for the @graphql-hive/gateway@1.7.6 release.

Assets 6
Loading

December 31, 2024

31 Dec 11:34
@theguild-bot theguild-bot
release-1735644866348
03a648c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
December 31, 2024

@graphql-tools/batch-delegate@9.0.26

Patch Changes

@graphql-tools/federation@3.0.6

Patch Changes

  • Updated dependencies []:
    • @graphql-tools/stitch@9.4.12

@graphql-mesh/fusion-runtime@0.10.26

Patch Changes

  • Updated dependencies []:
    • @graphql-tools/stitch@9.4.12
    • @graphql-tools/federation@3.0.6

@graphql-mesh/plugin-prometheus@1.3.21

Patch Changes

  • Updated dependencies []:
    • @graphql-hive/gateway-runtime@1.4.5
Assets 2
Loading

December 26, 2024

26 Dec 15:26
@theguild-bot theguild-bot
release-1735226786267
5e18cb1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
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:

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

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

  • #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 chan...

Read more
Assets 2
Loading

hive-gateway@1.7.4

26 Dec 15:28
@theguild-bot theguild-bot
hive-gateway@1.7.4
5e18cb1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
hive-gateway@1.7.4

Pre-built binaries of the Hive Gateway for the @graphql-hive/gateway@1.7.4 release.

Assets 6
Loading

December 24, 2024

24 Dec 13:05
@theguild-bot theguild-bot
release-1735045517345
66f5450
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
December 24, 2024

@graphql-hive/gateway-abort-signal-any@0.0.2

Patch Changes

@graphql-tools/batch-delegate@9.0.25

Patch Changes

@graphql-tools/batch-execute@9.0.11

Patch Changes

@graphql-tools/delegate@10.2.9

Patch Changes

@graphql-tools/executor-graphql-ws@1.3.6

Patch Changes

@graphql-tools/executor-http@1.2.2

Patch Changes

  • #373 e606975 Thanks @ardatan! - dependencies updates:

  • #367 15975c2 Thanks @ardatan! - Fix the combination of upstreamRetry and upstreamTimeout together

    When you use upstreamRetry and upstreamTimeout together, the upstreamRetry wasn't applied properly when the request is timed out with upstreamTimeout.

  • Updated dependencies [e606975, e606975]:

    • @graphql-hive/gateway-abort-signal-any@0.0.2

@graphql-tools/federation@3.0.4

Patch Changes

@graphql-mesh/fusion-runtime@0.10.24

Patch Changes

@graphql-hive/gateway@1.7.3

Patch Changes

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

Patch Changes

Read more
Assets 2
Loading

December 24, 2024

24 Dec 09:22
@theguild-bot theguild-bot
release-1735032160959
ecd505d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
December 24, 2024

@graphql-mesh/fusion-runtime@0.10.23

Patch Changes

  • #357 8b64103 Thanks @ardatan! - Fix the bug on setting the default polling interval to 10 seconds
    So by default, the gateway will poll the schema every 10 seconds, and update the schema if it has changed.

    This PR also contains improvements on logging about polling

@graphql-hive/gateway@1.7.2

Patch Changes

  • #357 8b64103 Thanks @ardatan! - Fix the bug on setting the default polling interval to 10 seconds
    So by default, the gateway will poll the schema every 10 seconds, and update the schema if it has changed.

    This PR also contains improvements on logging about polling

  • #342 2f59fce Thanks @ardatan! - Respect both registry token from CLI arguments and the configuration in the `gateway.config`

    User can provide the token in the CLI arguments, and have some registry configuration in `gateway.config`

  • Updated dependencies [7a1877a, 8b64103, 122c013, 2f59fce]:

    • @graphql-mesh/plugin-opentelemetry@1.3.30
    • @graphql-hive/gateway-runtime@1.4.2
    • @graphql-mesh/hmac-upstream-signature@1.2.17
    • @graphql-mesh/plugin-prometheus@1.3.18

@graphql-mesh/plugin-opentelemetry@1.3.30

Patch Changes

@graphql-mesh/plugin-prometheus@1.3.18

Patch Changes

@graphql-hive/gateway-runtime@1.4.2

Patch Changes

  • #357 8b64103 Thanks @ardatan! - Fix the bug on setting the default polling interval to 10 seconds
    So by default, the gateway will poll the schema every 10 seconds, and update the schema if it has changed.

    This PR also contains improvements on logging about polling

  • #356 122c013 Thanks @ardatan! - Better messages on debug logs of readiness check endpoint;

    Before;
    On successful readiness check, the gateway was logging the following message:

    Readiness check passed: Supergraph loaded

    Because this makes the users think it was just loaded.
    After;
    On successful readiness check, the gateway will log the following message:

    Readiness check passed because supergraph has been loaded already

    On failed readiness check, the gateway was logging the following message:
    Before;

    Readiness check failed: Supergraph not loaded

    It should make the users think it was not loaded or there is an issue with the supergraph.

    After;

    Readiness check failed because supergraph has not been loaded yet or failed to load

  • #342 2f59fce Thanks @ardatan! - token doesn't need to be required for Hive reporting in the configuration because it can be provided by the arguments

  • Updated dependencies [8b64103]:

    • @graphql-mesh/fusion-runtime@0.10.23
    • @graphql-mesh/hmac-upstream-signature@1.2.17
Assets 2
Loading

hive-gateway@1.7.3

24 Dec 13:08
@theguild-bot theguild-bot
hive-gateway@1.7.3
66f5450
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
hive-gateway@1.7.3

Pre-built binaries of the Hive Gateway for the @graphql-hive/gateway@1.7.3 release.

Assets 6
Loading

hive-gateway@1.7.2

24 Dec 09:25
@theguild-bot theguild-bot
hive-gateway@1.7.2
ecd505d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
hive-gateway@1.7.2

Pre-built binaries of the Hive Gateway for the @graphql-hive/gateway@1.7.2 release.

Assets 6
Loading

December 14, 2024

14 Dec 15:45
@theguild-bot theguild-bot
release-1734191139755
3551600
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
December 14, 2024

@graphql-tools/federation@3.0.3

Patch Changes

@graphql-mesh/fusion-runtime@0.10.22

Patch Changes

@graphql-hive/gateway@1.7.1

Patch Changes

  • #333 0d81307 Thanks @renovate! - dependencies updates:

  • Updated dependencies [0d81307, 0d81307]:

    • @graphql-hive/gateway-runtime@1.4.1
    • @graphql-mesh/plugin-prometheus@1.3.17
    • @graphql-mesh/hmac-upstream-signature@1.2.17
    • @graphql-mesh/plugin-opentelemetry@1.3.29

@graphql-mesh/plugin-opentelemetry@1.3.29

Patch Changes

  • Updated dependencies [0d81307]:
    • @graphql-hive/gateway-runtime@1.4.1

@graphql-mesh/plugin-prometheus@1.3.17

Patch Changes

@graphql-hive/gateway-runtime@1.4.1

Patch Changes

Assets 2
Loading