chore(deps): update dependency koa-body to v8#39
Merged
Conversation
B4nan
approved these changes
May 13, 2026
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:
^7.0.0→^8.0.0Release Notes
koajs/koa-body (koa-body)
v8.0.0Compare Source
Major Changes
f858724Thanks @TheDadi! - Drop support for Node.js 18 and 20, both of which are past end-of-life (Node 18 EOL April 2025, Node 20 EOL April 2026).The minimum supported version is now Node.js 22. CI is tested against Node 22 (Maintenance LTS), 24 (Active LTS), and 26 (Current).
If you are on Node 18 or 20, upgrade to Node 22+ before updating
koa-body. No source-level API changes accompany this bump — it reflects the supported runtime floor only.Minor Changes
9b3b5b6Thanks @TheDadi! - Add configurable body-type matchers:jsonTypes,urlencodedTypes,textTypes, andmultipartTypes.These options let callers customize which
Content-Typevalues are parsed as which body kind, without patching the middleware internals. Each accepts an array of types passed directly to Koa'sctx.is(...), so the standard mime patterns (e.g.urlencoded,multipart,text/*,application/vnd.custom+json) all work.Defaults preserve the previous behavior:
jsonTypes:application/json,application/json-patch+json,application/vnd.api+json,application/csp-report,application/reports+jsonurlencodedTypes:urlencodedtextTypes:text/*multipartTypes:multipartExample — parse a vendor JSON type and a custom multipart type:
v7.0.1Compare Source
Patch Changes
c060a9bThanks @TheDadi! - fix: use JsonValue from type-fest as body type fixes: #245Configuration
📅 Schedule: (UTC)
🚦 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.