Skip to content

chore(deps): update dependency graphql-yoga to ^5.24.5 - #26

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/graphql-yoga-5.x
Open

chore(deps): update dependency graphql-yoga to ^5.24.5#26
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/graphql-yoga-5.x

Conversation

@renovate

@renovate renovate Bot commented Sep 1, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
graphql-yoga (source) ^5.1.1 → ^5.24.5 age confidence

Release Notes

graphql-hive/graphql-yoga (graphql-yoga)

v5.24.5

Compare Source

v5.24.4

Compare Source

Patch Changes

v5.24.3

Compare Source

Patch Changes

v5.24.2

Compare Source

Patch Changes

  • #​4589
    c08efde
    Thanks @​egoodwinx! - Remove the built-in subscriptions driver
    option and its graphql-ws / subscriptions-transport-ws wiring (previously implemented via
    @nestjs/graphql's GqlSubscriptionService).

    Fix open handle leak in multipart tests.

    @nestjs/graphql v14 (required for NestJS 12 support) dropped server-side support for
    subscriptions-transport-ws, and the driver-level graphql-ws integration held a socket open
    after shutdown. Rather than keep a partial, driver-managed subscriptions setup, YogaDriver and
    YogaFederationDriver no longer accept a subscriptions option. Wire up subscriptions yourself
    using GraphQL Yoga's own subscription support (e.g. the graphql-ws package, or
    @graphql-yoga/plugin-graphql-sse) the same way you would for a standalone graphql-yoga server.

v5.24.1

Compare Source

Patch Changes

  • #​4586
    c6a9aa4
    Thanks @​ardatan! - Fixes the issue thrown in the plugin that limits
    the incoming request body's size, when the incoming Request object is not the instance of the
    fetchAPI.Request which is usually the ponyfill implementation from @whatwg-node/node-fetch.

    This will be fixed in the following breaking release in @whatwg-node/node-fetch but in order to
    unblock the current users of GraphQL Yoga, a small normalization layer has been added to the
    plugin as a temporary workaround.

    Since the native Request.body is a native ReadableStream, that doesn't support other
    TransformStream implementation to its pipeThrough method, the limiting implementation didn't
    work properly.

    When the user ran Yoga within Next.js that uses the native Request object, it threw a
    TypeError which causes a cryptic 500 Internal Server Error for Next.js users.

    This workaround checks whether the incoming Request's body object is an instance of the native
    ReadableStream and applies the appropriate TransformStream implementation to ensure the
    request body size limiting works correctly.

v5.24.0

Compare Source

Minor Changes

  • #​4580
    3763aca
    Thanks @​egoodwinx! - Limit the size of incoming HTTP request
    bodies by default to protect against denial-of-service attacks from oversized payloads.

    Requests whose Content-Length exceeds the limit are rejected with an HTTP 413 response before
    the body is read, and the limit is also enforced while streaming the body so that requests with a
    missing, incorrect, or chunked-transfer-encoded body are covered too.

    The default limit is 25 MB. Configure it with the new maxRequestBodySize option, or set it to
    false to disable the limit (not recommended unless an upstream reverse proxy already enforces
    one):

    createYoga({
  // Allow bodies up to 25 MB
  maxRequestBodySize: 25_000_000
})

    Also return an HTTP 400 response for malformed multipart/form-data requests (e.g. a missing or
    invalid boundary), instead of masking the parse error as a generic 500 Internal Server Error.

Patch Changes

v5.23.0

Compare Source

Patch Changes

  • #​4569
    c80f43c
    Thanks @​Urigo! - Serve the favicon of the built-in GraphiQL and
    landing pages from a file that stays in the repository (packages/render-graphiql/favicon.ico)
    now that the website sources moved.

  • #​4573
    d3b4164
    Thanks @​cpruijsen! - Keep SSE keep-alive pings running when the
    stream reports backpressure (desiredSize === 0) instead of treating a full queue as a closed
    connection.

  • Updated dependencies
    [b70ad4a]:

v5.22.0

Compare Source

Minor Changes

  • #​4545
    94ebe5b
    Thanks @​egoodwinx! - Update to support graphql-js 17

    Bump package versions, fix expected typing, and update compatability with subscribe.

Patch Changes

v5.21.3

Compare Source

Patch Changes

v5.21.2

Compare Source

Patch Changes

v5.21.1

Compare Source

Patch Changes

v5.21.0

Compare Source

Minor Changes

  • #​4430
    e263f7e
    Thanks @​ardatan! - Short-circuit response in onRequestParse hook

    In the onRequestParse hook, if a response is sent using endResponse, we should short-circuit
    the request parsing and return that response immediately. This allows users to handle certain
    requests entirely within the onRequestParse hook without needing to go through the rest of the
    request processing pipeline.

    const plugin = {
  onRequestParse({ endResponse }) {
    if (/* some condition */) {
      endResponse(new Response('Short-circuited response'));
    }
  },
};

    Or you can also short-circuit the response inside the request parser:

    const plugin = {
  onRequestParse({ setRequestParser }) {
    setRequestParser(req => {
      if (req.url === '/short-circuit') {
        return new Response('Short-circuited response')
      }
      // Otherwise, return the parsed parameters as usual
      return parseRequestNormally(req)
    })
  }
}

v5.20.0

Compare Source

Minor Changes

  • #​4428
    93f1dc0
    Thanks @​ardatan! - Support changing graphqlEndpoint after
    initialization;

    const yoga = createYoga({
  schema,
  logging: false,
  plugins: [
    {
      onYogaInit({ yoga }) {
        // Inside the plugin
        yoga.graphqlEndpoint = `/(graphql|my-custom-path)`
      }
    }
  ]
})

// Or after the initialization
yoga.graphqlEndpoint = `/(graphql|my-custom-path)`

v5.19.0

Compare Source

Minor Changes

v5.18.1

Compare Source

Patch Changes

  • #​4345
    9a221c3
    Thanks @​ardatan! - Fix error isolation in batched GraphQL operations

    When processing batched GraphQL requests, an error in one operation would previously cause the
    entire batch to fail. This change wraps each batched operation in error handling so that
    individual operation errors are caught and returned as GraphQL errors for that specific operation,
    while other operations in the batch continue to execute successfully.

  • #​4346
    f98149a
    Thanks @​ardatan! - dependencies updates:

v5.18.0

Compare Source

Minor Changes
  • #​4312
    3eabd17
    Thanks @​ardatan! - Export GraphiQLRenderer type which is the
    signature for renderGraphiQL option of Yoga configuration

v5.17.1

Compare Source

Patch Changes

v5.17.0

Compare Source

Minor Changes

  • #​4288
    66c370c
    Thanks @​EmrysMyrddin! - Add experimental support for
    coordinate error attribute proposal.

    The coordinate attribute indicates the coordinate in the schema of the resolver which
    experienced the errors. It allows for an easier error source identification than with the path
    which can be difficult to walk, or even lead to unsolvable ambiguities when using Union or
    Interface types.

v5.16.2

Compare Source

Patch Changes

  • #​4270
    ba38629
    Thanks @​ardatan! - Fixes the bug where the error masking incorrectly
    sets http.unexpected instead of just unexpected.

    {
  "extensions": {
-    "http": {
      "unexpected": true
-    }
  }
}

v5.16.1

Compare Source

Patch Changes

v5.16.0

Compare Source

Minor Changes
Patch Changes
  • #​4191
    0a7a635
    Thanks @​ardatan! - Fix workers' loading in online GraphiQL mode, so
    that Monaco features like autocomplete can work properly

v5.15.2

Compare Source

Patch Changes
  • e7b8906
    Thanks @​ardatan! - Bump URL Loader in GraphiQL to the latest to
    remove extra DOWNSTREAM_SERVICE_ERROR code in the errors

v5.15.1

Compare Source

Patch Changes

v5.15.0

Compare Source

Minor Changes
Patch Changes

v5.14.0

Compare Source

Minor Changes

v5.13.5

Compare Source

Patch Changes

v5.13.4

Compare Source

Patch Changes

v5.13.3

Compare Source

Patch Changes

v5.13.2

Compare Source

Patch Changes

v5.13.1

Compare Source

Patch Changes

v5.13.0

Compare Source

Minor Changes

  • #​3793
    63b78d5
    Thanks @​EmrysMyrddin! - Add new Instrumentation API

    Introduction of a new API allowing to instrument the graphql pipeline.

    This new API differs from already existing Hooks by not having access to input/output of phases.
    The goal of Instrumentation is to run allow running code before, after or around the whole
    process of a phase    , including plugins hooks executions.

    The main use case of this new API is observability (monitoring, tracing, etc...).

Basic usage
import { createYoga } from 'graphql-yoga'
import Sentry from '@sentry/node'
import schema from './schema'

const server = createYoga({
  schema,
  plugins: [
    {
      instrumentation: {
        request: ({ request }, wrapped) =>
          Sentry.startSpan({ name: 'Graphql Operation' }, async () => {
            try {
              await wrapped()
            } catch (err) {
              Sentry.captureException(err)
            }
          })
      }
    }
  ]
})
Multiple instrumentation plugins

It is possible to have multiple instrumentation plugins (Prometheus and Sentry for example), they
will be automatically composed by envelop in the same order than the plugin array (first is
outermost, last is inner most).

import { createYoga } from 'graphql-yoga'
import schema from './schema'

const server = createYoga({
  schema,
  plugins: [useSentry(), useOpentelemetry()]
})
Custom instrumentation ordering

If the default composition ordering doesn't suite your need, you can manually compose
instrumentation. This allows to have a different execution order of hooks and instrumentation.

import { composeInstrumentation, createYoga } from 'graphql-yoga'
import schema from './schema'

const { instrumentation: sentryInstrumentation, ...sentryPlugin } = useSentry()
const { instrumentation: otelInstrumentation, ...otelPlugin } = useOpentelemetry()
const instrumentation = composeInstrumentation([otelInstrumentation, sentryInstrumentation])

const server = createYoga({
  schema,
  plugins: [{ instrumentation }, useSentry(), useOpentelemetry()]
})
Patch Changes

v5.12.2

Compare Source

Patch Changes

v5.12.1

Patch Changes

v5.12.0

Minor Changes
Patch Changes

v5.11.0

Compare Source

Minor Changes

  • #​3727
    5fd15b8
    Thanks @​EmrysMyrddin! - Allow to configure the endpoint used by
    GraphiQL to send requests.

  • #​3736
    d13b8a4
    Thanks @​ardatan! - Now it is possible to replace or wrap the logic
    how GraphQLParams handled;

    By default Yoga calls Envelop to handle the parameters, but now you can replace it with your own
    logic.

    Example: Wrap the GraphQL handling pipeline in an AsyncLocalStorage

    function myPlugin(): Plugin {
  const context = new AsyncLocalStorage();
  return {
    onParams({ paramsHandler, setParamsHandler }) {
      const store = { foo: 'bar' }
      setParamsHandler(payload => context.run(store, paramsHandler, payload))
   }
}

v5.10.11

Compare Source

Patch Changes

v5.10.10

Compare Source

Patch Changes

v5.10.9

Compare Source

Patch Changes

v5.10.8

Compare Source

Patch Changes
  • #​3588
    ed344ea
    Thanks @​ardatan! - Mark createLRUCache utility as deprecated, and
    export it as _createLRUCache marking it as an internal utility

v5.10.7

Compare Source

Patch Changes

v5.10.6

Compare Source

Patch Changes

v5.10.5

Compare Source

Patch Changes

v5.10.4

Compare Source

Patch Changes

v5.10.3

Compare Source

Patch Changes

v5.10.2

Compare Source

Patch Changes

  • #​3491
    7a413bc
    Thanks @​n1ru4l! - dependencies updates:

  • #​3491
    7a413bc
    Thanks @​n1ru4l! - Fix issue where context values being shared between
    batched requests.

    A bug within @whatwg-node/server caused properties assigned to a batched requests context to be
    propagated to all other batched requests contexts. It is resolved by updating the dependency of
    @whatwg-node/server to 0.9.55.

v5.10.1

Compare Source

Patch Changes

v5.10.0

Compare Source

Minor Changes

v5.9.0

Compare Source

Minor Changes
Patch Changes

v5.8.0

Compare Source

Minor Changes
Patch Changes

v5.7.0

Compare Source

Minor Changes

  • #​3331
    5dae4ab
    Thanks @​EmrysMyrddin! - Expose server context in
    onResultProcessHook. In particular, this gives access to the waitUntil method to cleanly
    handle hanging promises.

  • #​3331
    5dae4ab
    Thanks @​EmrysMyrddin! - New hook: onExecutionResult which is
    triggered when an execution is done on the pipeline. If it is a batched operation, this is called
    per each operation in the batch

  • #​3331
    5dae4ab
    Thanks @​EmrysMyrddin! - Expose the already existing waitUntil
    method from the server context.

Patch Changes

v5.6.3

Compare Source

Patch Changes

v5.6.2

Compare Source

Patch Changes

v5.6.1

[Compare Source](https://redirect.github.com

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every 8 months on the first day of the month"
  • 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.

@github-actions

github-actions Bot commented Sep 1, 2025 •
edited
Loading

Copy link
Copy Markdown

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 0% 0 / 571
🔵 Statements 0% 0 / 571
🔵 Functions 0% 0 / 6
🔵 Branches 0% 0 / 6
File CoverageNo changed files found.
Generated in workflow #1003 for commit 7f9f854 by the Vitest Coverage Report Action

@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 8d207b9 to 480ab5c Compare September 6, 2025 22:13
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.15.1 chore(deps): update dependency graphql-yoga to ^5.15.2 Sep 6, 2025
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 480ab5c to 2a02928 Compare September 19, 2025 19:23
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.15.2 chore(deps): update dependency graphql-yoga to ^5.16.0 Sep 19, 2025
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 2a02928 to 9559dfb Compare October 21, 2025 19:38
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 9559dfb to 5caf577 Compare November 4, 2025 18:33
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.16.0 chore(deps): update dependency graphql-yoga to ^5.16.1 Nov 4, 2025
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 5caf577 to 2432d36 Compare November 7, 2025 04:13
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.16.1 chore(deps): update dependency graphql-yoga to ^5.16.2 Nov 7, 2025
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 2432d36 to 7b9871b Compare November 10, 2025 22:46
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 7b9871b to afcf6b4 Compare November 18, 2025 13:48
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from afcf6b4 to 32baf07 Compare November 28, 2025 12:05
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.16.2 chore(deps): update dependency graphql-yoga to ^5.17.0 Nov 28, 2025
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 32baf07 to 6a523b2 Compare December 2, 2025 03:53
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.17.0 chore(deps): update dependency graphql-yoga to ^5.17.1 Dec 2, 2025
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 6a523b2 to bfc0913 Compare December 18, 2025 15:37
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.17.1 chore(deps): update dependency graphql-yoga to ^5.18.0 Dec 18, 2025
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from bfc0913 to 9a4f36c Compare January 8, 2026 21:08
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 9a4f36c to eb03496 Compare January 23, 2026 20:53
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from eb03496 to e589afc Compare February 12, 2026 12:40
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from e589afc to cfbd723 Compare March 6, 2026 19:04
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.18.0 chore(deps): update dependency graphql-yoga to ^5.18.1 Mar 6, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from cfbd723 to 95933e9 Compare April 1, 2026 15:12
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.18.1 chore(deps): update dependency graphql-yoga to ^5.19.0 Apr 1, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 95933e9 to 48d48bc Compare April 3, 2026 18:42
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.19.0 chore(deps): update dependency graphql-yoga to ^5.20.0 Apr 3, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 48d48bc to 6347f02 Compare April 4, 2026 22:27
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.20.0 chore(deps): update dependency graphql-yoga to ^5.21.0 Apr 4, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 6347f02 to ddd469e Compare April 29, 2026 17:09
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from ddd469e to 073bb0c Compare June 2, 2026 20:12
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.21.0 chore(deps): update dependency graphql-yoga to ^5.21.1 Jun 2, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 073bb0c to 665ffa8 Compare June 8, 2026 20:52
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.21.1 chore(deps): update dependency graphql-yoga to ^5.21.2 Jun 8, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch 2 times, most recently from 31d5520 to 88b44e9 Compare July 18, 2026 04:15
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 88b44e9 to 4fe4974 Compare August 13, 2026 12:34
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.21.2 chore(deps): update dependency graphql-yoga to ^5.21.3 Aug 13, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 4fe4974 to 2323a52 Compare August 19, 2026 10:48
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.21.3 chore(deps): update dependency graphql-yoga to ^5.22.0 Aug 19, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 2323a52 to fc46828 Compare August 26, 2026 10:38
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch 2 times, most recently from 3efc092 to dc7e217 Compare September 11, 2026 19:09
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.22.0 chore(deps): update dependency graphql-yoga to ^5.23.0 Sep 11, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from dc7e217 to b7435ba Compare September 16, 2026 17:58
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.23.0 chore(deps): update dependency graphql-yoga to ^5.24.0 Sep 16, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from b7435ba to ea06ef6 Compare September 17, 2026 22:00
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.24.0 chore(deps): update dependency graphql-yoga to ^5.24.1 Sep 17, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch 2 times, most recently from f4002b0 to 754b1c3 Compare October 5, 2026 19:43
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.24.1 chore(deps): update dependency graphql-yoga to ^5.24.2 Oct 5, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 754b1c3 to 896c59a Compare October 8, 2026 17:24
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.24.2 chore(deps): update dependency graphql-yoga to ^5.24.4 Oct 8, 2026
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from 896c59a to fadc20b Compare October 13, 2026 13:57
@renovate
renovate Bot force-pushed the renovate/graphql-yoga-5.x branch from fadc20b to 7f9f854 Compare October 13, 2026 21:22
@renovate renovate Bot changed the title chore(deps): update dependency graphql-yoga to ^5.24.4 chore(deps): update dependency graphql-yoga to ^5.24.5 Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants