[dependabot]

Bumps graphql-yoga from 5.24.6 to 6.0.1.

Release notes

Sourced from graphql-yoga's releases.

graphql-yoga@6.0.1

Patch Changes

• #4634 d73f61c Thanks @​ardatan! - dependencies: bump @whatwg-node/server to ^0.13.1 so native Request subclasses (Next.js NextRequest, including the App Router proxyNextRequest Proxy) are classified as the platform Fetch API. The body-size limiter no longer throws a cross-realm TypeError / 500 on those requests; oversized bodies still return 413.

  See graphql-hive/graphql-yoga#4633 and ardatan/whatwg-node#3717.

graphql-yoga@6.0.0

Major Changes

• #4575 862447a Thanks @​egoodwinx! - Use @graphql-hive/logger and add correlated, per-request logging (closes #4048)

  Every request now gets its own logger, available as context.log (and serverContext.log in plugin hooks), tagged with a requestId. 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 incoming x-request-id header, otherwise generated. It is also sent back in the x-request-id response header. Configure it with the new requestId option:

  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: false to disable it.

  At the info level, a single "Request processed" line is logged per request with the method, path, operation name and type, response status, error count and duration. At the debug level, 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 maskError functions receive the request's context as an optional fourth

... (truncated)

Changelog

Sourced from graphql-yoga's changelog.

6.0.1

Patch Changes

• #4634 d73f61c Thanks @​ardatan! - dependencies: bump @whatwg-node/server to ^0.13.1 so native Request subclasses (Next.js NextRequest, including the App Router proxyNextRequest Proxy) are classified as the platform Fetch API. The body-size limiter no longer throws a cross-realm TypeError / 500 on those requests; oversized bodies still return 413.

  See graphql-hive/graphql-yoga#4633 and ardatan/whatwg-node#3717.

6.0.0

Major Changes

• #4575 862447a Thanks @​egoodwinx! - Use @graphql-hive/logger and add correlated, per-request logging (closes #4048)

  Every request now gets its own logger, available as context.log (and serverContext.log in plugin hooks), tagged with a requestId. 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 incoming x-request-id header, otherwise generated. It is also sent back in the x-request-id response header. Configure it with the new requestId option:

  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: false to disable it.

  At the info level, a single "Request processed" line is logged per request with the method, path, operation name and type, response status, error count and duration. At the debug level, more details about request processing are logged.

... (truncated)

Commits

• 9d7bb3a chore(release): update monorepo packages versions (#4635)
• d73f61c test(yoga): cover Request subclass body-size limit (#4633) (#4634)
• 88c3a06 chore(release): update monorepo packages versions (#4629)
• 862447a feat!: update logging to use hive logger and add more logging (#4575)
• be89d05 chore(deps)!: bump @graphql-tools/* to majors (utils@13) (#4623)
• 5334079 fix(yoga): drop redundant native TransformStream swap in body-size limit (#4622)
• 79b0e8b chore(deps)!: drop support for node <22 and graphql <16 (#4574)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)