chore(deps): update dependency graphql-yoga to ^5.13.2 - autoclosed by renovate[bot] · Pull Request #24 · productdevbookcom/ts-relay-cursor-paging

renovate · 2025-01-01T01:34:30Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
graphql-yoga (source)	`^5.1.1` -> `^5.13.2`

Release Notes

dotansimha/graphql-yoga (graphql-yoga)

`v5.13.2`

Compare Source

Patch Changes

#3876
abe91bd
Thanks @EmrysMyrddin! - Re-export the utility type
AsyncIterableIteratorOrValue from @envelop/core.
#3874
9311842
Thanks @EmrysMyrddin! - Gives access to the request in the
operation instrument payload, since the request is not in the context yet.

`v5.13.1`

Compare Source

Patch Changes

#3865
dee7995
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @envelop/core@^5.2.3 ↗︎ (from
  ^5.2.1, in dependencies)
- Updated dependency
  @whatwg-node/server@^0.10.1 ↗︎
  (from ^0.10.0, in dependencies)
- Added dependency
  @envelop/instrumentation@^1.0.0 ↗︎
  (to dependencies)
- Removed dependency
  @envelop/instruments@^1.0.0 ↗︎
  (from dependencies)

`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 '@&#8203;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

#3793
63b78d5
Thanks @EmrysMyrddin! - dependencies updates:
- Updated dependency
  @envelop/core@^5.2.1 ↗︎ (from
  ^5.0.2, in dependencies)
- Added dependency
  @envelop/instrumentation@^1.0.0 ↗︎
  (to dependencies)
- Added dependency
  @whatwg-node/promise-helpers@^1.2.4 ↗︎
  (to dependencies)
#3855
6ed67e8
Thanks @renovate! - dependencies updates:
- Updated dependency
  @whatwg-node/server@^0.10.0 ↗︎
  (from ^0.9.71, in dependencies)

`v5.12.2`

Compare Source

Patch Changes

#3837
a6b3de9
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @whatwg-node/server@^0.9.71 ↗︎
  (from ^0.9.69, in dependencies)

`v5.12.1`

Patch Changes

#3808
fbf328c
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @whatwg-node/fetch@^0.10.5 ↗︎
  (from ^0.10.1, in dependencies)
- Updated dependency
  @whatwg-node/server@^0.9.69 ↗︎
  (from ^0.9.64, in dependencies)

`v5.12.0`

Minor Changes

#3672
5150146
Thanks @ardatan! - extensions.code usage for specific errors

Patch Changes

#3764
96498ee
Thanks @slagiewka! - Pass through disposeOnProcessTerminate to
createServerAdapter
#3672
5150146
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @graphql-tools/executor@^1.4.0 ↗︎
  (from ^1.3.7, in dependencies)

`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

#3712
1c055f5
Thanks @ardatan! - Show deprecated input fields, arguments and all
other input values in GraphiQL

Patch Changes

#3620
d24c5d5
Thanks @enisdenjo! - Bump dset dependency handling the
CVE-2024-21529

https://security.snyk.io/vuln/SNYK-JS-DSET-7116691
#3620
d24c5d5
Thanks @enisdenjo! - dependencies updates:
- Updated dependency dset@^3.1.4 ↗︎ (from
  ^3.1.1, in dependencies)

`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

#3547
8fee214
Thanks @Urigo! - dependencies updates:
- Updated dependency
  @graphql-tools/executor@^1.3.7 ↗︎
  (from ^1.3.5, in dependencies)
- Updated dependency
  @graphql-tools/schema@^10.0.11 ↗︎
  (from ^10.0.10, in dependencies)
- Updated dependency
  @graphql-tools/utils@^10.6.2 ↗︎
  (from ^10.6.1, in dependencies)
- Updated dependency
  @whatwg-node/server@^0.9.63 ↗︎
  (from ^0.9.60, in dependencies)
#3567
1df4912
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @whatwg-node/server@^0.9.64 ↗︎
  (from ^0.9.63, in dependencies)

`v5.10.6`

Compare Source

Patch Changes

#3551
121ccba
Thanks @bridges-wood! - Fix stylesheet reference in graphiql

`v5.10.5`

Compare Source

Patch Changes

#3546
eca7cd1
Thanks @EmrysMyrddin! - Add documentation for Plugin hooks
#3549
05fe345
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @graphql-tools/executor@^1.3.7 ↗︎
  (from ^1.3.5, in dependencies)
- Updated dependency
  @graphql-tools/schema@^10.0.11 ↗︎
  (from ^10.0.10, in dependencies)
- Updated dependency
  @graphql-tools/utils@^10.6.2 ↗︎
  (from ^10.6.1, in dependencies)
- Updated dependency
  @whatwg-node/server@^0.9.63 ↗︎
  (from ^0.9.60, in dependencies)
Updated dependencies []:
- @graphql-yoga/subscription @5.0.2

`v5.10.4`

Compare Source

Patch Changes

#3520
944ecd5
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @envelop/core@^5.0.2 ↗︎ (from
  ^5.0.1, in dependencies)
- Updated dependency
  @graphql-tools/executor@^1.3.5 ↗︎
  (from ^1.3.3, in dependencies)
- Updated dependency
  @graphql-tools/schema@^10.0.10 ↗︎
  (from ^10.0.4, in dependencies)
- Updated dependency
  @graphql-tools/utils@^10.6.1 ↗︎
  (from ^10.3.2, in dependencies)
- Updated dependency
  @whatwg-node/server@^0.9.60 ↗︎
  (from ^0.9.55, in dependencies)
- Updated dependency tslib@^2.8.1 ↗︎ (from
  ^2.5.2, in dependencies)

`v5.10.3`

Compare Source

Patch Changes

#3501
c93366d
Thanks @enisdenjo! - dependencies updates:
- Updated dependency
  @graphql-tools/executor@^1.3.3 ↗︎
  (from ^1.3.0, in dependencies)
#3501
c93366d
Thanks @enisdenjo! - Update transport executors containing
improvements and fixes

`v5.10.2`

Compare Source

Patch Changes

#3491
7a413bc
Thanks @n1ru4l! - dependencies updates:
- Updated dependency
  @whatwg-node/server@^0.9.55 ↗︎
  (from ^0.9.54, in dependencies)
#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

#3712
1c055f5
Thanks @ardatan! - Show deprecated input fields, arguments and all
other input values in GraphiQL

`v5.10.0`

Compare Source

Minor Changes

#3462
f81501c
Thanks @maeldur! - Correctly handle HTTP GET requests with ?
characters in the query search string.

`v5.9.0`

Compare Source

Minor Changes

#3464
87ee333
Thanks @n1ru4l! - Inject initial context into onParams hook.

Patch Changes

#3457
2523d9f
Thanks @kroupacz! - ### Fixed
- propagation of Yoga version

`v5.8.0`

Compare Source

Minor Changes

18fe916
Thanks @kroupacz! - Add version property to get version of Yoga

Patch Changes

#3445
6bb19ed
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @whatwg-node/fetch@^0.9.22 ↗︎
  (from ^0.9.18, in dependencies)
- Updated dependency
  @whatwg-node/server@^0.9.50 ↗︎
  (from ^0.9.44, in dependencies)

`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

#3331
5dae4ab
Thanks @EmrysMyrddin! - dependencies updates:
- Updated dependency
  @whatwg-node/server@^0.9.44 ↗︎
  (from ^0.9.41, in dependencies)

`v5.6.3`

Compare Source

Patch Changes

#3400
0866c1b
Thanks @n1ru4l! - Restores compatibility with
RFC1341: The Multipart Content-Type by
including preceding \r\n for initial boundary delimiter when using the multipart response
protocol.

This makes Yoga compatible with libraries that strictly follow the response protocol, such as
fetch-multipart-graphql.

`v5.6.2`

Compare Source

Patch Changes

#3357
b7bf47b
Thanks @renovate! - dependencies updates:
- Updated dependency
  @whatwg-node/server@^0.9.41 ↗︎
  (from ^0.9.40, in dependencies)
#3384
81a736b
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @envelop/core@^5.0.1 ↗︎ (from
  ^5.0.0, in dependencies)
- Updated dependency
  @graphql-tools/executor@^1.3.0 ↗︎
  (from ^1.2.5, in dependencies)
- Updated dependency
  @graphql-tools/schema@^10.0.4 ↗︎
  (from ^10.0.0, in dependencies)
- Updated dependency
  @graphql-tools/utils@^10.3.2 ↗︎
  (from ^10.1.0, in dependencies)
- Updated dependency
  @whatwg-node/fetch@^0.9.18 ↗︎
  (from ^0.9.17, in dependencies)
- Updated dependency
  @whatwg-node/server@^0.9.40 ↗︎
  (from ^0.9.36, in dependencies)

`v5.6.1`

Compare Source

Patch Changes

#3338
4252e3d
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @whatwg-node/server@^0.9.36 ↗︎
  (from ^0.9.33, in dependencies)

`v5.6.0`

Compare Source

Minor Changes

#3333
9f3f945
Thanks @ardatan! - By default, Yoga does not allow extra parameters
in the request body other than query, operationName, extensions, and variables, then
throws 400 HTTP Error. This change adds a new option called extraParamNames to allow extra
parameters in the request body.

import { createYoga } from 'graphql-yoga'

const yoga = createYoga({
  /* other options */
  extraParamNames: ['extraParam1', 'extraParam2']
})

const res = await yoga.fetch('/graphql', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    query: 'query { __typename }',
    extraParam1: 'value1',
    extraParam2: 'value2'
  })
})

console.assert(res.status === 200)

`v5.5.0`

Compare Source

Minor Changes

#3332
0208024
Thanks @ardatan! - Customize the landing page by passing a custom
renderer that returns Response to the landingPage option

import { createYoga } from 'graphql-yoga'

const yoga = createYoga({
  landingPage: ({ url, fetchAPI }) => {
    return new fetchAPI.Response(
      /* HTML */ `
        <!doctype html>
        <html>
          <head>
            <title>404 Not Found</title>
          </head>
          <body>
            <h1>404 Not Found</h1>
            <p>Sorry, the page (${url.pathname}) you are looking for could not be found.</p>
          </body>
        </html>
      `,
      {
        status: 404,
        headers: {
          'Content-Type': 'text/html'
        }
      }
    )
  }
})

`v5.4.0`

Compare Source

Minor Changes

#3314
d5dfe99
Thanks @EmrysMyrddin! - Allow for full customization of the
GraphiQL page.

Props from the YogaGraphiQL are now forwarded to the underlying GraphiQL components.

The graphiql option field type of the Yoga server as also been updated to document which options
are configurable from the server side. Only serializable options are available.
#3255
7335a82
Thanks @nissy-dev! - support shouldPersistHeaders option in
GraphiQL plugin

Patch Changes

#3325
4cd43b9
Thanks @n1ru4l! - Fix TypeScript compatibility with type: "module".
#3300
fdd902c
Thanks @EmrysMyrddin! - dependencies updates:
- Updated dependency
  @graphql-yoga/logger@workspace:^ ↗︎
  (from ^2.0.0, in dependencies)
- Updated dependency
  @graphql-yoga/subscription@workspace:^ ↗︎
  (from ^5.0.0, in dependencies)
#3270
f9aa1cd
Thanks @andrew0! - Retain server context prototype for batched
requests
Updated dependencies
[fdd902c]:
- @graphql-yoga/subscription @5.0.1

`v5.3.1`

Compare Source

Patch Changes

#3237
3324bbab
Thanks @ardatan! - dependencies updates:
- Updated dependency
  @whatwg-node/server@^0.9.33 ↗︎
  (from ^0.9.32, in dependencies)
#3237
3324bbab
Thanks @ardatan! - In such environments like CloudFlare Workers, the
request object in the context always has the initial request object, so it was impossible to
access the actual Request object from the execution context. Now Yoga ensures that the request
in the context is the same with the actual Request.

`v5.3.0`

Compare Source

Minor Changes

#3197
f775b341
Thanks @n1ru4l! - Experimental support for aborting GraphQL execution
when the HTTP request is canceled.

The execution of subsequent GraphQL resolvers is now aborted if the incoming HTTP request is
canceled from the client side. This reduces the load of your API in case incoming requests with
deep GraphQL operation selection sets are canceled.
```
import { createYoga, useExecutionCancellation } from 'graphql-yoga'

const yoga = createYoga({
  plugins: [useExecutionCancellation()]
})
```
Learn more in our docs

Action Required In order to benefit from this new feature, you need to update your integration
setup for Fastify, Koa and Hapi.
```
- const response = await yoga.handleNodeRequest(req, { ... })
+ const response = await yoga.handleNodeRequestAndResponse(req, res, { ... })
```
Please refer to the corresponding integration guides for examples.
- Fastify
- Koa
- Hapi

Patch Changes

#3197
f775b341
Thanks @n1ru4l! - dependencies updates:
- Updated dependency
  @graphql-tools/executor@^1.2.5 ↗︎
  (from ^1.2.2, in dependencies)
- Updated dependency
  @whatwg-node/fetch@^0.9.17 ↗︎
  (from ^0.9.7, in dependencies)
- Updated dependency
  @whatwg-node/server@^0.9.32 ↗︎
  (from ^0.9.1, in dependencies)
#3214
f89a1aa2
Thanks @n1ru4l! - Always include empty data payload for final
complete event of SSE stream responses to ensure
EventSource compatibility. See
the
GraphQL over SSE protocol
for more information.

`v5.2.0`

Compare Source

Minor Changes

#3196
71db7548
Thanks @n1ru4l! - Allow setting async iterable within onParams hook
setResult function

Patch Changes

#3196
71db7548
Thanks @n1ru4l! - dependencies updates:
- Updated dependency
  @graphql-tools/executor@^1.2.2 ↗︎
  (from ^1.0.0, in dependencies)
- Updated dependency
  @graphql-tools/utils@^10.1.0 ↗︎
  (from ^10.0.0, in dependencies)

Configuration

📅 Schedule: Branch creation - "every 8 months on the first day of the month" (UTC), 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 · 2025-01-01T01:34:59Z

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	0%	0 / 571
🔵	Statements	0%	0 / 571
🔵	Functions	0%	0 / 6
🔵	Branches	0%	0 / 6

File Coverage

No changed files found.

Generated in workflow #428 for commit 49826a4 by the Vitest Coverage Report Action

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from 88c6674 to c93d5ad Compare January 6, 2025 15:02

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.10.8~~ chore(deps): update dependency graphql-yoga to ^5.10.9 Jan 6, 2025

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from c93d5ad to 91e8c7c Compare January 16, 2025 18:40

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.10.9~~ chore(deps): update dependency graphql-yoga to ^5.10.10 Jan 16, 2025

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from 91e8c7c to 20ea498 Compare January 27, 2025 10:55

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.10.10~~ chore(deps): update dependency graphql-yoga to ^5.10.11 Jan 27, 2025

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from 20ea498 to aa02451 Compare February 6, 2025 16:13

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.10.11~~ chore(deps): update dependency graphql-yoga to ^5.11.0 Feb 6, 2025

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from aa02451 to 0a853c1 Compare February 19, 2025 05:13

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.11.0~~ chore(deps): update dependency graphql-yoga to ^5.12.0 Feb 19, 2025

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from 0a853c1 to 6bf589b Compare February 24, 2025 14:29

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.12.0~~ chore(deps): update dependency graphql-yoga to ^5.12.1 Feb 24, 2025

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from 6bf589b to 2b84ed0 Compare March 3, 2025 05:13

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.12.1~~ chore(deps): update dependency graphql-yoga to ^5.12.2 Mar 3, 2025

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from 2b84ed0 to 634e24b Compare March 5, 2025 17:14

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.12.2~~ chore(deps): update dependency graphql-yoga to ^5.13.0 Mar 5, 2025

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.13.0~~ chore(deps): update dependency graphql-yoga to ^5.13.1 Mar 6, 2025

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from 634e24b to b0e702e Compare March 6, 2025 16:38

chore(deps): update dependency graphql-yoga to ^5.13.2

49826a4

renovate bot force-pushed the renovate/graphql-yoga-monorepo branch from b0e702e to 49826a4 Compare March 17, 2025 15:57

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.13.1~~ chore(deps): update dependency graphql-yoga to ^5.13.2 Mar 17, 2025

renovate bot changed the title ~~chore(deps): update dependency graphql-yoga to ^5.13.2~~ chore(deps): update dependency graphql-yoga to ^5.13.2 - autoclosed Apr 9, 2025

renovate bot closed this Apr 9, 2025

renovate bot deleted the renovate/graphql-yoga-monorepo branch April 9, 2025 15:58

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency graphql-yoga to ^5.13.2 - autoclosed#24

chore(deps): update dependency graphql-yoga to ^5.13.2 - autoclosed#24
renovate[bot] wants to merge 1 commit intomainfrom
renovate/graphql-yoga-monorepo

renovate bot commented Jan 1, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Jan 1, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate bot commented Jan 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Minor Changes

Basic usage

Multiple instrumentation plugins

Custom instrumentation ordering

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

github-actions bot commented Jan 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Coverage Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Jan 1, 2025 •

edited

Loading

github-actions bot commented Jan 1, 2025 •

edited

Loading