@graphql-yoga/apollo-managed-federation
Changelog for @graphql-yoga/apollo-managed-federation: every release with its changes and the pull requests behind them.
1.0.0
Minor Changes
-
#4575
862447aThanks @egoodwinx! - Use@graphql-hive/loggerand add correlated, per-request logging (closes #4048)Every request now gets its own logger, available as
context.log(andserverContext.login plugin hooks), tagged with arequestId. Everything logged while handling a request can be correlated by that id.The request id is taken from the host integration if it already assigned one (e.g. Fastify’s
request.id), otherwise from the incomingx-request-idheader, otherwise generated. It is also sent back in thex-request-idresponse header. Configure it with the newrequestIdoption:createYoga({ requestId: { // don't trust the incoming header, recommended when clients can reach the server directly trustHeader: false, headerName: 'x-correlation-id', generateRequestId: () => myId() } })Pass
requestId: falseto disable it.At the
infolevel, a single “Request processed” line is logged per request with the method, path, operation name and type, response status, error count and duration. At thedebuglevel, more details about request processing are logged.Masked errors are now logged with the request’s logger, so they can be traced back to the request that caused them. Custom
maskErrorfunctions receive the request’s context as an optional fourth argument.The
@envelop/newrelic,@envelop/auth0,@envelop/resource-limitations,@envelop/statsd,@envelop/graphql-jit,@envelop/response-cacheand@envelop/response-cache-cloudflare-kvplugins accept a newlogoption for their own messages, instead of always writing to the console.@envelop/response-cache’sshouldCacheResultnow also receives the GraphQLcontext.Breaking Changes
- The
@graphql-yoga/loggerpackage has been removed.graphql-yogare-exportsLogger,MemoryLogWriterandLogLevelfrom@graphql-hive/loggerinstead. createLoggerand theYogaLoggertype are no longer exported. Usenew Logger(options)instead.- The
loggingoption now takesboolean | Logger | LogLevel, whereLoggeris the one from@graphql-hive/logger. yoga.loggerhas been renamed toyoga.log.- The
loggeroption ofuseGraphiQLanduseHealthCheckhas been removed. They now log through the request’s logger. @graphql-yoga/nestjsnow logs through Nest’sLoggerby default instead of not logging at all. Passlogging: falseto keep the previous behaviour.logging: trueon Fastify no longer logs through Fastify’s logger, pass it explicitly instead (see below).@envelop/apollo-federation,@envelop/auth0,@envelop/graphql-jit,@envelop/newrelic,@envelop/resource-limitations,@envelop/response-cache,@envelop/response-cache-cloudflare-kvand@envelop/statsdnow have a peer dependency on@graphql-hive/loggerthat you must install.@envelop/apollo-federation’sloggeroption now expects aLoggerfrom@graphql-hive/loggerand defaults tonew Logger()instead ofconsole.
Migration
Create loggers with
Logger:- import { createLogger } from 'graphql-yoga'; + import { Logger } from 'graphql-yoga'; createYoga({ - logging: createLogger('debug'), + logging: new Logger({ level: 'debug' }), });Use
loginstead ofloggeron the Yoga instance:const plugin = { onYogaInit({ yoga }) { - yoga.logger.info('ready'); + yoga.log.info('ready'); }, };Prefer the request-scoped logger inside resolvers and plugin hooks so the logs carry the request id:
const resolvers = { Query: { hello: (_, __, context) => { context.log.debug('resolving hello') return 'world' } } }If you use any of the
@envelop/*plugins listed above, install the logger:npm i @graphql-hive/loggerIf you depended on
@graphql-yoga/loggerdirectly, switch to@graphql-hive/logger:- import { Logger } from '@graphql-yoga/logger'; + import { Logger } from '@graphql-hive/logger';To keep logging through Fastify’s logger in
@graphql-yoga/nestjs:import { Logger } from 'graphql-yoga' import { PinoLogWriter } from '@graphql-hive/logger/writers/pino' // in your yoga driver options logging: new Logger({ writers: [new PinoLogWriter(app.log)] }) - The
-
#4574
79b0e8bThanks @egoodwinx! - ### Breaking Changes- Node: minimum supported version is now Node 22. Node 18 and 20 are no longer supported. Future releases will only support Node >=22.
- GraphQL: minimum supported version is now GraphQL 16. GraphQL 14 and 15 are no longer supported.
- Request body parsing: Yoga now limits request bodies to 25,000,000 bytes by default.
Enforcing this limit streams the body through a byte counter, making POST body parsing
asynchronous even for an in-memory body. As a result,
yoga.fetch()can return a Promise where it previously returned a synchronous Response, even when all resolvers and plugins are synchronous.
Migration
- If you’re on Node 18/20, upgrade to Node 22 or later before upgrading this package.
- If you’re on graphql 14/15, upgrade to graphql 16 or 17 first.
- Await
yoga.fetch()and response body parsing instead of relying on synchronous results. SetmaxRequestBodySize: falseincreateYogato disable the body-size limit and preserve synchronous parsing for in-memory bodies, but only if you enforce an appropriate request-body limit elsewhere.
Patch Changes
0.23.6
Patch Changes
- Updated dependencies
[
9294289]:- graphql-yoga@5.24.6
0.23.5
Patch Changes
- Updated dependencies []:
- graphql-yoga@5.24.5
0.23.4
Patch Changes
- Updated dependencies
[
d8b8860]:- graphql-yoga@5.24.4
0.23.3
Patch Changes
- #4604
c6febdcThanks @enisdenjo! - dependencies updates:- Updated dependency
@graphql-tools/federation@^4.5.3↗︎ (from^4.0.0, independencies)
- Updated dependency
- Updated dependencies
[
c6febdc]:- graphql-yoga@5.24.3
0.23.2
Patch Changes
- Updated dependencies
[
c08efde]:- graphql-yoga@5.24.2
0.23.1
Patch Changes
- Updated dependencies
[
c6a9aa4]:- graphql-yoga@5.24.1
0.23.0
Patch Changes
-
#4577
7bff35cThanks @egoodwinx! - Add homepage and bugs.url to package.json files -
Updated dependencies [
7bff35c,3763aca]:- graphql-yoga@5.24.0
0.22.0
Patch Changes
0.21.0
Minor Changes
-
#4545
94ebe5bThanks @egoodwinx! - Update to support graphql-js 17Bump package versions, fix expected typing, and update compatability with subscribe.
Patch Changes
- Updated dependencies
[
94ebe5b]:- graphql-yoga@5.22.0
0.20.3
Patch Changes
- Updated dependencies
[
04014d2]:- graphql-yoga@5.21.3
0.20.2
Patch Changes
- Updated dependencies
[
39b55ba]:- graphql-yoga@5.21.2
0.20.1
Patch Changes
- Updated dependencies
[
4b43efd]:- graphql-yoga@5.21.1
0.20.0
Patch Changes
- Updated dependencies
[
e263f7e]:- graphql-yoga@5.21.0
0.19.0
Patch Changes
- Updated dependencies
[
93f1dc0]:- graphql-yoga@5.20.0
0.18.0
Patch Changes
- Updated dependencies
[
7e0aaf6]:- graphql-yoga@5.19.0
0.17.1
Patch Changes
0.17.0
Patch Changes
- Updated dependencies
[
3eabd17]:- graphql-yoga@5.18.0
0.16.1
Patch Changes
- Updated dependencies
[
c27f550]:- graphql-yoga@5.17.1
0.16.0
Patch Changes
0.15.2
Patch Changes
- Updated dependencies
[
ba38629]:- graphql-yoga@5.16.2
0.15.1
Patch Changes
0.15.0
Patch Changes
0.14.0
Minor Changes
Patch Changes
- #4171
17e574aThanks @renovate! - dependencies updates:- Updated dependency
@graphql-tools/federation@^4.0.0↗︎ (from^3.0.0, independencies)
- Updated dependency
- Updated dependencies
[
e7b8906]:- graphql-yoga@5.15.2
0.13.1
Patch Changes
- Updated dependencies
[
ecd605b]:- graphql-yoga@5.15.1
0.13.0
Patch Changes
0.12.0
Patch Changes
0.11.5
Patch Changes
- Updated dependencies
[
8b41a52]:- graphql-yoga@5.13.5
0.11.4
Patch Changes
-
#3995
000c33dThanks @enisdenjo! - Update whatwg-node packagesIn light of https://github.com/ardatan/whatwg-node/pull/2305. Please upgrade as soon as possible!
-
Updated dependencies [
000c33d]:- graphql-yoga@5.13.4
0.11.3
Patch Changes
0.11.2
Patch Changes
0.11.1
Patch Changes
- Updated dependencies
[
dee7995]:- graphql-yoga@5.13.1
0.11.0
Patch Changes
0.10.2
Patch Changes
- Updated dependencies
[
a6b3de9]:- graphql-yoga@5.12.2
0.10.1
Patch Changes
- Updated dependencies
[
fbf328c]:- graphql-yoga@5.12.1
0.10.0
Patch Changes
0.9.0
Patch Changes
0.8.6
Patch Changes
- Updated dependencies
[
1c055f5]:- graphql-yoga@5.10.11
0.8.5
Patch Changes
- Updated dependencies []:
- graphql-yoga@5.10.10
0.8.4
Patch Changes
0.8.3
Patch Changes
- Updated dependencies
[
ed344ea]:- graphql-yoga@5.10.8
0.8.2
Patch Changes
- #3567
1df4912Thanks @ardatan! - dependencies updates:- Removed dependency
@whatwg-node/disposablestack@^0.0.5↗︎ (fromdependencies)
- Removed dependency
- Updated dependencies
[
8fee214,1df4912]:- graphql-yoga@5.10.7
0.8.1
Patch Changes
- Updated dependencies
[
121ccba]:- graphql-yoga@5.10.6
0.8.0
Minor Changes
-
#3532
57e7701Thanks @ardatan! -supergraphManageroption is not available anymore, you can passSupergraphManagerdirectly to the plugin instead;- useManagedFederation({ supergraphManager }) + useManagedFederation(supergraphManager)
Patch Changes
- #3532
57e7701Thanks @ardatan! - dependencies updates:- Updated dependency
@graphql-tools/federation@^3.0.0↗︎ (from2.1.0, independencies) - Added dependency
@whatwg-node/disposablestack@^0.0.5↗︎ (todependencies)
- Updated dependency
- Updated dependencies
[
eca7cd1,05fe345]:- graphql-yoga@5.10.5
0.7.4
Patch Changes
- Updated dependencies
[
944ecd5]:- graphql-yoga@5.10.4
0.7.3
Patch Changes
0.7.2
Patch Changes
0.7.1
Patch Changes
- Updated dependencies
[
20cd9b6]:- graphql-yoga@5.10.1
0.7.0
Patch Changes
- Updated dependencies
[
f81501c]:- graphql-yoga@5.10.0
0.6.0
Patch Changes
0.5.0
Patch Changes
0.4.0
Patch Changes
0.3.3
Patch Changes
- Updated dependencies
[
0866c1b]:- graphql-yoga@5.6.3
0.3.2
Patch Changes
0.3.1
Patch Changes
- Updated dependencies
[
4252e3d]:- graphql-yoga@5.6.1
0.3.0
Patch Changes
- Updated dependencies
[
9f3f945]:- graphql-yoga@5.6.0
0.2.0
Patch Changes
- Updated dependencies
[
0208024]:- graphql-yoga@5.5.0
0.1.0
Patch Changes
- #3328
9b468ecThanks @EmrysMyrddin! - dependencies updates:- Updated dependency
@graphql-tools/federation@2.1.0↗︎ (from^2.0.0, independencies)
- Updated dependency
- Updated dependencies
[
4cd43b9,fdd902c,d5dfe99,7335a82,f9aa1cd]:- graphql-yoga@5.4.0