Releases: graphql-hive/gateway
February 04, 2025
@graphql-tools/[email protected]
Patch Changes
- #591
7d42160
Thanks @ardatan! - Fix the regression preventing users from passing customlazy
andlazyCloseTimeout
options
@graphql-hive/[email protected]
Patch Changes
- Updated dependencies [
7d42160
,7d42160
]:- @graphql-mesh/[email protected]
@graphql-mesh/[email protected]
Patch Changes
-
#591
7d42160
Thanks @ardatan! - dependencies updates:- Removed dependency
isomorphic-ws@^5.0.0
↗︎ (fromdependencies
)
- Removed dependency
-
#591
7d42160
Thanks @ardatan! - Avoid having an extra Client instantiation in the transport, and use the one in the executor -
Updated dependencies [
7d42160
]:- @graphql-tools/[email protected]
February 04, 2025
@graphql-tools/[email protected]
Major Changes
-
#481
0b13cb4
Thanks @enisdenjo! - Executor options don't exist graphql-ws dependency optionsRemoving the dependency on the types. Some options are still exposed, but if you want to further customise the graphql-ws client, you should pass your own instance of the client instead.
import { buildGraphQLWSExecutor } from '@graphql-tools/executor-graphql-ws'; import { createClient } from 'graphql-ws'; import { options } from './my-graphql-ws-client-options'; const executor = buildGraphQLWSExecutor( createClient({ url: 'ws://localhost:4000/graphql', ...options, }), );
-
#481
0b13cb4
Thanks @enisdenjo! - Upgrade graphql-ws to v6If you have a custom graphql-ws configuration when building the executor with
buildGraphQLWSExecutor
, you will have to migrate the graphql-ws side to v6. Please consult the changelog of graphql-ws.
Minor Changes
- #481
0b13cb4
Thanks @enisdenjo! - Export GraphQLWSExecutorOptions type
Patch Changes
-
#481
0b13cb4
Thanks @enisdenjo! - dependencies updates:- Updated dependency
graphql-ws@^6.0.3
↗︎ (from^5.14.0
, independencies
)
- Updated dependency
@graphql-hive/[email protected]
Patch Changes
-
#481
0b13cb4
Thanks @enisdenjo! - dependencies updates:- Updated dependency
graphql-ws@^6.0.3
↗︎ (from^5.16.0
, independencies
)
- Updated dependency
-
#481
0b13cb4
Thanks @enisdenjo! - WebSocket transport options allow configuring onlyconnectionParams
In most of the cases you won't need to configure the underlying graphql-ws client any further.
-
#481
0b13cb4
Thanks @enisdenjo! - Upgrade graphql-ws to v6If you have a custom graphql-ws configuration when using the transport, you will have to migrate the graphql-ws side to v6. Please consult the changelog of graphql-ws.
-
Updated dependencies [
0b13cb4
,0b13cb4
,0b13cb4
,0b13cb4
,0b13cb4
]:- @graphql-hive/[email protected]
- @graphql-mesh/[email protected]
- @graphql-mesh/[email protected]
- @graphql-mesh/[email protected]
- @graphql-mesh/[email protected]
@graphql-mesh/[email protected]
Patch Changes
- Updated dependencies [
0b13cb4
]:- @graphql-hive/[email protected]
@graphql-mesh/[email protected]
Patch Changes
- Updated dependencies [
0b13cb4
]:- @graphql-hive/[email protected]
@graphql-hive/[email protected]
Patch Changes
-
#481
0b13cb4
Thanks @enisdenjo! - dependencies updates:- Updated dependency
graphql-ws@^6.0.3
↗︎ (from^5.16.0
, independencies
)
- Updated dependency
-
Updated dependencies []:
- @graphql-mesh/[email protected]
@graphql-mesh/[email protected]
Major Changes
-
#481
0b13cb4
Thanks @enisdenjo! - WebSocket transport options allow configuring onlyconnectionParams
In most of the cases you won't need to configure the underlying graphql-ws client any further.
-
#481
0b13cb4
Thanks @enisdenjo! - WebSocket transport is stable and production ready
Minor Changes
-
#481
0b13cb4
Thanks @enisdenjo! - Upgrade graphql-ws to v6If you have a custom graphql-ws configuration when using the transport, you will have to migrate the graphql-ws side to v6. Please consult the changelog of graphql-ws.
Patch Changes
-
#481
0b13cb4
Thanks @enisdenjo! - dependencies updates:- Updated dependency
graphql-ws@^6.0.3
↗︎ (from^5.16.0
, independencies
) - Added dependency
isomorphic-ws@^5.0.0
↗︎ (todependencies
)
- Updated dependency
-
Updated dependencies [
0b13cb4
,0b13cb4
,0b13cb4
,0b13cb4
]:- @graphql-tools/[email protected]
[email protected]
Pre-built binaries of the Hive Gateway for the @graphql-hive/[email protected] release.
[email protected]
Pre-built binaries of the Hive Gateway for the @graphql-hive/[email protected] release.
January 31, 2025
@graphql-hive/[email protected]
Patch Changes
[email protected]
Pre-built binaries of the Hive Gateway for the @graphql-hive/[email protected] release.
January 30, 2025
@graphql-hive/[email protected]
Minor Changes
-
#568
de83dd2
Thanks @dotansimha! - Improvecache
configuration signature.The
cache
configuration key now allow you to pass a custom factory function to get the cache instance:import { defineConfig } from '@graphql-hive/gateway'; export const gatewayConfig = defineConfig({ // ... cache: (ctx) => { // Here you may create/retrieve your cache store instance, and return a KeyValueCache instance }, });
Patch Changes
[email protected]
Pre-built binaries of the Hive Gateway for the @graphql-hive/[email protected] release.
January 29, 2025
@graphql-tools/[email protected]
Patch Changes
- Updated dependencies [
9144222
]:- @graphql-tools/[email protected]
@graphql-tools/[email protected]
Patch Changes
-
#506
9144222
Thanks @ardatan! - AddisPrototypePollutingKey
to prevent accidential prototype pollution, whenever object manipulation happens with the keys based on the user input, it is validated to prevent prototype pollution.For example,
WrapQuery
takespath
which is used to manipulate the object returned to the client. If the user input is__proto__
, it will throw an error from now on but previously it would have polluted the prototype.
@graphql-tools/[email protected]
Minor Changes
-
#444
b52c9ba
Thanks @ardatan! - NowSupergraphSchemaManager
can be used inApolloServer
asgateway
;import { ApolloServer } from '@apollo/server'; import { SupergraphSchemaManager } from '@graphql-tools/federation'; const gateway = new SupergraphSchemaManager(); const apolloServer = new ApolloServer({ gateway, });
And with the new
onStitchedSchema
option, you can manipulate the executable schema created from the supergraph.
The following example demonstrates how to useonStitchedSchema
withapplyMiddleware
fromgraphql-middleware
:import { SupergraphSchemaManager } from '@graphql-tools/federation'; import { applyMiddleware } from 'graphql-middleware'; const logInput = async (resolve, root, args, context, info) => { console.log(`1. logInput: ${JSON.stringify(args)}`); const result = await resolve(root, args, context, info); console.log(`5. logInput`); return result; }; const logResult = async (resolve, root, args, context, info) => { console.log(`2. logResult`); const result = await resolve(root, args, context, info); console.log(`4. logResult: ${JSON.stringify(result)}`); return result; }; const gateway = new SupergraphSchemaManager({ onStitchedSchema: async (schema) => { // Manipulate the schema return applyMiddleware(schema, logInput, logResult); }, });
Patch Changes
-
#552
b0bc26b
Thanks @ardatan! - Handle shared subscription root fields correctlyIn case of conflicting subscription root fields coming from different subgraphs or different entry points(multiple keys),
subscription was failing. -
Updated dependencies [
9144222
]:- @graphql-tools/[email protected]
- @graphql-tools/[email protected]
- @graphql-tools/[email protected]
@graphql-mesh/[email protected]
Patch Changes
-
#538
aab5441
Thanks @renovate! - dependencies updates:- Updated dependency
graphql-yoga@^5.10.11
↗︎ (from^5.10.6
, independencies
)
- Updated dependency
-
Updated dependencies [
b52c9ba
,9144222
,b0bc26b
]:- @graphql-tools/[email protected]
- @graphql-tools/[email protected]
- @graphql-tools/[email protected]
- @graphql-tools/[email protected]
- @graphql-tools/[email protected]
@graphql-hive/[email protected]
Patch Changes
-
#526
188a763
Thanks @renovate! - dependencies updates:- Updated dependency
@graphql-mesh/plugin-http-cache@^0.104.0
↗︎ (from^0.103.0
, independencies
)
- Updated dependency
-
#538
aab5441
Thanks @renovate! - dependencies updates:- Updated dependency
graphql-yoga@^5.10.11
↗︎ (from^5.10.6
, independencies
)
- Updated dependency
-
#539
df20361
Thanks @renovate! - dependencies updates:- Updated dependency
parse-duration@^2.0.0
↗︎ (from^1.1.0
, independencies
)
- Updated dependency
-
#555
836ab2c
Thanks @enisdenjo! - dependencies updates:- Removed dependency
parse-duration@^2.0.0
↗︎ (fromdependencies
)
- Removed dependency
-
#549
46888f1
Thanks @enisdenjo! - ExportgetGraphQLWSOptions
function that createsgraphql-ws
for the Hive GatewayAllowing the users to correctly set up WebSockets when using the Hive Gateway programmatically.
-
#555
836ab2c
Thanks @enisdenjo! - Bundleparse-duration
dependencyparse-duration
is ESM only starting from v2. We therefore bundle it in because doing so we transpile it to CJS and allow importing the GW in CJS. -
Updated dependencies [
aab5441
,46888f1
,180c2c4
,aab5441
,46888f1
,61f387c
]:- @graphql-hive/[email protected]
- @graphql-mesh/[email protected]
- @graphql-mesh/[email protected]
- @graphql-mesh/[email protected]
@graphql-mesh/[email protected]
Patch Changes
@graphql-mesh/[email protected]
Patch Changes
-
#538
aab5441
Thanks @renovate! - dependencies updates:- Updated dependency
graphql-yoga@^5.10.11
↗︎ (from^5.10.6
, inpeerDependencies
)
- Updated dependency
-
Updated dependencies [
aab5441
,46888f1
,180c2c4
,46888f1
,61f387c
]:- @graphql-hive/[email protected]
@graphql-hive/[email protected]
Patch Changes
-
#538
aab5441
Thanks @renovate! - dependencies updates:- Updated dependency
graphql-yoga@^5.10.11
↗︎ (from^5.10.6
, independencies
)
- Updated dependency
-
#549
46888f1
Thanks @enisdenjo! - dependen...
[email protected]
Pre-built binaries of the Hive Gateway for the @graphql-hive/[email protected] release.