Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency graphql-yoga to v5 #823

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 16, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphql-yoga (source) ^1.18.3 -> ^5.0.0 age adoption passing confidence

Release Notes

dotansimha/graphql-yoga (graphql-yoga)

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

Patch Changes

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

v5.3.1

Compare Source

Patch Changes
  • #​3237
    3324bbab
    Thanks @​ardatan! - dependencies updates:

  • #​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.

Patch Changes

v5.2.0

Compare Source

Minor Changes
Patch Changes

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Patch Changes

v4.0.5

Compare Source

Patch Changes

v4.0.4

Compare Source

Patch Changes

v4.0.3

Compare Source

Patch Changes

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes
Patch Changes

v3.9.1

Compare Source

Patch Changes

v3.9.0

Compare Source

Minor Changes

v3.8.1

Compare Source

Patch Changes

v3.8.0

Compare Source

Minor Changes
Patch Changes

v3.7.3

Compare Source

Patch Changes

v3.7.2

Compare Source

Patch Changes

v3.7.1

Compare Source

Patch Changes

v3.7.0

Minor Changes
Patch Changes

v3.6.1

Patch Changes
  • 3c8c8434
    Thanks @​ardatan! - Replace LRU caching with lazy URL construction,
    avoid unnecessary parse and validate invocation and CORS

v3.6.0

Minor Changes
Patch Changes

v3.5.1

Patch Changes

v3.5.0

Minor Changes
  • #​2364
    03597a5a
    Thanks @​n1ru4l! - export the yoga default format error function.

    import { createYoga, maskError } from 'graphql-yoga'
    
    const yoga = createYoga({
      maskedErrors: {
        maskError(error, message, isDev) {
          if (error?.extensions?.code === 'DOWNSTREAM_SERVICE_ERROR') {
            return error
          }
    
          return maskError(error, message, isDev)
        }
      }
    })

v3.4.1

Compare Source

Patch Changes

v3.4.0

Compare Source

Patch Changes

v3.3.0

Compare Source

Minor Changes
Patch Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

Minor Changes
Patch Changes

v3.1.2

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@renovate renovate bot changed the title Update dependency graphql-yoga to v5 Update dependency graphql-yoga to v5 - autoclosed Jun 28, 2024
@renovate renovate bot closed this Jun 28, 2024
@renovate renovate bot deleted the renovate/graphql-yoga-5.x branch June 28, 2024 14:03
@renovate renovate bot restored the renovate/graphql-yoga-5.x branch June 28, 2024 16:16
@renovate renovate bot changed the title Update dependency graphql-yoga to v5 - autoclosed Update dependency graphql-yoga to v5 Jun 28, 2024
@renovate renovate bot reopened this Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants