chore(deps): update dependency graphql-yoga to ^5.10.2 #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^5.1.1
->^5.10.2
Release Notes
dotansimha/graphql-yoga (graphql-yoga)
v5.10.2
Compare Source
Patch Changes
#3491
7a413bc
Thanks @n1ru4l! - dependencies updates:
@whatwg-node/server@^0.9.55
↗︎(from
^0.9.54
, independencies
)#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 bepropagated to all other batched requests contexts. It is resolved by updating the dependency of
@whatwg-node/server
to0.9.55
.v5.10.1
Compare Source
Patch Changes
20cd9b6
Thanks @ardatan! - dependencies updates:
@whatwg-node/fetch@^0.10.1
↗︎(from
^0.9.22
, independencies
)@whatwg-node/server@^0.9.54
↗︎(from
^0.9.50
, independencies
)v5.10.0
Compare Source
Minor Changes
f81501c
Thanks @maeldur! - Correctly handle HTTP GET requests with
?
characters in the query search string.
v5.9.0
Compare Source
Minor Changes
87ee333
Thanks @n1ru4l! - Inject initial context into
onParams
hook.Patch Changes
2523d9f
Thanks @kroupacz! - ### Fixed
version
v5.8.0
Compare Source
Minor Changes
18fe916
Thanks @kroupacz! - Add
version
property to get version of YogaPatch Changes
6bb19ed
Thanks @ardatan! - dependencies updates:
@whatwg-node/fetch@^0.9.22
↗︎(from
^0.9.18
, independencies
)@whatwg-node/server@^0.9.50
↗︎(from
^0.9.44
, independencies
)v5.7.0
Compare Source
Minor Changes
#3331
5dae4ab
Thanks @EmrysMyrddin! - Expose server context in
onResultProcessHook
. In particular, this gives access to thewaitUntil
method to cleanlyhandle 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
5dae4ab
Thanks @EmrysMyrddin! - dependencies updates:
@whatwg-node/server@^0.9.44
↗︎(from
^0.9.41
, independencies
)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 responseprotocol.
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:
@whatwg-node/server@^0.9.41
↗︎(from
^0.9.40
, independencies
)#3384
81a736b
Thanks @ardatan! - dependencies updates:
@envelop/core@^5.0.1
↗︎ (from^5.0.0
, independencies
)@graphql-tools/executor@^1.3.0
↗︎(from
^1.2.5
, independencies
)@graphql-tools/schema@^10.0.4
↗︎(from
^10.0.0
, independencies
)@graphql-tools/utils@^10.3.2
↗︎(from
^10.1.0
, independencies
)@whatwg-node/fetch@^0.9.18
↗︎(from
^0.9.17
, independencies
)@whatwg-node/server@^0.9.40
↗︎(from
^0.9.36
, independencies
)v5.6.1
Compare Source
Patch Changes
4252e3d
Thanks @ardatan! - dependencies updates:
@whatwg-node/server@^0.9.36
↗︎(from
^0.9.33
, independencies
)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
, andvariables
, thenthrows 400 HTTP Error. This change adds a new option called
extraParamNames
to allow extraparameters in the request body.
v5.5.0
Compare Source
Minor Changes
#3332
0208024
Thanks @ardatan! - Customize the landing page by passing a custom
renderer that returns
Response
to thelandingPage
optionv5.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 optionsare 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:
@graphql-yoga/logger@workspace:^
↗︎(from
^2.0.0
, independencies
)@graphql-yoga/subscription@workspace:^
↗︎(from
^5.0.0
, independencies
)#3270
f9aa1cd
Thanks @andrew0! - Retain server context prototype for batched
requests
Updated dependencies
[
fdd902c
]:v5.3.1
Compare Source
Patch Changes
#3237
3324bbab
Thanks @ardatan! - dependencies updates:
@whatwg-node/server@^0.9.33
↗︎(from
^0.9.32
, independencies
)#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 toaccess the actual
Request
object from the execution context. Now Yoga ensures that therequest
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.
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.
Please refer to the corresponding integration guides for examples.
Patch Changes
#3197
f775b341
Thanks @n1ru4l! - dependencies updates:
@graphql-tools/executor@^1.2.5
↗︎(from
^1.2.2
, independencies
)@whatwg-node/fetch@^0.9.17
↗︎(from
^0.9.7
, independencies
)@whatwg-node/server@^0.9.32
↗︎(from
^0.9.1
, independencies
)#3214
f89a1aa2
Thanks @n1ru4l! - Always include empty data payload for final
complete
event of SSE stream responses to ensureEventSource
compatibility. Seethe
GraphQL over SSE protocol
for more information.
v5.2.0
Compare Source
Minor Changes
71db7548
Thanks @n1ru4l! - Allow setting async iterable within
onParams
hooksetResult
functionPatch Changes
71db7548
Thanks @n1ru4l! - dependencies updates:
@graphql-tools/executor@^1.2.2
↗︎(from
^1.0.0
, independencies
)@graphql-tools/utils@^10.1.0
↗︎(from
^10.0.0
, independencies
)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.
This PR was generated by Mend Renovate. View the repository job log.