fix(deps): update dependency graphql-yoga to v5.24.1 - #4649
Merged
Merged
Conversation
lowsky
enabled auto-merge (squash)
September 17, 2026 18:10
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
lowsky
force-pushed
the
renovate/graphql-yoga-5.x
branch
from
September 24, 2026 18:04
706e88d to
10d74be
Compare
coolboard
|
||||||||||||||||||||||||||||||
| Project |
coolboard
|
| Branch Review |
renovate/graphql-yoga-5.x
|
| Run status |
|
| Run duration | 00m 34s |
| Commit |
|
| Committer | Renovate |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
|
|
0
|
|
|
0
|
|
|
0
|
|
|
0
|
|
|
7
|
Upgrade your plan to view test results. | |
| View all changes introduced in this branch ↗︎ | |
lowsky
force-pushed
the
renovate/graphql-yoga-5.x
branch
from
September 24, 2026 18:47
10d74be to
1b72359
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.23.0→5.24.1Release Notes
graphql-hive/graphql-yoga (graphql-yoga)
v5.24.1Compare Source
Patch Changes
#4586
c6a9aa4Thanks @ardatan! - Fixes the issue thrown in the plugin that limits
the incoming request body's size, when the incoming
Requestobject is not the instance of thefetchAPI.Requestwhich is usually the ponyfill implementation from@whatwg-node/node-fetch.This will be fixed in the following breaking release in
@whatwg-node/node-fetchbut in order tounblock the current users of GraphQL Yoga, a small normalization layer has been added to the
plugin as a temporary workaround.
Since the native
Request.bodyis a nativeReadableStream, that doesn't support otherTransformStreamimplementation to itspipeThroughmethod, the limiting implementation didn'twork properly.
When the user ran Yoga within Next.js that uses the native
Requestobject, it threw aTypeErrorwhich causes a cryptic500 Internal Server Errorfor Next.js users.This workaround checks whether the incoming
Request's body object is an instance of the nativeReadableStreamand applies the appropriateTransformStreamimplementation to ensure therequest body size limiting works correctly.
v5.24.0Compare Source
Minor Changes
#4580
3763acaThanks @egoodwinx! - Limit the size of incoming HTTP request
bodies by default to protect against denial-of-service attacks from oversized payloads.
Requests whose
Content-Lengthexceeds the limit are rejected with an HTTP 413 response beforethe 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
maxRequestBodySizeoption, or set it tofalseto disable the limit (not recommended unless an upstream reverse proxy already enforcesone):
Also return an HTTP 400 response for malformed
multipart/form-datarequests (e.g. a missing orinvalid
boundary), instead of masking the parse error as a generic 500 Internal Server Error.Patch Changes
#4577
7bff35cThanks @egoodwinx! - Add homepage and bugs.url to package.json
files
Updated dependencies
[
7bff35c]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.